API/RSS

Social

How can we resist the centralized attack of Tornado Cash?

22-08-16 14:12

Read this article in 10 Minutes

AI summary

View the summary

Original author: BanklessCZECH Lianchuangrixcian

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), including The website itself was banned, along with several Ethereum wallet addresses. Additionally, the injunction prohibits all U.S.-based individuals and entities from interacting with Tornado Cash or any Ethereum wallet address associated with the protocol. Since the ban was issued, multiple DeFi protocols have announced the banning of Tornado Cash-related addresses.

In this regard, BanklessCZECH Lianchuangrixcian proposed solutions to deal with relevant sanctions from five levels , BlockBeats organizes and translates it as follows:

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

< /p>

Tornado Cash is sanctioned at the following five levels:

1. Tornado The domain name of the Cash website is blocked

2. Infura and Alchemy close the RPC call support for Tornado Cash from the frontend

3. GitHub deletes all code bases and disables contributor accounts

4. USDC was frozen in the Tornado Cash contract

5. Aave banned Tornado Cash related addresses on the front end

1. The domain name is blocked

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

< /p>

Some people think that ENS may be a solution. Unfortunately, this is not the case. Tornado Cash has an ENS domain name tornadocash.eth that can be used to access the front end (for example, through https://tornadocash.eth.limo/), but the ENS domain name resolution is "centralized", so it is used to defend against "attacks on decentralization " is unrealistic.

Solution

TheShake is a solution built on the Handshake protocol, which is a P2P domain name system. You just need to use their Beacon browser, and the browser will convert the Handshake domain name to the corresponding IPFS address in the background.

< /h4>

Second, Infura and Alchemy are prohibited from interacting with Tornado Cash

Solution 1

Most dApps need to interact with the blockchain, so they should provide users with self- Define RPC settings.

< /p>

Your wallet (usually Metamask) will connect to the Infura node by default, so when you want to deposit ETH into Tornado Cash, the transaction will not be processed.

Solution 2

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

< /p>

But where to get a truly decentralized RPC node provider?

Solution 3

Users can run nodes themselves, but this method is not suitable for everyone.

Solution 4

You can choose a provider from the list below.

< /h4>
Solution 5

Use Pocket Network. Instead of using just one node provider, why not choose from multiple node providers?

< /h4>
Workaround 6

Use a node you run on your local crypto community, eg Bordel or Gweicz (community members are running their own node and be able to share it with you).

3. Github bans Tornado Cash source code and all contributors

Solution

We can use the P2P Git network Radicle to share the source code of smart contracts or front ends without restriction.

4. USDC in the Tornado Cash contract Freeze

Solution

Use a truly decentralized Stablecoin, such as LUSD from Liquity or RAI from Reflexer. Note that DAI is not decentralized (it is primarily backed by USDC).

5. Aave front-end integrated TRM API banned address

Solution 1

You can still use the protocol via Etherscan or eth95.dev, although this is not for everyone.

Solution 2

Use Aave's open source front-end, remove TRM's API and deploy the website on IPFS or better Arweave network (permanent file storage solution). Then use Handshake (decentralized domain name service) and Voila Websocket, and you will have a perfectly decentralized front-end with a good user experience.

Solution 3

Borrowing the example of the Liquity team, only build a license-free protocol and let the community build a front-end on top of the protocol.

Remember, nothing is difficult in the world, as long as you are willing to climb, the ETH community will always improvise, Instantly adapt, instant overcome.