1
0
mirror of https://github.com/tornadocash/docs synced 2024-02-02 15:04:08 +01:00

GitBook: [master] 4 pages modified

This commit is contained in:
Ayefda 2021-09-09 17:00:42 +00:00 committed by gitbook-bot
parent 8c2ad79ec8
commit 2d26520bc0
No known key found for this signature in database
GPG Key ID: 07D2180C7B12D0FF
4 changed files with 12 additions and 11 deletions

View File

@ -1,5 +1,7 @@
# Introduction of Tornado.Cash
**\[Work in progress\]**
![](.gitbook/assets/image.png)
Tornado Cash is a **fully decentralized** **non-custodial** **protocol** allowing private transactions in the crypto-space.
@ -28,9 +30,9 @@ As of today, Tornado.Cash can be used with the following tokens:
![](.gitbook/assets/non-custodial-anonymous-transactions-on-ethereum-3-.png)
The protocol also includes an **anonymity mining system for some of its token**, allowing its users to earn a **governance token**. Thanks to TORN tokens, Tornado Cash users actively participate in shaping the protocol. The community has a strong weight regarding the evolution of Tornado Cash and the improvement of its features. Indeed, protocol parameters & token distribution are completely under the community's control through this governance.
The protocol also includes an **anonymity mining system for some of its token**, allowing its users to earn a **governance token**. Thanks to TORN tokens, Tornado Cash users actively participate in shaping the protocol. The community has a strong weight regarding the evolution of Tornado Cash and the improvement of its features. Indeed, protocol para@eters & token distribution are completely under the community's control through this governance.
_More information about_ [_Anonymity mining_](anonymity-mining.md) _&_ [_Tornado.Cash token_](torn.md) _are available._
More information about [Anonymity mining](anonymity-mining.md) & [Tornado.Cash token](torn.md) are available.
## How does Tornado.Cash run?
@ -38,9 +40,7 @@ _More information about_ [_Anonymity mining_](anonymity-mining.md) _&_ [_Tornado
The protocol also functions with zk-SNARK, which enables zero-knowledge proofs allowing users to demonstrate possession of information without needing to reveal it. The use of this technology is based **on open source research made by Zcash team with the help of Ethereum community**. To set-up zk-SNARK initial keys, Tornado.Cash[ Trusted Setup Community](https://tornado-cash.medium.com/tornado-cash-trusted-setup-ceremony-b846e1e00be1) was launched in May 2020 & accounted [for 1114 contributions](https://tornado-cash.medium.com/the-biggest-trusted-setup-ceremony-in-the-world-3c6ab9c8fffa). This significant number of contributors makes it impossible to compromise the protocol by faking zero-knowledge proofs.
User interface is hosted on **IPFS** \(InterPlanetary File System\) by the community, minimizing risks of data being deleted. Indeed, the interface will work as long as at least one user is hosting it.
User interface is hosted on **IPFS** \(InterPlanetary File System\) by the community, minimizing risks of data being deleted. Indeed, the interface will work as long as at least one user is hosting it.
_Written by_ [_@ayefda_](https://torn.community/u/ayefda)\_\_

View File

@ -1,5 +1,7 @@
# Community Involvement
**\[Work In Progress\]**
In a Decentralized Autonomous Organization \(DAO\), significant elements such as protocol parameters & token distribution are controlled by the community through governance. This governance allows the community to shape & continuously improve the protocol.
However, the role of a community does not stop to suggesting proposals & expressing its opinion through votes. The community can also actively contribute to the success and prosperity of their protocol through constructive debates, mutual help and specific actions.

View File

@ -6,7 +6,7 @@ However, maintaining privacy and preserving financial freedom should never come
To this extent, **Tornado.Cash Compliance Tool enables users to prove the origin of their funds.** Thanks to the Note generated after each deposit, **this tool will issue a cryptographically verified proof of transactional history** using the Ethereum addresses used to deposit & withdraw assets.
You can visit the Medium post related to this tool to learn more about the development and launch: [**Tornado.Cash compliance Medium Post**](https://tornado-cash.medium.com/tornado-cash-compliance-9abbf254a370).
You can visit the Medium post related to this tool to learn more about is development and launch: [**Tornado.Cash compliance Medium Post**](https://tornado-cash.medium.com/tornado-cash-compliance-9abbf254a370).
Therefore, if you are ever in need to prove the origin of held assets withdrawn from one of Tornado.Cash pools, we invite you to use the following [Compliance Tool](https://app.tornado.cash/compliance/):

View File

@ -1,5 +1,7 @@
# How does Tornado.Cash work?
**\[Work in progress\]**
Before diving in tutorials explaining & easing the use of Tornado.Cash, here is an overall overview of the protocol global functioning.
### Global overview of Tornado.Cash functioning
@ -12,9 +14,8 @@ When a user puts funds into a pool \(a.k.a. the deposit\), a private note is gen
The strength of such a protocol comes naturally from its number of users and the size of its pool. The more users deposit into the pool the merrier. However, to preserve privacy & anonymity, the user must keep some basic rules in mind such as:
* Using a relayer to pay gas at withdrawal;
* Leaving a lapse of time between the deposit & the withdrawal action;
* Mixing its funds with the crowd by waiting for several transactions before recovering its assets.
* Leaving a lapse of time between the deposit & the withdrawal action
* Mixing its funds with the crowd by waiting for several transactions before recovering its assets.
_More recommendations are provided on:_ [_Tips to remain anonymous_](tips-to-remain-anonymous.md)_._
@ -30,7 +31,5 @@ Thanks to zk-SNARK, it is possible to prove the 20 mimc hash of the initial comm
Deposits are simple on a technological point of view, but expensive in terms of gas as they need to compute the 20 mimc hash & update the Merkle tree. At the opposite, the withdrawal process is complex, but cheaper as gas is only needed for the nullifier hash and the zero-knowledge proof.
_Written by_ [_@ayefda_](https://torn.community/u/ayefda)\_\_