mirror of
https://github.com/tornadocash/tornado-core.git
synced 2024-10-01 01:06:17 -04:00
readme
This commit is contained in:
parent
9bd2c5eff3
commit
b595d29321
14
README.md
14
README.md
@ -17,5 +17,19 @@
|
||||
1. `node v11.15.0`
|
||||
2. `npm install -g npx`
|
||||
|
||||
# Specs:
|
||||
- Deposit gas cost: deposit 903472
|
||||
- Withdraw gas cost: 727821
|
||||
- Circuit constraints: 22617
|
||||
- Circuit proving time: 8965ms
|
||||
- Serverless, executed entirely in the browser
|
||||
|
||||
# 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 or drain mixer funds
|
||||
* 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
|
||||
|
||||
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user