Disclaimer: This article is intended to convey more market information and does not constitute any investment advice. The article only represents the author's views and does not represent the official position of MarsBit. Editor of
: Remember to pay attention to
Source: rixcian.eth/.lens
Original title: Tornado Cash’s centralized attack, how can we resist it?
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 its website itself and multiple Ethereum wallet addresses being banned. Additionally, the injunction prohibits all U.S. individuals and entities from interacting with Tornado Cash or any Ethereum wallet address associated with the protocol. Since the introduction of the ban, multiple DeFi protocols have begun to announce the ban of Tornado Cash-related addresses.
In this regard, BanklessCZECH Lianchuang rixcian proposed solutions to deal with relevant sanctions from five levels. 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 was sanctioned at the following five levels:
1. Tornado Cash website domain name was blocked
2. Infura and Alchemy closed RPC calls to Tornado Cash from the front end to support
3. Github deleted all code libraries and deactivated contributor accounts
4. Tornado Cash USDC was frozen in the contract
5. Aave blocked the Tornado Cash related address on the front end
1. The domain name was blocked
As shown in the figure below, the http://tornado.cash domain name is no longer running. How can this type of lockdown be prevented in the future?
Someone thought ENS might 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 ENS domain name resolution is "centralized", so use it to resist "decentralization" attack" is unrealistic.
solution
TheShake is a solution built on the Handshake protocol, which is a P2P domain name system. You only need to use their Beacon browser, and the browser will convert the Handshake domain name into the corresponding IPFS address in the background.
2. Infura and Alchemy prohibit interaction with Tornado Cash
Solution 1
Most dApps need to interact with the blockchain, so they should provide users with custom RPC settings like Tornado Cash.
Your wallet (usually Metamask) will be connected to the Infura node by default, so when you want to deposit ETH into Tornado Cash, the transaction will not be processed.
Workaround 2
You can set a node provider in Metamask that will not block your transactions.
But where can I get a truly decentralized RPC node provider?
solution 3
users can run the node themselves, but this method is not suitable for everyone.
Solution 4
You can select a supplier from the list below.
solution 5
uses Pocket Network. Rather than using just one node provider, why not choose from multiple node providers?
Solution 6
Use a node run by your local crypto community, such as Bordel or Gweicz (community members are running their own nodes and can share them with you).
3. Github bans the 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 restrictions.
4. USDC is frozen in the Tornado Cash contract
Solution
Use a truly decentralized Stablecoin, such as LUSD launched by Liquity or RAI launched by Reflexer. Note that DAI is not decentralized (it is primarily backed by USDC).
5. Aave front-end integration TRM API blocked address
Solution 1
You can still use this protocol through Etherscan or eth95.dev, although this is not suitable for everyone.
solution 2
adopts Aave's open source front end, removes TRM's API and deploys 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 front-end that is perfectly decentralized and has a good user experience.
solution 3
draws on the example of the Liquity team and only builds a permissionless protocol and lets the community build the front end on top of the protocol.
Please remember that nothing is difficult in the world, as long as you are willing to climb, the ETH community will always improvise, adapt immediately, and overcome immediately.
Editor in charge: MK
