3 ms·
Oh this is bullshit and you know it. Another example of "we didn't call it a security so it's not a security" They weren't arrested for the code. They were arr
by cududa 3y ago
Oh this is bullshit and you know it. Another example of "we didn't call it a security so it's not a security"
They weren't arrested for the code. They were arrested for actively participating and profiting off money laundering with North Korea being a customer.
Zero-knowledge proofs are different from public ledgers. That's where the issue comes in to play. The Treasury Department has already given guidance that cryptocurrency mixers fall under Know Your Customer laws and the Bank Secrecy Act, and are required to know who exactly is using their services and how.
It's not "Criminalizing Open Source". You live in a society with laws. Obfuscating classic financial products with tech jargon worked for the first half of the decade.
Y'all are just mad it doesn't work anymore and claim "You just don't understand the technology. You haven't issued guidance on specifics of crypto currency. You can't use hundred year old laws"
Yes, you can use 100 year old laws. At the end of the day, the financial shenanigans of most crypto, exchanges, and tokens are fundamentally the same things that have already been regulated. You just have new words.
- ipaddr 3y agoYou live in a society of variable laws that change at runtime get applied unevenly.
- cududa 3y agoClass templates get applied at runtime based on the heap size/ legacy properties of the initializing task. If we’re using software metaphors for things that aren’t software, I can pull that card too.
- pushedx 3y agoThe first half of which decade?
- cududa 3y agoYour pedantism perfectly illustrates my point