tornadocash
/
tornado-core
mirror of https://github.com/tornadocash/tornado-core.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

add whitepaper link

This commit is contained in:
Roman Semenov 2019-12-17 15:43:27 +07:00 committed by poma
parent a780956a63
commit 91e652ae66
No known key found for this signature in database
GPG Key ID: BA20CB01FE165657
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -6,7 +6,7 @@ To make a deposit user generates a secret and sends its hash (called a commitmen
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 contract’s 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](https://medium.com/@tornado.cash.mixer/introducing-private-transactions-on-ethereum-now-42ee915babe0)
You can read more about it in [this medium article](https://medium.com/@tornado.cash/introducing-private-transactions-on-ethereum-now-42ee915babe0)
## Specs
- Deposit gas const: 1088354 (43381 + 50859 * tree_depth)
@ -15,6 +15,8 @@ You can read more about it in [this medium article](https://medium.com/@tornado.
- Circuit Proof time = 10213ms (1071 + 347 * tree_depth)
- Serverless
[Whitepaper](https://tornado.cash/Tornado.cash_Whitepaper_v1.4.pdf)
![image](diagram.png)
## Was it audited?