Tornado cash. Non-custodial private transactions on Ethereum.
Go to file
2019-08-30 13:21:53 +03:00
circuits split extra constraints back to 2 2019-08-02 12:24:50 +03:00
contracts test with real DAI and USDT 2019-08-30 13:06:17 +03:00
lib fix a bug 2019-07-23 00:19:50 +03:00
migrations test with real DAI and USDT 2019-08-30 13:06:17 +03:00
test test with real DAI and USDT 2019-08-30 13:06:17 +03:00
.editorconfig Move contracts to repository root 2019-07-12 12:53:44 +03:00
.env.example gas tuning 2019-08-30 13:21:53 +03:00
.eslintrc.json styling final 2019-07-16 23:49:45 +03:00
.gitattributes
.gitignore additional eth for the recipient 2019-08-27 23:42:24 +03: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 test cli in travis 2019-08-06 14:51:52 +03:00
cli.js additional eth for the recipient 2019-08-27 23:42:24 +03:00
index.html readme 2019-07-17 14:12:57 +03:00
LICENSE Create LICENSE 2019-07-17 14:14:07 +03:00
mixer.png readme 2019-07-17 14:12:57 +03:00
package-lock.json eslint vuln fix 2019-08-28 11:15:49 +03:00
package.json eslint vuln fix 2019-08-28 11:15:49 +03:00
README.md additional eth for the recipient 2019-08-27 23:42:24 +03:00
truffle-config.js gas tuning 2019-08-30 13:21:53 +03:00

Tornado mixer Build Status

mixer image

Specs

  • Deposit gas cost: deposit 888054
  • Withdraw gas cost: 692133
  • Circuit constraints: 22617
  • Circuit proving time: 6116ms
  • Serverless

Security risks

  • Cryptographic tools used by mixer (zkSNARKS, Pedersen commitment, MiMC hash) are not yet extensively audited by cryptographic experts and may be vulnerable
    • Note: we use MiMC hash only for merkle tree, so even if a preimage attack on MiMC is discovered, it will not allow to deanonymize users. To drain funds attacker needs to be able to generate arbitrary hash collisions, which is a pretty strong assumption.
  • Relayer is frontrunnable. When relayer submits a transaction someone can see it in tx pool and frontrun it with higher gas price to get the fee and drain relayer funds.
    • Workaround: we can set high gas price so that (almost) all fee is used on gas. The relayer will not receive profit this way, but this approach is acceptable until we develop more sophisticated system that prevents frontrunning
  • Bugs in contract. Even though we have an extensive experience in smart contract security audits, we can still make mistakes. An external audit is needed to reduce probablility of bugs
  • Nullifier griefing. when you submit a withdraw transaction you reveal the nullifier for your note. If someone manages to make a deposit with the same nullifier and withdraw it while your transaction is still in tx pool, your note will be considered spent since it has the same nullifier and it will prevent you from withdrawing your funds
    • Fixed by sending nullifier hash instead of plain nullifier

Requirements

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

Usage

  1. npm i
  2. cp .env.example .env
  3. npm run build:circuit - may take 10 minutes or more
  4. npm run build:contract
  5. npm run browserify
  6. npx ganache-cli
  7. npm run test - optionally run tests. It may fail for the first time, just run one more time.
  8. npm run migrate:dev
  9. ./cli.js deposit
  10. ./cli.js withdraw <note from previous step> <destination eth address>
  11. ./cli.js balance <destination eth address>
  12. vi .env - add your Kovan private key to deploy contracts
  13. npm run migrate
  14. npx http-server - serve current dir, you can use any other http server
  15. Open localhost:8080

Deploy ETH Tornado Cash

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

Deploy ERC20 Tornado Cash

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

Note. If you want to reuse the same verifier for all the mixers, then after you deployed one of the mixers you should only run 4th or 5th migration for ETH or ERC20 mixers 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