guides: post censorship zh, es, ru
This commit is contained in:
gozzy
parent
d567397d31
commit
e7d4faee75
@ -23,14 +23,14 @@ As mentioned before most operating systems support unpacking .zip files, so open
|
||||
### Step #3: Install the Web Server extension
|
||||
Open up Google Chrome and navigate to the [Web Server extension page](https://chrome.google.com/webstore/detail/web-server-for-chrome/ofhbbkphhbklhfoeikjpcbhemlocgigb/related?hl=en), click the button highlighted in the image to install. Once installed, click the same button which should now say ¨Launch app¨ to launch the extension.
|
||||
|
||||
|
||||
|
||||
|
||||
### Step #4: Configure the Web Server extension
|
||||
If everything is going correctly you should see a similar screen, firstly click the "Select folder" button (1) and select the folder that was created after the .zip file was opened. It should be in the same location where you downloaded it to. Then once it has been loaded click the link underneath (2) to view the hosted content.
|
||||
|
||||
|
||||
|
||||
|
||||
### Step #5: Achieve privacy
|
||||
If you can see the frontend interface after clicking the link in the extension then you've successfully done everything correctly and you can use the protocol like normal.
|
||||
|
||||
|
||||
|
||||
@ -2,6 +2,14 @@
|
||||
|
||||
While the protocol breaks the links between source and destination addresses when appeared on-chain, there is countless areas where individuals can disclose information about their identity when accessing the protocol through middleware like RPC endpoints, hosted web instances and top level domains.
|
||||
|
||||
### Local deployment
|
||||
|
||||
Local serving user interfaces or using the CLI tool are the best way to use the protocol to maintain a low profile and prevent phishing, if you are not technical you can still easily use IPFS companion browser extension to locally deploy with ease.
|
||||
|
||||
### Browser
|
||||
|
||||
Google Chrome runs background analytics services on it's production release which breaches individual privacy. This is also the case for many browser extensions, as permission is usually required to caches and cookies. Use open source extensions and browsers like Firefox or TOR and reduce browser tracking.
|
||||
|
||||
### VPN
|
||||
|
||||
Proxy servers that help mask your internet traffic and location, although purely are operated on a trust basis with the provider. Avoid using free VPNs, they tend to keep or even sell your data. VPNs are not a solution to anonymising your data and are always recommended to use in combination with other tooling. Wireguard is the latest standard when it comes VPN networking protocols.
|
||||
@ -18,23 +26,30 @@ Using onion routing, you can singificantly mask your internet traffic at the cos
|
||||
|
||||
Your note provides a record of your original transaction. Anyone who has it can withdraw the funds deposited, but also know the details regarding the depositing address therefore allowing the ability to deanonymise the transaction.
|
||||
|
||||
### Delete cache and history
|
||||
### Delete history, cache and cookies
|
||||
|
||||
Browser history and caches can provide a massive amount of data regarding specific behaviourial patterns and timestamps. It is common for browser extensions have read access permissiones to your cache. If two transfers are made with the same cookies, the extension you are using will be able to link these two transactions.
|
||||
Browser history and caches can provide a massive amount of data regarding specific behaviourial patterns and timestamps. It is common for browser extensions have read access permissiones to your cache. **If transactions of two independent addresses are made with the same cookies, the extension will be able to link the wallets**.
|
||||
|
||||
### Wallet
|
||||
|
||||
Metamask now by default, logs IP addresses **when a wallet is generated or makes a transaction** please excercise caution if you are using this choice as a wallet and do not take methods to migitate the logging. It would effectively void any anonymity acheived on-chain, if your actual IP address is exposed.
|
||||
Metamask one of the most popular wallets - now by default, **logs IP addresses when a wallet is generated or makes a transaction** please excercise caution if you are using this choice as a wallet and do not take methods to migitate the logging. It would effectively void any anonymity acheived on-chain, if your actual IP address is exposed.
|
||||
|
||||
Additionally when you configure an Metamask wallet an Infura RPC access key is assigned to your instance, **if you make two transactions from two seperate addresses from that instance they will be directly related**. It is recommended to delete and reintall the extension when transacting from the source and destination address to ensure a fresh access key and not void your destination address's anonymity.
|
||||
|
||||
It is recommended to use open source wallets to evade the surveilance present in the adopoted software like the following recommendations:
|
||||
|
||||
* [Frame](https://github.com/floating/frame)
|
||||
* [Enkrypt](https://github.com/enkryptcom/enKrypt)
|
||||
* [Tally Ho](https://tallyhowallet/extension)
|
||||
|
||||
Additionally when you configure an Metamask wallet an Infura RPC access key is assigned to your instance, **if you make two transactions from two seperate addresses from that instance they will be directly related**. It is recommended to delete and reintall the extension for every address you wish to transact from to ensure a fresh access key.
|
||||
|
||||
### Wait for subsequent deposits
|
||||
|
||||
Your anonymity also depends on the number of transactions after your deposit (statistics tab). If you withdraw your funds immediately after depositing them, it is possible to link your deposit to your transfer using correlation probabilities. The longer you wait, the greater your anonymity set will be.
|
||||
Your anonymity also depends on the number of transactions after your deposit (statistics tab). If you withdraw your funds immediately after depositing them, it is possible to link your deposit to your withdrawal using correlation probabilities. **The greater the amount of deposits after your deposit, the greater your anonymity set will be.**
|
||||
|
||||
### Use multiple addresses
|
||||
|
||||
If an inidivudal makes 7 x 10 ETH deposit from one address and then makes 7 x 10 ETH withdrawals to a single address, it highly indicates an association - remember to use multiple withdrawal addresses to fragment original depositing amounts.
|
||||
If you make 7 x 10 ETH deposit from one address and withdraw all 10 ETH notes to a single destination address - **it indicates a clear association** - remember to use multiple withdrawal addresses to fragment the original depositing amounts.
|
||||
|
||||
### Use different gas parameters
|
||||
|
||||
@ -44,6 +59,10 @@ Behavioural patterns in consisent gas values can be used to fingerprint transact
|
||||
|
||||
As privacy through the protocol is achieved probabilistically, the more activity and volumes a specific anonymity set has - the better the potential for anonymity. Select the popular anonymity sets to hide in with the crowd.
|
||||
|
||||
### Fragment deposits
|
||||
|
||||
The lower denomination anonymity sets have always been the most active, if you have a balance desired to shield refrain from depositing independently into the largest anonymity set. **It is more effective to break up your deposit into smaller denominations which will greatly increase your anonymity but comes at the cost of more fees.**
|
||||
|
||||
### Do not repeatively process withdrawals through the same relayer
|
||||
|
||||
Only processing withdrawals through a singular relayer, oses a risk to behavioural pattern profiling. Ensure you are using different relayers for every withdrawal if you want to diassociate two withdrawal addresses from one another.
|
||||
|
||||
115
general/guides/post-censorship/es.md
Normal file
115
general/guides/post-censorship/es.md
Normal file
@ -0,0 +1,115 @@
|
||||
# Uso de Tornado Cash tras la censura
|
||||
|
||||
Esta es una guía para usar Tornado Cash después de la crisis del 8 de agosto, cuando la OFAC decidió sancionar a la organización y a los contratos. Esto generó una ola de censura generalizada de los proveedores de servicios. Como resultado los usuarios son vulnerables y no pueden acceder a sus fondos.
|
||||
|
||||
## Compilación de la comunidad
|
||||
|
||||
El código fuente de la compilación de la comunidad se puede encontrar en [el git oficial de la comunidad](https://development.tornadocash.community/tornadocash/classic-ui). Para un tutorial sobre cómo auditar los cambios mirá [la guía de Micah](https://notes.ethereum.org/@GW1ZUbNKR5iRjjKYx6_dJQ/Bk8zsJ9xj).
|
||||
|
||||
* Versión actual de compilación **ea97a39**
|
||||
* Registro de cambios: [#003](https://development.tornadocash.community/tornadocash/classic-ui/pulls/10)
|
||||
|
||||
**Consulte [las instrucciones sobre cómo configurar RPC](#RPC) si está realizando transacciones con direcciones sancionadas.**
|
||||
|
||||
### Contenido y resolutores de ENS
|
||||
La últimas compilaciones de la comunidad deberían estar disponibles en:
|
||||
|
||||
* Classic:
|
||||
* [tornadocash.3th.ws](https://tornadocash.3th.ws) (recomendado)
|
||||
* [tornadocashcommunity.eth.link](https://tornadocashcommunity.eth.link)
|
||||
* Nova:
|
||||
* [nova.tornadocash.3th.ws](https://nova.tornadocash.3th.ws) (recomendado)
|
||||
* [nova.tornadocashcommunity.eth.link](https://nova.tornadocashcommunity.eth.link)
|
||||
|
||||
### TOR de la red
|
||||
|
||||
**El historial del navegador debe estar habilitado al usar el navegador TOR para el almacenamiento en caché de eventos**.
|
||||
|
||||
Ahora es posible acceder a las compilaciones a través de los servicios ocultos de cebolla con el solucionador de la comunidad (3th.ws), si no hay respuesta, consulte la [página de estado de la red](https://status.torproject.org) para posibles interrupciones.
|
||||
|
||||
* [onion.tornadocash.3th.ws](https://onion.tornadocash.3th.ws)
|
||||
* [h76qqhctmyehsaoazm7fqtncitt3vrdixoshwhuu7vpgzh3mld7dt2qd.onion](https://h76qqhctmyehsaoazm7fqtncitt3vrdixoshwhuu7vpgzh3mld7dt2qd.onion/)
|
||||
* [onion.nova.tornadocash.3th.ws](https://onion.nova.tornadocash.3th.ws)
|
||||
* [tytltckkqi3g6djjmiaorobu5jgshgwpdqelgmdcabnp2l7whj6sdhid.onion](https://tytltckkqi3g6djjmiaorobu5jgshgwpdqelgmdcabnp2l7whj6sdhid.onion)
|
||||
|
||||
### Detalles de IPFS
|
||||
|
||||
Si no podés acceder a estos enlaces, deberás obtener el hash del contenido IPFS y el enlace desde los detalles del dominio. Visitá la página del dominio de la aplicación ENS en:
|
||||
|
||||
* Classic: [tornadocash.eth](https://app.ens.domains/name/tornadocash.eth/details)
|
||||
* Nova: [nova.tornadocash.eth](https://app.ens.domains/name/nova.tornadocashcommunity.eth/details)
|
||||
|
||||
El enlace IPFS para Classic (tornadocash.eth), por ejemplo, va a tener el siguiente aspecto:
|
||||
|
||||
```
|
||||
ipfs://bafybeiguelxw5aanwnhvaea5vjhknmcdmwvujne36wgabnkmcbt3563toa
|
||||
```
|
||||
|
||||
El hash de contenido de este enlace es `bafybeiguelxw5aanwnhvaea5vjhknmcdmwvujne36wgabnkmcbt3563toa`
|
||||
|
||||
### Despliegue local de IPFS (recomendado)
|
||||
|
||||
* Brave
|
||||
* Navegá hacia el enlace IPFS en el navegador
|
||||
* Cuando se solicite, seleccioná “Use a Brave local IPFS node" -usar un nodo IPFS local de Brave-.
|
||||
|
||||
* Chrome / Firefox
|
||||
* Instalar IPFS Desktop
|
||||
* Instalar la extensión IPFS Companion ([Chrome](https://chrome.google.com/webstore/detail/ipfs-companion/nibjojkomfdiaoajekhjakgkdhaomnch?hl=es) / [Firefox](https://addons.mozilla.org/es/firefox/addon/ipfs-companion/))
|
||||
* Asegurate que IPFS Desktop está abierto y con conexión a internet
|
||||
* Navegá hacia el enlace IPFS en el navegador
|
||||
|
||||
### Uso de la puerta de enlace de IPFS
|
||||
|
||||
Toma el hash del contenido, añade un . y a continuación adhiere una de las siguientes puertas de enlace de IPFS:
|
||||
|
||||
* `ipfs.dweb.link`
|
||||
* https://bafybeiguelxw5aanwnhvaea5vjhknmcdmwvujne36wgabnkmcbt3563toa.ipfs.dweb.link
|
||||
* `ipfs.tornadocash.is` (puerta de enlace de la comunidad)
|
||||
* https://bafybeiguelxw5aanwnhvaea5vjhknmcdmwvujne36wgabnkmcbt3563toa.ipfs.tornadocash.is
|
||||
* `ipfs.cf-ipfs.com`
|
||||
* https://bafybeiguelxw5aanwnhvaea5vjhknmcdmwvujne36wgabnkmcbt3563toa.ipfs.cf-ipfs.com
|
||||
|
||||
|
||||
## RPC
|
||||
|
||||
* Si desea depositar, es posible que deba cambiar su RPC de billetera, ya que la mayoría de los proveedores han censurado los contratos inteligentes. **El proveedor predeterminado de Metamask, Infura junto con Ankr y Alchemy no prohíben las transacciones hacia y desde el protocolo, la gobernanza y el token TORN**.
|
||||
|
||||
* Intentá buscar en Chainlist un endpoint (punto final) que funcione, esto podría llevar varios intentos (anotá el ChainID para configurar la red). A continuación se muestra un ejemplo de cómo cambiar el proveedor RPC para MetaMask.
|
||||
|
||||
|
||||
|
||||
* A veces al visitar la aplicación puede aparecer el siguiente mensaje, para solucionarlo haga clic en "OPEN SETTINGS" -abrir ajustes-.
|
||||
|
||||
|
||||
|
||||
* A continuación, aparecerá un desplegable con una selección por defecto. Hacé clic en él y seleccioná la opción "Custom" -personalizada-.
|
||||
|
||||
|
||||
|
||||
* Introducí aquí un proveedor de RPC sin censura dependiendo de tu red y esto resolverá los problemas de la aplicación.
|
||||
|
||||
|
||||
|
||||
* Ahora podés retirar, depositar, hacer staking o participar libremente en la gobernanza descentralizada como si nunca hubiera pasado nada.
|
||||
|
||||
## FAQ
|
||||
|
||||
> ¿Por qué sigo recibiendo el error `Failed to fetch relayers`?
|
||||
|
||||
* Este error está relacionado con una mala conexión o como resultado de que no hay repetidores disponibles en su red. Por lo general, se puede resolver refrescando.
|
||||
|
||||
> ¿Por qué sigo recibiendo el error `Failed to fetch proving keys`?
|
||||
|
||||
* Este error está relacionado con una mala conexión, por lo general se puede resolver actualizando o cambiando la ubicación de VPN para una mejor latencia.
|
||||
|
||||
> ¿Por qué sigo recibiendo el error `Failed to fetch all deposit events from contract` cuando intento retirar dinero?
|
||||
|
||||
* Este error está relacionado con una mala conexión o con el uso de un extremo RPC censurado. Para resolver esto:
|
||||
* cambiar la ubicación de VPN para una mejor latencia
|
||||
* probar un nuevo navegador o método de acceso
|
||||
* configure la configuración RPC de la aplicación a una alternativa
|
||||
|
||||
> ¿Por qué no puedo hacer un depósito desde mi monedero?
|
||||
|
||||
* La mayoría de los RPC censuran las transacciones según el protocolo y la gobernanza desde las sanciones de la OFAC, debe configurar su RPC de billetera en un punto final sin censura.
|
||||
@ -1,10 +1,10 @@
|
||||
# Tornado Cash usage post-censorship
|
||||
# Tornado Cash post-censorship
|
||||
|
||||
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.
|
||||
|
||||
--------
|
||||
|
||||
<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>
|
||||
**LANGUAGE: [ZH](zh.md) | [ES](es.md) | [RU](ru.md) **
|
||||
|
||||
--------
|
||||
|
||||
@ -36,13 +36,12 @@ The latest community builds are available at:
|
||||
It is now possible to access the builds via onion hidden services with the community resolver (3th.ws), if there is no response see the [network status page](https://status.torproject.org/) for possible disruption.
|
||||
|
||||
* [onion.tornadocash.3th.ws](https://onion.tornadocash.3th.ws)
|
||||
* [fueywrkuuqfikscslaavck762p6xr7fiiakrb2uy3acne4z67jeanqid.onion](https://fueywrkuuqfikscslaavck762p6xr7fiiakrb2uy3acne4z67jeanqid.onion)
|
||||
* [h76qqhctmyehsaoazm7fqtncitt3vrdixoshwhuu7vpgzh3mld7dt2qd.onion](https://h76qqhctmyehsaoazm7fqtncitt3vrdixoshwhuu7vpgzh3mld7dt2qd.onion/)
|
||||
* [onion.nova.tornadocash.3th.ws](https://onion.nova.tornadocash.3th.ws)
|
||||
* [y7ghfvm6jlgfvx25sy5l7muvqnqkw37jjbmzbikpn6sfma65dp3qysqd.onion](https://y7ghfvm6jlgfvx25sy5l7muvqnqkw37jjbmzbikpn6sfma65dp3qysqd.onion)
|
||||
* [tytltckkqi3g6djjmiaorobu5jgshgwpdqelgmdcabnp2l7whj6sdhid.onion](https://tytltckkqi3g6djjmiaorobu5jgshgwpdqelgmdcabnp2l7whj6sdhid.onion)
|
||||
|
||||
#### IPFS details
|
||||
|
||||
|
||||
To get the IPFS content hash and link from the domain details. Visit the ENS application domain page at either:
|
||||
|
||||
* Classic: [tornadocash.eth](https://app.ens.domains/name/tornadocash.eth/details)
|
||||
@ -84,33 +83,32 @@ The content hash of this link is `bafybeiguelxw5aanwnhvaea5vjhknmcdmwvujne36wgab
|
||||
|
||||
--------
|
||||
|
||||
<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>
|
||||
**LANGUAGE: [ZH](zh.md) | [ES](es.md) | [RU](ru.md) **
|
||||
|
||||
--------
|
||||
|
||||
|
||||
* 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.
|
||||
* If you want to deposit you may have to change your wallet RPC, as most providers have censored the smart contracts. **The default provider of Metamask, Infura along with Ankr and Alchemy do not prohibit transactions to and from the protocol, governance and the TORN token**.
|
||||
|
||||
* 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.
|
||||
* Try searching for an alternative 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.
|
||||
|
||||
### FAQ
|
||||
## FAQ
|
||||
|
||||
> Why do I keep recieving the error `Failed to fetch relayers`?
|
||||
|
||||
@ -120,13 +118,13 @@ The content hash of this link is `bafybeiguelxw5aanwnhvaea5vjhknmcdmwvujne36wgab
|
||||
|
||||
* 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?
|
||||
> Why do I keep recieving the error `Failed to fetch all deposit events from contract` 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?
|
||||
> Why can't I 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.
|
||||
* Most RPCs censor transactions to the protocol and governance since the OFAC sanctions, you need to configure your wallet RPC to a uncensored endpoint. .
|
||||
116
general/guides/post-censorship/ru.md
Normal file
116
general/guides/post-censorship/ru.md
Normal file
@ -0,0 +1,116 @@
|
||||
# Tornado Cash после цензуры
|
||||
|
||||
Это руководство по использованию Tornado Cash после кризиса 8 августа, когда OFAC решило ввести санкции против организации и смарт-контрактов. Это привело к широко распространенной волне цензуры со стороны поставщиков услуг. В результате пользователи становятся уязвимыми и не могут получить доступ к своим средствам.
|
||||
|
||||
## Версия сообщества
|
||||
|
||||
Исходный код сборки сообщества можно найти на официальном [сайте сообщества git](https://development.tornadocash.community/tornadocash/classic-ui). Руководство по аудиту изменений см. в [руководстве Micah](https://notes.ethereum.org/@GW1ZUbNKR5iRjjKYx6_dJQ/Bk8zsJ9xj).
|
||||
|
||||
* Текущая версия: **ea97a39**
|
||||
* журнал изменений: [#003](https://development.tornadocash.community/tornadocash/classic-ui/pulls/10)
|
||||
|
||||
**См. [Инструкции по настройке RPC](#RPC) при выполнении транзакций с адресами, санкционированными OFAC**.
|
||||
|
||||
### Контент ENS
|
||||
|
||||
Последняя версия сообщества должна быть доступна по адресу:
|
||||
|
||||
* Classic:
|
||||
* [tornadocash.3th.ws](https://tornadocash.3th.ws) (рекомендуется)
|
||||
* [tornadocashcommunity.eth.link](https://tornadocashcommunity.eth.link)
|
||||
* Nova:
|
||||
* [nova.tornadocash.3th.ws](https://nova.tornadocash.3th.ws) (рекомендуется)
|
||||
* [nova.tornadocashcommunity.eth.link](https://nova.tornadocashcommunity.eth.link)
|
||||
|
||||
|
||||
### TOR сеть
|
||||
|
||||
**История браузера должна быть включена при использовании браузера TOR для кэширования событий**.
|
||||
|
||||
Теперь можно получить доступ через скрытые сервисы onion с помощью распознавателя сообщества (3th.ws), если нет ответа, см. [страницу состояния сети](https://status.torproject.org/) для возможных сбоев.
|
||||
|
||||
* [onion.tornadocash.3th.ws](https://onion.tornadocash.3th.ws)
|
||||
* [h76qqhctmyehsaoazm7fqtncitt3vrdixoshwhuu7vpgzh3mld7dt2qd.onion](https://h76qqhctmyehsaoazm7fqtncitt3vrdixoshwhuu7vpgzh3mld7dt2qd.onion/)
|
||||
* [onion.nova.tornadocash.3th.ws](https://onion.nova.tornadocash.3th.ws)
|
||||
* [tytltckkqi3g6djjmiaorobu5jgshgwpdqelgmdcabnp2l7whj6sdhid.onion](https://tytltckkqi3g6djjmiaorobu5jgshgwpdqelgmdcabnp2l7whj6sdhid.onion)
|
||||
|
||||
|
||||
### IPFS подробности
|
||||
|
||||
Если у вас нет доступа к этим ссылкам, вам необходимо получить хэш содержимого IPFS и ссылку из сведений о домене. Посетите страницу доменов приложений ENS:
|
||||
|
||||
* Сlassic: [tornadocash.eth](https://app.ens.domains/name/tornadocash.eth/details)
|
||||
* Nova: [nova.tornadocash.eth](https://app.ens.domains/name/nova.tornadocash.eth/details)
|
||||
|
||||
|
||||
Например, ссылка IPFS для Classic (tornadocash.eth) будет выглядеть так:
|
||||
```
|
||||
ipfs://bafybeiguelxw5aanwnhvaea5vjhknmcdmwvujne36wgabnkmcbt3563toa
|
||||
```
|
||||
|
||||
Хэш содержимого этой ссылки: `bafybeiguelxw5aanwnhvaea5vjhknmcdmwvujne36wgabnkmcbt3563toa`.
|
||||
|
||||
#### Локальное развертывание IPFS (рекомендуется)
|
||||
|
||||
* Brave
|
||||
* Перейдите по ссылке IPFS в браузере.
|
||||
* При появлении запроса выберите «Использовать локальный узел Brave IPFS».
|
||||
|
||||
* Chrome / Firefox
|
||||
* Установите рабочий стол IPFS
|
||||
* Установите расширение IPFS Companion ([Chrome](https://chrome.google.com/webstore/detail/ipfs-companion/nibjojkomfdiaoajekhjakgkdhaomnch?hl=ru) / [Firefox](https://addons.mozilla.org/ru/firefox/addon/ipfs-companion/))
|
||||
* Убедитесь, что рабочий стол IPFS открыт и имеет подключение к Интернету.
|
||||
* Перейдите по ссылке IPFS в браузере.
|
||||
|
||||
#### Проверка и использование шлюза IPFS
|
||||
|
||||
* Возьмите хеш содержимого и добавьте к нему префикс, за которым следует расширение . к одному из следующих шлюзов IPFS:
|
||||
* `ipfs.dweb.link`
|
||||
* https://bafybeiguelxw5aanwnhvaea5vjhknmcdmwvujne36wgabnkmcbt3563toa.ipfs.dweb.link
|
||||
* `ipfs.tornadocash.is` (шлюз сообщества)
|
||||
* https://bafybeiguelxw5aanwnhvaea5vjhknmcdmwvujne36wgabnkmcbt3563toa.ipfs.tornadocash.is
|
||||
* `ipfs.cf-ipfs.com`
|
||||
* https://bafybeiguelxw5aanwnhvaea5vjhknmcdmwvujne36wgabnkmcbt3563toa.ipfs.cf-ipfs.com
|
||||
|
||||
## RPC
|
||||
|
||||
* Если вы хотите внести депозит, вам, возможно, придется изменить RPC вашего кошелька, так как большинство провайдеров подвергают смарт-контракты цензуре. **Поставщик Metamask по умолчанию, Infura, наряду с Ankr и Alchemy, не запрещает транзакции между протоколом, управлением и токеном TORN**.
|
||||
|
||||
* Попробуйте найти работающую конечную точку в [chainlist.org](https://chainlist.org), что может потребовать нескольких попыток (обратите внимание на ChainID для настройки сети). Пример того, как изменить поставщика RPC для MetaMask, показан ниже.
|
||||
|
||||
|
||||
|
||||
* Иногда при посещении приложения вас могло встречать следующее сообщение, для исправления нажмите "ОТКРЫТЬ НАСТРОЙКИ".
|
||||
|
||||
|
||||
|
||||
* Затем вам отобразится раскрывающийся список, по умолчанию выбранный. Нажмите на него и выберите опцию "Пользовательский".
|
||||
|
||||
|
||||
|
||||
* Здесь введите поставщика RPC без цензуры в зависимости от вашей сети, и это решит проблемы с приложением.
|
||||
|
||||
|
||||
|
||||
* Затем вы можете свободно снимать средства, вносить депозиты или участвовать в децентрализованном управлении, как будто ничего не произошло.
|
||||
|
||||
## FAQ
|
||||
|
||||
> Почему я постоянно получаю сообщение об ошибке `Failed to fetch relayers`?
|
||||
|
||||
* Эта ошибка возникает либо из-за плохого соединения, либо из-за отсутствия ретрансляторов в сети. Обычно это решается обновлением.
|
||||
|
||||
> Почему я постоянно получаю сообщение об ошибке `Failed to fetch proving keys`?
|
||||
|
||||
* Эта ошибка возникает либо из-за плохого соединения, обычно ее можно решить, обновив или изменив местоположение VPN для лучшей задержки.
|
||||
|
||||
> Почему я постоянно получаю сообщение об ошибке `Failed to fetch all deposit events from contract` при попытке вывести средства?
|
||||
|
||||
* Эта ошибка возникает из-за плохого соединения или использования цензурированной конечной точки RPC. Чтобы решить это либо:
|
||||
* изменить местоположение VPN для лучшей задержки
|
||||
* попробуйте новый браузер или метод доступа
|
||||
* установить альтернативную конфигурацию приложения RPC
|
||||
|
||||
> Почему я не могу внести депозит со своего кошелька?
|
||||
|
||||
* Большинство RPC подвергают цензуре протокол и транзакции управления, поскольку OFAC налагает санкции, вам необходимо настроить RPC вашего кошелька на не подвергаемую цензуре конечную точку.
|
||||
117
general/guides/post-censorship/zh.md
Normal file
117
general/guides/post-censorship/zh.md
Normal file
@ -0,0 +1,117 @@
|
||||
# Tornado Cash 制裁后教程
|
||||
|
||||
这是8月8日危机后使用龙卷风现金的指南。 当OFAC决定制裁组织和智能合约时。 这导致了广泛的审查制度。 结果，用户很脆弱，无法访问其资金。
|
||||
|
||||
## 社区应用
|
||||
|
||||
社区构建的源代码可以在官方社区 [git 上找到。](https://development.tornadocash.community/tornadocash/classic-ui) 有关如何查看更改的教程，请参阅 [Micah 的指南](https://notes.ethereum.org/@GW1ZUbNKR5iRjjKYx6_dJQ/Bk8zsJ9xj)。
|
||||
|
||||
* 当前构建版本：**ea97a39**
|
||||
* 更改日志: [#003](https://development.tornadocash.community/tornadocash/classic-ui/pulls/10)
|
||||
|
||||
**如果使用受制裁的地址进行交易，请参阅 [RPC 配置说明](#RPC)**。
|
||||
|
||||
### ENS 内容
|
||||
|
||||
最新的社区版本应在以下位置提供：
|
||||
|
||||
* Classic:
|
||||
* [tornadocash.3th.ws](https://tornadocash.3th.ws)（推荐）
|
||||
* [tornadocashcommunity.eth.link](https://tornadocashcommunity.eth.link)
|
||||
* Nova:
|
||||
* [nova.tornadocash.3th.ws](https://nova.tornadocash.3th.ws)（推荐）
|
||||
* [nova.tornadocashcommunity.eth.link](https://nova.tornadocashcommunity.eth.link)
|
||||
|
||||
### TOR 网络
|
||||
|
||||
**如果您使用的是 TOR 浏览器，请启用浏览器历史记录，否则事件将不会被缓存。**
|
||||
|
||||
现在可以使用社区解析器 (3th.ws) 通过洋葱隐藏服务访问构建，如果没有响应，请查看 [网络状态页面](https://status.torproject.org/) 以了解可能的中断。
|
||||
|
||||
* [onion.tornadocash.3th.ws](https://onion.tornadocash.3th.ws)
|
||||
* [h76qqhctmyehsaoazm7fqtncitt3vrdixoshwhuu7vpgzh3mld7dt2qd.onion](https://h76qqhctmyehsaoazm7fqtncitt3vrdixoshwhuu7vpgzh3mld7dt2qd.onion/)
|
||||
* [onion.nova.tornadocash.3th.ws](https://onion.nova.tornadocash.3th.ws)
|
||||
* [tytltckkqi3g6djjmiaorobu5jgshgwpdqelgmdcabnp2l7whj6sdhid.onion](https://tytltckkqi3g6djjmiaorobu5jgshgwpdqelgmdcabnp2l7whj6sdhid.onion)
|
||||
|
||||
### IPFS 详情
|
||||
|
||||
如果您无法访问这些链接，则需要从域详细信息中获取 IPFS 内容哈希和链接。 访问 ENS 应用程序域页面：
|
||||
|
||||
* Classic：[tornadocash.eth](https://app.ens.domains/name/tornadocash.eth/details)
|
||||
* Nova：[nova.tornadocash.eth](https://app.ens.domains/name/nova.tornadocash.eth/details)
|
||||
|
||||
|
||||
例如，Classic (tornadocash.eth) 的 IPFS 链接将如下所示：
|
||||
```
|
||||
ipfs://bafybeiguelxw5aanwnhvaea5vjhknmcdmwvujne36wgabnkmcbt3563toa
|
||||
```
|
||||
|
||||
此链接的内容哈希是 `bafybeiguelxw5aanwnhvaea5vjhknmcdmwvujne36wgabnkmcbt3563toa`
|
||||
|
||||
### 本地 IPFS 部署（推荐）
|
||||
|
||||
* 勇敢的
|
||||
* 在浏览器中导航到 IPFS 链接
|
||||
* 出现提示时，选择 “使用 Brave 本地 IPFS 节点”
|
||||
|
||||
* 铬/火狐
|
||||
* 安装 IPFS 桌面
|
||||
* 安装 IPFS 伴侣扩展 ([Chrome](https://chrome.google.com/webstore/detail/ipfs-companion/nibjojkomfdiaoajekhjakgkdhaomnch?hl=zh) / [Firefox](https://addons.mozilla.org/zh/firefox/addon/ipfs-companion/))
|
||||
* 确保 IPFS 桌面已打开并有互联网连接
|
||||
* 在浏览器中导航到 IPFS 链接
|
||||
|
||||
### 验证和 IPFS 网关使用
|
||||
|
||||
* 获取内容哈希并为其添加前缀，后跟 `.` 到以下 IPFS 网关之一：
|
||||
* `ipfs.dweb.link`
|
||||
* https://bafybeiguelxw5aanwnhvaea5vjhknmcdmwvujne36wgabnkmcbt3563toa.ipfs.dweb.link
|
||||
* `ipfs.tornadocash.is` (社区网关)
|
||||
* https://bafybeiguelxw5aanwnhvaea5vjhknmcdmwvujne36wgabnkmcbt3563toa.ipfs.tornadocash.is
|
||||
* `ipfs.cf-ipfs.com`
|
||||
* https://bafybeiguelxw5aanwnhvaea5vjhknmcdmwvujne36wgabnkmcbt3563toa.ipfs.cf-ipfs.com
|
||||
|
||||
|
||||
## RPC
|
||||
|
||||
* 如果您想存款，您可能需要更改您的钱包 RPC，因为大多数提供商已阻止该协议。**Metamask、Infura 以及 Ankr 和 Alchemy 的默认提供者不禁止使用协议、治理和 TORN 进行交易**。
|
||||
|
||||
* 尝试在 [Chainlist](https://chainlist.org) 中搜索工作端点，这可能需要多次尝试（注意网络配置的 ChainID）。 下面显示了如何更改 MetaMask 的 RPC 提供程序的示例。
|
||||
|
||||
|
||||
|
||||
* 有时，访问该应用程序时，您可能会收到以下消息来解决此问题，请单击“打开设置”.
|
||||
|
||||
|
||||
|
||||
|
||||
* 然后，您将看到一个下拉选择，默认为一个选择。 单击它并选择“自定义”选项。
|
||||
|
||||
|
||||
|
||||
|
||||
* 根据您的网络在此处输入非审查 RPC 提供程序，这将解决应用程序问题。
|
||||
|
||||
|
||||
|
||||
* 然后，您可以自由地取款、存款、质押或参与去中心化治理，就像从未发生过一样。
|
||||
|
||||
## FAQ
|
||||
|
||||
> 为什么我总是收到 `Failed to fetch relayers` 的错误消息？
|
||||
|
||||
* 此错误要么与连接不良有关，要么与您的网络上没有可用的中继器有关。 通常可以通过刷新来解决。
|
||||
|
||||
> 为什么我总是收到 `Failed to fetch proving keys` 的错误消息？
|
||||
|
||||
* 此错误与连接不良有关，通常可以通过刷新或更改 VPN 位置以获得更好的延迟来解决。
|
||||
|
||||
> 为什么我在尝试提款时一直收到错误`Failed to fetch all deposit events from contract`？
|
||||
|
||||
* 此错误与连接不良或使用经过审查的 RPC 端点有关。 要解决此问题：
|
||||
* 更改 VPN 位置以获得更好的延迟
|
||||
* 尝试新的浏览器或访问方式
|
||||
* 将应用程序 RPC 配置配置为替代方案
|
||||
|
||||
> 为什么不能从我的钱包中存款？
|
||||
|
||||
* 自 OFAC 制裁以来，大多数 RPC 都会审查协议和治理的交易，您需要将钱包 RPC 配置为未经审查的端点。
|
||||
@ -18,9 +18,7 @@ Currently, it is fixed at `0.3%` . Some pools remain without fees, either becaus
|
||||
|
||||
## How to become a relayer?
|
||||
|
||||
Anyone can become a relayer for the protocol in **6 simple steps** through the relayer registry user interface [relayers-network.tornadocash.eth](https://app.ens.domains/name/relayers-network.tornadocash.eth/details)).
|
||||
|
||||
Below you will find everything your need to join our relayers' club & get listed on Tornado Cash decentralized relayer registry.
|
||||
Anyone can become a relayer for the protocol in **6 simple steps** through the relayer registry user interface [relayers-network.tornadocash.eth](https://app.ens.domains/name/relayers-network.tornadocash.eth/details).
|
||||
|
||||
### 1. Disclaimer
|
||||
|
||||
@ -36,11 +34,11 @@ The formula for designating a relayer is as follows:
|
||||
|
||||
### 2. Set up relayer
|
||||
|
||||
The first concrete step is to run the Tornado Cash Relayer software for Ethereum Mainnet on your computer. All steps are outlined in the protocol's github. To complete this task successfully, you will have to carefully follow [these instructions](https://github.com/tornadocash/tornado-relayer#deploy-with-docker-compose).
|
||||
The first concrete step is to run the Tornado Cash Relayer software for Ethereum Mainnet on your computer. All steps are outlined in the protocol's github. To complete this task successfully, you will have to carefully follow [these instructions](https://development.tornadocash.community/tornadocash/classic-relayer).
|
||||
|
||||
Once completed, you will need to insert your url in the input box.
|
||||
|
||||
.png>)
|
||||
.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).
|
||||
@ -82,7 +80,7 @@ Tornado Cash Nova uses its own version of the software. If you wish to become a
|
||||
| ------------------- |
|
||||
| gnosis-nova.xxx.eth |
|
||||
|
||||
|
||||
|
||||
|
||||
### **4. Set up workers**
|
||||
|
||||
@ -92,7 +90,7 @@ To ensure an extra level of security, we advise you to set up more than one work
|
||||
|
||||
Only the mainnet requires you to register workers. All other networks do not require the use of registered workers.
|
||||
|
||||
|
||||
|
||||
|
||||
### 5. Stake
|
||||
|
||||
@ -102,16 +100,16 @@ The minimum staked amount is currently set by Tornado Cash governance at **`300
|
||||
|
||||
When a relayer is used in the Tornado Cash pool, a small amount of TORN is automatically collected from this staked balance by the `StakingReward` contract. This element is essential to keep in mind as relayers will need 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 collected fees are subsequently distributed among DAO members with locked TORN tokens. TORN are usually locked to participate in on-chain governance (submitting & voting on proposals). You can find more information both on the _[Staking documentation page](../token/staking.md)_.
|
||||
The collected fees are subsequently distributed among DAO members with locked TORN tokens. TORN are usually locked to participate in on-chain governance (submitting & voting on proposals). You can find more information both on the _[Staking documentation page](../general/token/staking.md)_.
|
||||
|
||||
{% hint style="warning" %}
|
||||
Your staked TORN amount is not claimable, and it is non-refundable
|
||||
{% endhint %}
|
||||
|
||||
|
||||
|
||||
|
||||
### 6. Final verification and registration
|
||||
|
||||
Last but not least, we advise you to **double-check all information** displayed in the summary before registering.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -16,15 +16,15 @@ Then, run it.
|
||||
|
||||
First, search for `about:config` on your URL navigation bar.
|
||||
|
||||
|
||||
|
||||
|
||||
Then, accept the caution message by clicking on `Accept the Risk and Continue`.
|
||||
|
||||
|
||||
|
||||
|
||||
Search for `wasm` and turn `javascript.options.wasm` on true.
|
||||
|
||||
|
||||
|
||||
|
||||
Search for `indexedDB` and turn `dom.indexedDB.logging.details` and `dom.indexedDB.logging.enabled` on true
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user