Proposal to update Tornado IPFS hashes in ENS

Changes / effect description

Create new tornadocash.eth subdomains written in contants.ts and set Governance as owner for all
Assign corresponding IPFS contenthash to each domain

Requirements

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

Installation

git clone --recurse-submodules https://git.tornado.ws/Theo/proposal-30-decentralize-sources
cd proposal-30-decentralize-sources
npm install

Testing

npm run test:windows

npm run test:linux

Contracts

Proposal deployed contract: 0xaF0AbcF236D495AEfDA9f9e1DF5bECE0D132da66

Goerli test ENS address: tornadotest.eth (to see content, you need to connect wallet and switch to Goerli Testnet on app.ens.domains)

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).

Verification of the transformation of eth domains into ENS nodes:

Script source: calculateENSNodes.ts

Command to run: npm run calculateENS

Result data: ensNodesDeclarations.txt
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
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

2.7 KiB Raw Blame History