2 ms·
The fact that TC is an autonomous program is central to their statutory argument. They advance two parallel justifications for the argument: * A separate divis
by woodruffw 4y ago
The fact that TC is an autonomous program is central to their statutory argument. They advance two parallel justifications for the argument:
* A separate division of the Treasury (FinCEN) makes a policy distinction between various groups of users/operations of transaction anonymization software. The authors concede that OFAC is not bound to this policy distinction.
* OFAC's stated mission is to bring about a "positive change in behavior." They claim that this can't happen with an autonomous contract, neglecting that the entire point is to scare developers away from deploying and using these kinds of contracts (which is indeed, from the Treasury's perspective, a positive change).
Later on, they make a separate argument that inclusion in the OFAC list exceeds statutory authority under IEEPA. The claim there also relies on autonomy: that the "Tornado Cash Entity" is not meaningfully an operator of the "Tornado Cash Application," because the former cannot cease operation of the latter.
This splits an exceedingly fine hair: it requires the Treasury to accept that the Tornado Cash Entity, despite being the prime mover for the Tornado Cash Application, is somehow not responsible for the thing it wrought. In other words, the "brick on the accelerator" argument.
Later, there's some more plausible hair splitting over whether the term "property" correctly applies, despite there being little to no disagreement over whether North Korea actually did launder a bunch of money through the Tornado Cash Application. So it comes down to whether the Treasury (and a jury) can be convinced that being the prime mover somehow does not matter.
- tonyarkles 4y ago> This splits an exceedingly fine hair: it requires the Treasury to accept that the Tornado Cash Entity, despite being the prime mover for the Tornado Cash Application, is somehow not responsible for the thing it wrought. In other words, the "brick on the accelerator" argument. I’m with you here. If I build a machine with no off switch that kills anyone who approaches it, even though it’s now completely out of my control… there’s a pretty clear connection between me and my creation. I have a feeling that people are going to be disappointed when “I built this autonomous thing and because I have no control over it I can’t be held responsible for it” is actually interpreted by the courts as “you built it and are responsible for every crime it commits”
- notch656a 4y agoWith ethereum applications someone can just publish the blue print, some random person anywhere in the world can publish the application for N ETH, and then everyone running the ethereum virtual machine executes the autonomous thing (interestingly the latter here haven't been sanctioned or blamed/punished at all). Sniffing out who actually paid the ethereum network to absorb the machine could be basically impossible, and once people start getting prosecuted you can bet almost anyone doing so will effectively do it in a way where it is impossible to find them. Either ethereum virtual machine operators at large is criminal organization or it's an endless game of a cat trying to catch its tail.
- salawat 4y ago>This splits an exceedingly fine hair: it requires the Treasury to accept that the Tornado Cash Entity, despite being the prime mover for the Tornado Cash Application, is somehow not responsible for the thing it wrought. In other words, the "brick on the accelerator" argument. This is completely thrown out in reality, because Courts've already handled this. If you create a thing that does harm (booby trap), you are still liable for damages incurred as a result of it's fundamental operation as you created the danger. Also see the case withregards to Alfred Anaya to dissuade yourself of the notion that they'd never go after someone for bringing into existence an instance of a tool key in facilitating known criminal activity. Besides which, Tornado.Cash screwed up as far as I'm aware, because they were financial beneficiaries of the operation of the mechanism. This is also something Courts are quite adept at being able to see through in spite of obfuscatory application of tech. So there is a tangible link there to anchor on both in the sense that the Entity's assets get sanctioned, and any addresses involved in the technical implementation get sanctioned. Anyone spinning up anything recognizably similar, (and I assure you, a recognizer that runs over the chain to find similar patterns of behavior is well within technical capabilities), will find themselves needing to resort to more and more elaborate constructs as more examples of the underlying implementation pattern of activity become known. This'll converge to becoming Yet Another Form of Financial Engineering Arms Race (tm). It is very difficult to outpace Nation states. Especially when you consider they are attractive pass times to those who like dealing with large distributed problems once one gets beyond a certain level of financial independence.