post-censorship guide faqs
This commit is contained in:
gozzy
parent
5f24eb7837
commit
68e22a522d
Binary file not shown.
|
After Width: | Height: | Size: 26 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 17 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 38 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 44 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 14 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 46 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 1.6 MiB |
Binary file not shown.
|
After Width: | Height: | Size: 12 KiB |
|
|
@ -2,11 +2,13 @@
|
|||
|
||||
This is a guide to using Tornado Cash after the 8th August crisis, when the OFAC decided to sanction the organisation and the smart contracts. This led to a widespread wave of censorship from middleware service providers, resulting in users being vulnerable and unable to access their assets.
|
||||
|
||||
-------
|
||||
### LANGUAGE: |<ul class="langs"><li class="lang-p">ENG*</li><li class="lang-p"><a href="https://hackmd.io/@gozzy/tornado-cash-制裁后教程">ZH</a></li><li class="lang-p"><a href="https://hackmd.io/@gozzy/tornado-cash-tras-la-censura">ES</a></li><li class="lang-p"><a href="https://hackmd.io/@gozzy/tornado-cash-после-цензуры">RU</a></li></ul>
|
||||
-------
|
||||
--------
|
||||
|
||||
## Community build
|
||||
> <h4>LANGUAGE: <a href="https://hackmd.io/@gozzy/tornado-cash-制裁后教程">ZH</a> | <a href="https://hackmd.io/@gozzy/tornado-cash-tras-la-censura">ES</a> | <a href="https://hackmd.io/@gozzy/tornado-cash-после-цензуры">RU</a> </h4>
|
||||
|
||||
--------
|
||||
|
||||
### Community build
|
||||
|
||||
_The source code for the community build can be found on [the offical community git](https://development.tornadocash.community/tornadocash/classic-ui). For a tutorial on how to audit the changes [see Micah's guide](https://notes.ethereum.org/@GW1ZUbNKR5iRjjKYx6_dJQ/Bk8zsJ9xj)_.
|
||||
|
||||
|
|
@ -15,7 +17,7 @@ _The source code for the community build can be found on [the offical community
|
|||
|
||||
**See [instructions on RPC configuration](#RPC) if transacting with sanctioned addresses**
|
||||
|
||||
### ENS resolvers
|
||||
#### ENS resolvers
|
||||
|
||||
The latest community builds are available at:
|
||||
|
||||
|
|
@ -27,7 +29,7 @@ The latest community builds are available at:
|
|||
* [nova.tornadocashcommunity.eth.link](https://nova.tornadocashcommunity.eth.link)
|
||||
|
||||
|
||||
### TOR network
|
||||
#### TOR network
|
||||
|
||||
**Browser history must be enabled when using TOR browser for event caching**.
|
||||
|
||||
|
|
@ -38,7 +40,7 @@ It is now possible to access the builds via onion hidden services with the commu
|
|||
* [onion.nova.tornadocash.3th.ws](https://onion.nova.tornadocash.3th.ws)
|
||||
* [y7ghfvm6jlgfvx25sy5l7muvqnqkw37jjbmzbikpn6sfma65dp3qysqd.onion](https://y7ghfvm6jlgfvx25sy5l7muvqnqkw37jjbmzbikpn6sfma65dp3qysqd.onion)
|
||||
|
||||
### IPFS details
|
||||
#### IPFS details
|
||||
|
||||
|
||||
To get the IPFS content hash and link from the domain details. Visit the ENS application domain page at either:
|
||||
|
|
@ -55,7 +57,7 @@ ipfs://bafybeiguelxw5aanwnhvaea5vjhknmcdmwvujne36wgabnkmcbt3563toa
|
|||
The content hash of this link is `bafybeiguelxw5aanwnhvaea5vjhknmcdmwvujne36wgabnkmcbt3563toa`
|
||||
|
||||
|
||||
### Local IPFS deployment (recommended)
|
||||
#### Local IPFS deployment (recommended)
|
||||
|
||||
* Brave
|
||||
* Navigate to the IPFS link in the browser
|
||||
|
|
@ -67,7 +69,7 @@ The content hash of this link is `bafybeiguelxw5aanwnhvaea5vjhknmcdmwvujne36wgab
|
|||
* Ensure IPFS Desktop is open and has an internet connection
|
||||
* Navigate to the IPFS link in the browser
|
||||
|
||||
### IPFS gateway usage
|
||||
#### IPFS gateway usage
|
||||
|
||||
* Take the content hash and prefix it followed by a `.` to one of the following IPFS gateways:
|
||||
* `ipfs.dweb.link`
|
||||
|
|
@ -78,51 +80,53 @@ The content hash of this link is `bafybeiguelxw5aanwnhvaea5vjhknmcdmwvujne36wgab
|
|||
* https://bafybeiguelxw5aanwnhvaea5vjhknmcdmwvujne36wgabnkmcbt3563toa.ipfs.cf-ipfs.com
|
||||
|
||||
|
||||
## RPC
|
||||
### RPC
|
||||
|
||||
-------
|
||||
### LANGUAGE: |<ul class="langs"><li class="lang-p">ENG*</li><li class="lang-p"><a href="https://hackmd.io/@gozzy/tornado-cash-制裁后教程">ZH</a></li><li class="lang-p"><a href="https://hackmd.io/@gozzy/tornado-cash-tras-la-censura">ES</a></li><li class="lang-p"><a href="https://hackmd.io/@gozzy/tornado-cash-после-цензуры">RU</a></li></ul>
|
||||
--------
|
||||
|
||||
<h4>LANGUAGE: <a href="https://hackmd.io/@gozzy/tornado-cash-制裁后教程">ZH</a> | <a href="https://hackmd.io/@gozzy/tornado-cash-tras-la-censura">ES</a> | <a href="https://hackmd.io/@gozzy/tornado-cash-после-цензуры">RU</a> </h4>
|
||||
|
||||
--------
|
||||
|
||||
|
||||
* If you want to deposit you may have to change your wallet RPC, as most providers have censored the smart contracts. One of these providers is Infura, which Metamask uses by default.
|
||||
|
||||
* Try searching for a working endpoint on [Chainlist](https://chainlist.org/), which could take multiple attempts (take note of the ChainID for network configuration). An example of how to change your RPC provider for MetaMask is shown below.
|
||||
|
||||
|
||||
|
||||
|
||||
* Sometimes visiting the application you could be greeted with the following message, to fix this click "OPEN SETTINGS".
|
||||
|
||||
|
||||
|
||||
|
||||
* You'll then be displayed a dropdown selection, defaulted to a selection. Click on it and select the "Custom" option.
|
||||
|
||||
|
||||
|
||||
|
||||
* Here enter a non-censoring RPC provider depending on your network and this will resolve application issues.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
* Then you are freely able to withdraw, deposit, stake or participate in decentralised governance like nothing ever happened.
|
||||
|
||||
<style>
|
||||
.langs {
|
||||
width: calc(79% - 50px);
|
||||
list-style-type: none;
|
||||
display: inline-block;
|
||||
padding: 0px !important;
|
||||
margin: 0px !important;
|
||||
margin-bottom: -5px !important;
|
||||
}
|
||||
### FAQ
|
||||
|
||||
.lang-p {
|
||||
float:left;
|
||||
margin-left: 10%;
|
||||
padding: 0px !important;
|
||||
}
|
||||
> Why do I keep recieving the error `Failed to fetch relayers`?
|
||||
|
||||
.lang-p:after {
|
||||
content: "|";
|
||||
margin-left: 4rem;
|
||||
}
|
||||
</style>
|
||||
* This error is either related to a poor connection or a result of no available relayers on your network. It usually can be solved by refreshing.
|
||||
|
||||
> Why do I keep recieving the error `Failed to fetch proving keys`?
|
||||
|
||||
* This error is either related to a poor connection, it usually can be solved by refreshing or changing VPN location for better latency.
|
||||
|
||||
> Why do I keep recieving the error `Failed to fetch all deposit events` when trying to withdraw?
|
||||
|
||||
* This error is related to a poor connection or using a censored RPC endpoint. To resolve this either:
|
||||
* change VPN location for better latency
|
||||
* try a new browser or method of access
|
||||
* configure the application RPC configuration to an alternative
|
||||
|
||||
> Why can't make a deposit from my wallet?
|
||||
|
||||
* Most RPCs censor transactions to the protocol and governance since the OFAC sanctions, you need to configure your wallet RPC to a uncensored endpoint.
|
||||
Loading…
Reference in New Issue