Proposal to update Tornado IPFS hashes in ENS

Changes / effect description

• Change owner of ENS domains staking-rewards.contract.tornadocash.eth and contract.tornadocash.eth to Tornado Cash Governance
• Change address on staking-rewards.contract.tornadocash.eth to new staking address (has been changed in proposal 22)
• Update IPFS content hashes on ENS domains for docs (docs.tornadocash.eth), Classic UI (tornadocash.eth), Nova UI (nova.tornadocash.eth) and relayers UI (relayers-network.tornadocash.eth)

Requirements

• Rust (Need only for Windows)
• Foundryup (Windows, Linux)
• Node 20 or higher (Windows, Linux)

Installation

git clone --recurse-submodules https://git.tornado.ws/Theo/proposal-27-update-ipfs.git
cd proposal-27-update-ipfs
npm install
npm run init

Testing

npm run test:windows

or

npm run test:linux

Verification

Since the proposal code can be confusing because it relies on numerous specifications and EIPs, users can use scripts to verify the correctness of the data, see the output in the corresponding files, and insert the code directly into Solidity, comparing it with the existing code in the proposal (there should be no discrepancies be).

1. Verification of the transformation of eth domains into ENS nodes:

   Script source: calculateENSNodes.ts

   Command to run: npm run calculateENS

   Result data: ensNodesDeclarations.txt

2. Verification of the transformation of IPFS CIDs to ENS content hashes

   Script source: calculateIPFSContenthashes.ts

   Command to run: npm run calculateIPFS

   Result data: ensDomainsIPFSContenthashes.txt

3. Verification of the equality IPFS CIDs v0 with v1 (because ENS on its interface shows v1 CIDs, but Pinata and contenthash library uses v0)

   Script source: calculateIpfsV1Cids.ts

   Command to run: npm run calculateIpfsV1Cids

   Result data: ipfsV1CIDs.txt