Tornado cash. Non-custodial private transactions on Ethereum.
Go to file
2020-02-27 16:36:44 +03:00
circuits new circomlib update 2019-12-13 13:18:16 -08:00
contracts remove migration script (moving to a separate branch) 2019-12-14 15:23:59 +07:00
lib change zero value constant 2019-11-15 11:44:07 +03:00
migrations Rename 2019-12-14 12:44:18 +03:00
test rename variables 2019-12-13 20:49:19 +07:00
.editorconfig Move contracts to repository root 2019-07-12 12:53:44 +03:00
.env.example change tree depth to 20 2019-12-11 19:29:03 +07:00
.eslintrc.json styling final 2019-07-16 23:49:45 +03:00
.gitattributes add dummy test 2019-07-10 19:58:21 +03:00
.gitignore rename variables 2019-12-13 20:49:19 +07:00
.nvmrc fix tests 2019-07-23 13:00:45 -07:00
.solhint.json add pauseDeposits 2019-08-01 01:41:22 -07:00
.travis.yml add erc20 to integration test 2019-10-04 19:27:19 +03:00
cli.js fix browser version; readme update 2020-02-27 16:32:10 +03:00
config.js tidy 2020-02-27 16:36:44 +03:00
diagram.png rename variables 2019-12-13 20:49:19 +07:00
downloadKeys.js fix browser version; readme update 2020-02-27 16:32:10 +03:00
index.html rename variables 2019-12-13 20:49:19 +07:00
LICENSE Create LICENSE 2019-07-17 14:14:07 +03:00
package-lock.json WIP 2020-02-26 16:57:53 +03:00
package.json fix browser version; readme update 2020-02-27 16:32:10 +03:00
README.md fix browser version; readme update 2020-02-27 16:32:10 +03:00
truffle-config.js update dependencies 2019-11-08 04:11:29 +03:00

Tornado Cash Privacy Solution Build Status

Tornado Cash is a non-custodial Ethereum and ERC20 privacy solution based on zkSNARKs. It improves transaction privacy by breaking the on-chain link between recipient and destination addresses. It uses a smart contract that accepts ETH deposits that can be withdrawn by a different address. Whenever ETH is withdrawn by the new address, there is no way to link the withdrawal to the deposit, ensuring complete privacy.

To make a deposit user generates a secret and sends its hash (called a commitment) along with the deposit amount to the Tornado smart contract. The contract accepts the deposit and adds the commitment to its list of deposits.

Later, the user decides to make a withdrawal. In order to do that, the user should provide a proof that he or she possesses a secret to an unspent commitment from the smart contracts list of deposits. zkSnark technology allows that to happen without revealing which exact deposit corresponds to this secret. The smart contract will check the proof, and transfer deposited funds to the address specified for withdrawal. An external observer will be unable to determine which deposit this withdrawal came from.

You can read more about it in this medium article

Specs

  • Deposit gas const: 1088354 (43381 + 50859 * tree_depth)
  • Withdraw gas cost: 301233
  • Circuit Constraints = 28271 (1869 + 1325 * tree_depth)
  • Circuit Proof time = 10213ms (1071 + 347 * tree_depth)
  • Serverless

image

Whitepaper

https://tornado.cash/Tornado.cash_whitepaper_v1.4.pdf

Was it audited?

Tornado.cash protocols, circuits, and smart contracts were audited by a group of experts from ABDK Consulting, specializing in zero knowledge, cryptography, and smart contracts.

During the audit no critical issues were found and all outstanding issues were fixed. The results can be found here:

Underlying circomlib dependency is currently being audited, and the team already published most of the fixes for found issues

Requirements

  1. node v11.15.0
  2. npm install -g npx

Usage

You can see example usage in cli.js, it works both in console and in browser.

  1. npm install
  2. cp .env.example .env
  3. npm run build - this may take 10 minutes or more
  4. npx ganache-cli
  5. npm run test - optionally runs tests. It may fail on the first try, just run it again.

Use browser version on Kovan:

  1. vi .env - add your Kovan private key to deploy contracts
  2. npm run migrate
  3. npx http-server - serve current dir, you can use any other static http server
  4. Open localhost:8080

Use with command line version. Works for Ganache, Kovan and Mainnet:

Initialization

  1. cp .env.example .env
  2. npm run download
  3. npm run build:contract

Ganache

  1. make sure you complete steps from Initialization
  2. ganache-cli -i 1337
  3. npm run migrate:dev
  4. ./cli.js test
  5. ./cli.js --help

Kovan, Mainnet

  1. make sure you complete steps from Initialization
  2. Add PRIVATE_KEY to .env file
  3. ./cli.js --help

Example:

./cli.js deposit ETH 0.1 --rpc https://kovan.infura.io/v3/27a9649f826b4e31a83e07ae09a87448
Your note: tornado-eth-0.1-42-0xf73dd6833ccbcc046c44228c8e2aa312bf49e08389dadc7c65e6a73239867b7ef49c705c4db227e2fadd8489a494b6880bdcb6016047e019d1abec1c7652
Tornado ETH balance is 8.9
Sender account ETH balance is 1004873.470619891361352542
Submitting deposit transaction
Tornado ETH balance is 9
Sender account ETH balance is 1004873.361652048361352542

./cli.js withdraw tornado-eth-0.1-42-0xf73dd6833ccbcc046c44228c8e2aa312bf49e08389dadc7c65e6a73239867b7ef49c705c4db227e2fadd8489a494b6880bdcb6016047e019d1abec1c7652 0x8589427373D6D84E98730D7795D8f6f8731FDA16 --rpc https://kovan.infura.io/v3/27a9649f826b4e31a83e07ae09a87448 --relayer https://kovan-frelay.duckdns.orgRelay address:  0x6A31736e7490AbE5D5676be059DFf064AB4aC754
Getting current state from tornado contract
Generating SNARK proof
Proof time: 9117.051ms
Sending withdraw transaction through relay
Transaction submitted through the relay. View transaction on etherscan https://kovan.etherscan.io/tx/0xcb21ae8cad723818c6bc7273e83e00c8393fcdbe74802ce5d562acad691a2a7b
Transaction mined in block 17036120
Done

Deploy ETH Tornado Cash

  1. cp .env.example .env
  2. Tune all necessary params
  3. npx truffle migrate --network kovan --reset --f 2 --to 4

Deploy ERC20 Tornado Cash

  1. cp .env.example .env
  2. Tune all necessary params
  3. npx truffle migrate --network kovan --reset --f 2 --to 3
  4. npx truffle migrate --network kovan --reset --f 5

Note. If you want to reuse the same verifier for all the instances, then after you deployed one of the instances you should only run 4th or 5th migration for ETH or ERC20 contracts respectively (--f 4 --to 4 or --f 5).

Credits

Special thanks to @barryWhiteHat and @kobigurk for valuable input, and to @jbaylina for awesome Circom & Websnark framework