[ 3 / biz / cgl / ck / diy / fa / ic / jp / lit / sci / vr / vt ] [ index / top / reports ] [ become a patron ] [ status ]
2023-11: Warosu is now out of extended maintenance.

/biz/ - Business & Finance

Search:


View post   

>> No.57331454 [View]
File: 720 KB, 1362x768, Heisensbergey.png [View same] [iqdb] [saucenao] [google]
57331454

next couple of years are gonna be crazy. life will be very different by the end of 2025

>> No.55224631 [View]
File: 720 KB, 1362x768, Heisensbergey.png [View same] [iqdb] [saucenao] [google]
55224631

>>55224600
you can't keep getting away with this

>> No.49583634 [View]
File: 720 KB, 1362x768, Heisensbergey.png [View same] [iqdb] [saucenao] [google]
49583634

>>49583444
checked

>> No.22805875 [View]
File: 721 KB, 1362x768, Heisensbergey.png [View same] [iqdb] [saucenao] [google]
22805875

>>22805844

>> No.17704844 [View]
File: 721 KB, 1362x768, 1570796533212.png [View same] [iqdb] [saucenao] [google]
17704844

>>17704758
>42 is one of the most annoying namefags
>>17704812
>Buidl something faggot

>> No.16816019 [View]
File: 721 KB, 1362x768, 1570796533212.png [View same] [iqdb] [saucenao] [google]
16816019

>>16815940
>Kys
your obsession with suicide says a lot about you

>> No.16497329 [View]
File: 721 KB, 1362x768, Heisensbergey.png [View same] [iqdb] [saucenao] [google]
16497329

>>16496934

>> No.16403910 [View]
File: 721 KB, 1362x768, 1570796533212.png [View same] [iqdb] [saucenao] [google]
16403910

>>16403889
>they DON'T WANT YOU IN THEIR CLUB
you don't know the first thing about what happened during ICO
shush

>> No.16258785 [View]
File: 721 KB, 1362x768, 1570796533212.png [View same] [iqdb] [saucenao] [google]
16258785

>>16258311
>THEY CANT KEEP GETTING AWAY WITH IT

>> No.16219503 [View]
File: 721 KB, 1362x768, 1570796533212.png [View same] [iqdb] [saucenao] [google]
16219503

>>16219486

>> No.16175880 [View]
File: 721 KB, 1362x768, 1570796533212.png [View same] [iqdb] [saucenao] [google]
16175880

>>16172040
>Sergey's blogpost is a lie
liddle Joey Krug is upset>>16173890

>> No.16104052 [View]
File: 721 KB, 1362x768, 1570796533212.png [View same] [iqdb] [saucenao] [google]
16104052

>>16103859
>Sounds kinda rapey anon

>> No.16018662 [View]
File: 721 KB, 1362x768, 1570796533212.png [View same] [iqdb] [saucenao] [google]
16018662

>>16018329
>4chan nazis

>> No.15996047 [View]
File: 721 KB, 1362x768, 1570796533212.png [View same] [iqdb] [saucenao] [google]
15996047

>>15995151

>> No.15900245 [View]
File: 721 KB, 1362x768, 1570796533212.png [View same] [iqdb] [saucenao] [google]
15900245

>>15900117
>Script nigger.
lol you wish

>> No.15886386 [View]
File: 721 KB, 1362x768, Heisensbergey.png [View same] [iqdb] [saucenao] [google]
15886386

>>15886300
>>15886377

>> No.13889685 [View]
File: 721 KB, 1362x768, Heisensbergey.png [View same] [iqdb] [saucenao] [google]
13889685

>>13889548
infinitely based and eternally redpilled. instant pasta

>> No.13162899 [View]
File: 721 KB, 1362x768, 1540907437660.png [View same] [iqdb] [saucenao] [google]
13162899

I was at the fireside chat this week. At one point Tom called Sergey a sandwich fucker. He even accused Sergey of eating the sandwiches after busting loads into them. There was an intense bit of silence while Sergey glared. Beads of sweat formed on his forehead immediately, and his face was flush. He forced a chuckle into the microphone. Then he walked off stage and just out of the room where there was a magazine rack. He was still in full view of everyone through a window. He starts taking these magazines, two and three at a time, and just tearing them to shreds. Sometimes he would pick one up, and try to twist and tear the whole thing at once, but fail, so then he would start ripping out individual pages. He was facing away from everyone, so we couldn't see his facial expressions. This went on for two minutes at least. At this point I thought he was totally screwed, and that he had just ruined the reputation of chainlink in one fell swoop. However, he turned around and walked back into the room. He looked completely rejuvinated and full of vigor again. He proceeded to completely btfo Tom in every way, acting as if nothing out of the ordinary had happened. Afterwards, he even did a little q&a session after Tom left due to being frustrated from the btfo. Janitorial services were picking up the mess of shredded magazines at this point, and the only acknowledgement Sergey ever made to the mess was when one of the older janitors fell over while leaning to pick up the pieces. He sort of covered his hand with his mouth, clearly holding back laughter. It was bizarre, but with genius comes inevitable personality quirks.

>> No.11577706 [View]
File: 721 KB, 1362x768, Heisensbergey.png [View same] [iqdb] [saucenao] [google]
11577706

>>11577438

>> No.11544933 [View]
File: 721 KB, 1362x768, Heisensbergey.png [View same] [iqdb] [saucenao] [google]
11544933

>888

>> No.11439511 [View]
File: 721 KB, 1362x768, Heisensbergey.png [View same] [iqdb] [saucenao] [google]
11439511

>That leaves us with the developers of the smart contract code that underlies these event contracts, as well as the individual users who then use that code to create and wager on their own event contracts. The developers of the code could claim that they merely created the protocol and therefore have no control over whether and how users choose to use it once it is part of the public domain. They would place the liability on the individual users, who are the actual creators and counterparties of the event contracts.

>In my view, this analysis misses the mark. Instead, I think the appropriate question is whether these code developers could reasonably foresee, at the time they created the code, that it would likely be used by U.S. persons in a manner violative of CFTC regulations. In this particular hypothetical, the code was specifically designed to enable the precise type of activity regulated by the CFTC, and no effort was made to preclude its availability to U.S. persons. Under these facts, I think a strong case could be made that the code developers aided and abetted violations of CFTC regulations.[9] As such, the CFTC could prosecute those individuals for wrongdoing.

From:
https://www.cftc.gov/PressRoom/SpeechesTestimony/opaquintenz16

How the fuck is enforcement even going to work. The rate of development of smart contracts is going to far outstrip the ability of the CFTC to go after individual developers, and in the case of open source software someone else can literally just copy the program and use it. He goes on to say that going after individual contracting parties will be relatively futile (which is true) but even going after developers, especially with the ridiculously wide net he is using, is going to be equally futile.
I just can't foresee how the law is going to keep up with this at all. It's almost out of their hands.

>> No.11435007 [View]
File: 721 KB, 1362x768, Heisensbergey.png [View same] [iqdb] [saucenao] [google]
11435007

>>11433594
>>11433611
>>11433622
>>11433644
>>11433655
>>11433677

Navigation
View posts[+24][+48][+96]