Talking about how to prevent the centralized attack of Tornado Cash from five levels

Original author: BanklessCZECH Lianchuang rixcian

Original compilation: 0x9F, 0x214, BlockBeats

On August 8, the U.S. Department of the Treasury’s Office of Foreign Assets Control (OFAC) announced that Tornado Cash would be included in the Sanctions List (SDN), includingIts website itself was banned along with several Ethereum wallet addresses. Additionally, the ban prohibits all US-based individuals and entities from interacting with Tornado Cash or any Ethereum wallet address associated with the protocol. Since the introduction of the ban,Several DeFi protocols have begun to announce the banning of Tornado Cash-related addresses。

In this regard, BanklessCZECH Lianchuangrixcian proposed solutions to deal with relevant sanctions from five levels, and BlockBeats compiled and translated them as follows:

Now, what options and solutions does the ETH community have to prevent "attacks on decentralization"? What can we do in the future?

Tornado Cash is sanctioned at the following five levels:

1. Tornado Cash website domain name blocked

2. Infura and Alchemy turn off support for RPC calls to Tornado Cash from the frontend

3. GitHub deletes all repositories and disables contributor accounts

4. USDC is frozen in the Tornado Cash contract

first level title

1. The domain name is blocked

As shown in the image below, the http://tornado.cash domain name is no longer operational. How can this type of blockade be prevented in the future?

secondary title

Solution

first level title

secondary title

Solution 1

Most dApps need to interact with the blockchain, so they should provide users with custom RPC settings like Tornado Cash did.

secondary title

Solution 2

You can set up a node provider in Metamask that won't block your transactions.

secondary title

Solution 3

secondary title

Solution 4

you can get fromThe list belowsecondary title

Solution 5

secondary title

Solution 6

orBordelorGweiczfirst level title

secondary title

Solution

first level title

secondary title

Solution

first level title

secondary title

Solution 1

You can still use Etherscan oreth95.devsecondary title

Solution 2

secondary title

Solution 3

Following the example of the Liquity team, only build a permissionless protocol and let the community build the front end on top of the protocol.

Original link

Original link