randomran01234
You can target the UXTO so that their value in crypto starts back at zero. But because they still have the mining hardware, they still control 51% of the hash power that secures the network. They can just mine from a different address and it won’t be clear who to target until they once again begin to produce majority blocks on the chain. This way they can continually attack the chain and render it useless.
When you burn a PoW miner’s crypto addresses, you aren’t burning their capital and stake, because it’s in the form of mining hardware, not tokens. When you burn a PoS staker’s crypto, you are burning their capital and stake which is in the form of tokens.
The main goal of crypto - the base token and protocol rewards from PoW or PoS - is to secure this network and keep it permissionless and decentralized.
All fields of engineering are complex to those that have an not studied them.
Lack of education can be fixed. You can even help: instead of spreading poor information, try to educate your readers about the difference between a node as a service and liveness of the blockchain.
I do agree this is probably the most concerning thing that Tornado Cash sanctions have shown us. Still don’t think the energy cost of PoW is worth it, and would rather see PBS and crList solve this problem.
Censorship of transactions because of OFAC is already happening in PoW mining.
https://twitter.com/takenstheorem/status/1560690035955011585...
Same argument can be made for key management. A typical user could use non custodial wallet, but they don’t. But that option exists, for when they become unsatisfied with their centralized wallet custodian, or when they want to change custodians, or when they want to use a multi sig that allows for a mix of custodial and non custodial.
Importantly: the option exists. The option to use non custodial EOA and smart contract wallet, DAI or RAI, Alchemy or a custom node RPC, Kraken or another CEX or DEX, the option is present and is chosen by plenty of users.
When one of the popular nodes as a service goes down, many dApps and users will need to change their endpoint to another. I think the author might be overstating the concern of this centralization.
The solution to RPC centralization is well known: light clients. It is on the developers roadmap but obviously they are prioritizing proof of stake and scalability.
> it's an action-oriented look at how tech and entertainment monopolies steal creators' incomes, with detailed, shovel-ready plans to unrig creative labor markets and pay artists
Let’s just agree to disagree though.
https://www.amazon.ca/Chokepoint-Capitalism-Content-Captured...
> You can pre-order the book on Amazon. It’s like a PETA selling furs to support their anti-fur campaign.
Edit: included Amazon as he is also selling his product through it.
https://www.amazon.ca/Chokepoint-Capitalism-Content-Captured...
Harder to imagine any L1 blockchain ever being able to reach the throughput needed without dramatic trade-offs in decentralization, censorship-resistance and security. At that point you might wonder how it would be any different than a centralized Visa or Mastercard network.
Do you disagree with the widespread reporting on the outcome of this case?
https://www.britannica.com/event/Bernstein-vs-the-US-Departm...
> Bernstein v. the U.S. Department of State, landmark legal decision (1996) that set two important precedents in the field of digital technology. First, it ruled that U.S. government regulations that barred the export of encryption software were unconstitutionally restrictive; second, it declared that software source code can be a form of protected free speech.
and
https://casetext.com/case/bernstein-v-united-states-dept-of-...
> The district court found that the Source Code was speech protected by the First Amendment, see Bernstein v. Department of State, 922 F. Supp. 1426 (N.D. Cal. 1996) ("Bernstein I")
https://harvardlawreview.org/2020/02/the-establishment-claus...
https://en.m.wikipedia.org/wiki/Chilling_effect
The bigger problem is whether republishing the source code would make you a target of the sanctions. If a user republishes the source code on Ethereum, pirate bay, Gitlab, or another host then it is reasonable to assume their actions might be interpreted as “supporting the Tornado Cash project” which makes them a target of the sanctions. If a user modifies the code and republishes it probably will fall under same risks.
https://www.eff.org/deeplinks/2015/04/remembering-case-estab...
The debate is pretty settled that code and language should be protected by 1st amendment as free speech. Based on this precedent, we should not be cheering on the barring of the open source project and it’s developers.
It is less clear if the execution and use of code should be free speech, and how to regulate code and language when the sole goal is illicit. Like anarchist cookbook, 3D printed guns. But to argue this, you will have to argue the sole goal of Tornado Cash is to aid in illicit behavior. There are many licit users of the protocol, like with Tor, who just want to seek privacy in their online communication.
The issue comes down to whether sending and receiving private keys in an encrypted way over the internet should be protected or not.