diff --git a/.gitbook/assets/1 (1).png b/.gitbook/assets/1 (1).png new file mode 100644 index 0000000..5552b69 Binary files /dev/null and b/.gitbook/assets/1 (1).png differ diff --git a/.gitbook/assets/1 (2).png b/.gitbook/assets/1 (2).png new file mode 100644 index 0000000..aade76c Binary files /dev/null and b/.gitbook/assets/1 (2).png differ diff --git a/.gitbook/assets/1 (3).png b/.gitbook/assets/1 (3).png new file mode 100644 index 0000000..aade76c Binary files /dev/null and b/.gitbook/assets/1 (3).png differ diff --git a/.gitbook/assets/1.png b/.gitbook/assets/1.png new file mode 100644 index 0000000..5552b69 Binary files /dev/null and b/.gitbook/assets/1.png differ diff --git a/.gitbook/assets/1add.png b/.gitbook/assets/1add.png new file mode 100644 index 0000000..41c58ae Binary files /dev/null and b/.gitbook/assets/1add.png differ diff --git a/.gitbook/assets/2 (1).png b/.gitbook/assets/2 (1).png new file mode 100644 index 0000000..6b59183 Binary files /dev/null and b/.gitbook/assets/2 (1).png differ diff --git a/.gitbook/assets/2 (2).png b/.gitbook/assets/2 (2).png new file mode 100644 index 0000000..4b3d2e7 Binary files /dev/null and b/.gitbook/assets/2 (2).png differ diff --git a/.gitbook/assets/2.png b/.gitbook/assets/2.png index 6b59183..4b3d2e7 100644 Binary files a/.gitbook/assets/2.png and b/.gitbook/assets/2.png differ diff --git a/.gitbook/assets/2add.png b/.gitbook/assets/2add.png new file mode 100644 index 0000000..e534fc5 Binary files /dev/null and b/.gitbook/assets/2add.png differ diff --git a/.gitbook/assets/3 (1).png b/.gitbook/assets/3 (1).png new file mode 100644 index 0000000..d9f4b0f Binary files /dev/null and b/.gitbook/assets/3 (1).png differ diff --git a/.gitbook/assets/3 (2).png b/.gitbook/assets/3 (2).png new file mode 100644 index 0000000..d9f4b0f Binary files /dev/null and b/.gitbook/assets/3 (2).png differ diff --git a/.gitbook/assets/4remove.png b/.gitbook/assets/4remove.png new file mode 100644 index 0000000..1df29fe Binary files /dev/null and b/.gitbook/assets/4remove.png differ diff --git a/.gitbook/assets/5remove.png b/.gitbook/assets/5remove.png new file mode 100644 index 0000000..0662bc8 Binary files /dev/null and b/.gitbook/assets/5remove.png differ diff --git a/.gitbook/assets/aaaaaaaa (1) (1) (1) (1).gif b/.gitbook/assets/aaaaaaaa (1) (1) (1) (1).gif new file mode 100644 index 0000000..4446375 Binary files /dev/null and b/.gitbook/assets/aaaaaaaa (1) (1) (1) (1).gif differ diff --git a/SUMMARY.md b/SUMMARY.md index 3407bab..0b91807 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -9,6 +9,7 @@ * [TORN](general/torn.md) * [Governance](general/governance.md) * [Staking](general/staking.md) +* [Farming](general/farming.md) * [How to Become a Relayer?](general/how-to-become-a-relayer.md) * [Community Involvement](general/community-involvement.md) * [Tornado Cash Smart Contracts](general/tornado-cash-smart-contracts.md) @@ -24,6 +25,7 @@ * [Anonymity Mining](circuits/anonymity-mining/README.md) * [Tornado Trees](circuits/anonymity-mining/tornado-trees.md) * [Reward Claim](circuits/anonymity-mining/mining-rewards.md) + ## Tornado Cash Nova * [Logging In Tornado Cash Nova](tornado-cash-nova/logging-in-tornado-cash-nova.md) diff --git a/general/farming.md b/general/farming.md new file mode 100644 index 0000000..35d5505 --- /dev/null +++ b/general/farming.md @@ -0,0 +1,64 @@ +# Farming + +In this tutorial we will see how to add and remove liquidity on Uniswap v2 TORN/ETH pair. + +[Add liquidity](farming.md#add-liquidity) + +[Remove liquidity](farming.md#remove-liquidity) + +### Add liquidity + +1. Go there: [https://app.uniswap.org/#/add/v2/ETH?chain=mainnet](https://app.uniswap.org/#/add/v2/ETH?chain=mainnet) +2. Add the TORN and ETH pair + +![](<../.gitbook/assets/1 (3).png>) + +3\. Click on Manage + +![](../.gitbook/assets/2.png) + +4\. Click on Add + +![](<../.gitbook/assets/3 (2).png>) + +5\. Choose an amount to add and click on Supply + +![](../.gitbook/assets/1add.png) + +6\. Click on confirm + +![](../.gitbook/assets/2add.png) + + + +### Remove liquidity + +1. Go there: [https://app.uniswap.org/#/add/v2/ETH?chain=mainnet](https://app.uniswap.org/#/add/v2/ETH?chain=mainnet) +2. Add the TORN and ETH pair + +![](<../.gitbook/assets/1 (2).png>) + +3\. Click on Manage + +![](<../.gitbook/assets/2 (2).png>) + +4\. Click on Remove + +![](<../.gitbook/assets/3 (1).png>) + +5\. Choose the percentage you wish to withdraw + +### ![](../.gitbook/assets/4remove.png) + +5\. Click on confirm + +![](../.gitbook/assets/5remove.png) + + + +And that's it! :tada: + + + +_Written by_ [_**@bt11ba**_](https://torn.community/u/bt11ba/) + diff --git a/general/governance.md b/general/governance.md index bed0d2f..7a732e2 100644 --- a/general/governance.md +++ b/general/governance.md @@ -38,7 +38,7 @@ Click `Manage` -> `Lock Tab` Approve the governance contract to transfer your TORN tokens by clicking on the `Approve` button. Once the approve is confirmed, chose the amount you want to deposit and click `Lock`. Confirm the transaction in your wallet and wait for the confirmation. -![](../.gitbook/assets/c05e5a1813edad280544b627b24002dc8d5adcf2.png) +![](<../.gitbook/assets/c05e5a1813edad280544b627b24002dc8d5adcf2 (1).png>) Before the vote, the next crucial step is to review the proposal.\ Legitimate proposals should have a dedicated post on [Torn.community ](https://torn.community)under the category “Proposal”. The forum post will provide additional context and arguments on the proposal. Read the thread and make your own mind on the issue. @@ -77,7 +77,7 @@ You first need to lock your tokens in the governance contract. Click **`Manage`* Approve the governance contract to transfer your TORN tokens by clicking on the **`Approve`** button. Once the approve is confirmed, chose the amount you want to delegate and click **`Lock`**. Confirm the transaction in your wallet and wait for the confirmation. -![](<../.gitbook/assets/c05e5a1813edad280544b627b24002dc8d5adcf2 (1).png>) +![](../.gitbook/assets/c05e5a1813edad280544b627b24002dc8d5adcf2.png) The last step, is to make the actual delegation. Go again to [https://tornadocash.eth.link/governance](https://tornadocash.eth.link/governance) diff --git a/general/how-to-become-a-relayer.md b/general/how-to-become-a-relayer.md index 395ee1c..6e5448b 100644 --- a/general/how-to-become-a-relayer.md +++ b/general/how-to-become-a-relayer.md @@ -3,10 +3,10 @@ Following the execution of [Tornado Cash 10th governance proposal](https://tornadocash.eth.link/governance/10), anyone can become a relayer for Tornado Cash users. {% hint style="success" %} -The only condition to be included on the Tornado Cash UI is to lock a min. of `300 TORN`*. -To remain listed, it is needed to keep enough TORN locked (~`40 TORN` at the moment in April 2022) to be able to pay back the transaction fee to the staking contract. +The only condition to be included on the Tornado Cash UI is to lock a min. of `300 TORN`\*. To remain listed, it is needed to keep enough TORN locked (\~`40 TORN` at the moment in April 2022) to be able to pay back the transaction fee to the staking contract. {% endhint %} -**This minimum stake can be changed by a governance vote at any time.* + +\*_This minimum stake can be changed by a governance vote at any time._ Relayers form an essential & necessary part of the Tornado Cash ecosystem. Their use guarantees privacy as they solve the infamous “fee payment dilemma” : how to pay fees for token withdrawals from a pool while maintaining anonymity? @@ -42,7 +42,7 @@ The first concrete step is to run the Tornado Cash Relayer software for Ethereum Once completed, you will need to insert your url in the input box. -![](../.gitbook/assets/2.png) +![](<../.gitbook/assets/2 (1).png>) {% hint style="warning" %} It is strongly recommended that you use your own RPC nodes. Instructions on how to run full nodes can be found [here](https://github.com/feshchenkod/rpc-nodes). diff --git a/general/staking.md b/general/staking.md index 6c569d0..e08debd 100644 --- a/general/staking.md +++ b/general/staking.md @@ -8,7 +8,7 @@ Since the execution of [Tornado Cash 10th governance proposal](https://tornadoca #### **FROM WHERE THESE COLLECTED FEES COME FROM ?** -The collection of these fees was made possible by the implementation of a decentralized relayer registry. In order to be listed on the protocol UI, relayers need to stake a given amount of TORN (currently set by governance at `300 TORN`) and keep enough TORN locked (~`40 TORN` at the moment in April 2022) to be able to pay back the transaction fee to the staking contract. The functioning of this relayer registry is more extensively explained [on this forum post](https://torn.community/t/proposal-relayer-registry-setting-parameters-after-audit/2134) & on the [Relayer Registry documentation page](how-to-become-a-relayer.md). +The collection of these fees was made possible by the implementation of a decentralized relayer registry. In order to be listed on the protocol UI, relayers need to stake a given amount of TORN (currently set by governance at `300 TORN`) and keep enough TORN locked (\~`40 TORN` at the moment in April 2022) to be able to pay back the transaction fee to the staking contract. The functioning of this relayer registry is more extensively explained [on this forum post](https://torn.community/t/proposal-relayer-registry-setting-parameters-after-audit/2134) & on the [Relayer Registry documentation page](how-to-become-a-relayer.md). In a nutshell, for each withdrawal through the relayer method, the chosen relayer has to pay a fee to the protocol from the staked balance (that should still be maintained above the `300 TORN` threshold). Currently, this fee has been fixed at `0.3%` by the governance and can be changed at any time through an on-chain proposal & vote. @@ -35,8 +35,8 @@ As soon as you log in the page, you will be able to see your staking reward at t ![](<../.gitbook/assets/claim (1).png>) -_That's it, we're done, easy peasy lemon squeezy_ :wink:\_\_ +_That's it, we're done, easy peasy lemon squeezy_ :wink: \_\_ -_Written by_ [_**@bt11ba**_](https://torn.community/u/bt11ba/) _\*\*\*\* &_ [_**@ayefda**_](https://torn.community/u/ayefda)\*\*\*\* +_Written by_ [_**@bt11ba**_](https://torn.community/u/bt11ba/) _&_ [_**@ayefda**_](https://torn.community/u/ayefda)