You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
Roman Storm ac9458208f
fix toNumber
2 years ago
.github/workflows fix ci 2 years ago
abi update abi 2 years ago
cache update cache 2 years ago
src fix toNumber 2 years ago
test initial 2 years ago
.dockerignore fix get pending caches 2 years ago
.editorconfig initial 2 years ago
.env.example update readme 2 years ago
.eslintrc initial 2 years ago
.gitignore upload updates using snark 2 years ago
.prettierrc initial 2 years ago
Dockerfile updates 2 years ago
LICENSE initial 2 years ago update readme 2 years ago
docker-compose.yml update docker compose 2 years ago
package.json bump version 2 years ago
yarn.lock fix get pending caches 2 years ago

Root updater Build Status Docker Image Version (latest semver)

For Tornado Cash to enable mining, it needs more metadata than is currently available: it needs to know the block number for each Tornado Cash deposit and withdrawal. Since the current version of Tornado cash is immutable the mining system uses a special proxy to collect this data. When users make deposits and withdrawal all necessary data is recorded to the proxy contract. In order to be used in zkSnark proof, this data should be added to the special Merkle trees (deposits Merkle tree and withdrawals Merkle tree). So long as someone out there does this, the system works smoothly and trustlessly.

This software helps to upload deposit and withdrawal metadata from Tornado Cash anonymity mining proxy into the TornadoTrees contract that handles the Merkle trees.

Keep in mind, it could cost some ether to do so.

Usage with docker

wget -O .env
vi .env # update env vars
docker-compose up -d

Usage for development

brew install redis

cp .env.example .env
vi .env
# download and unzip snark keys from to `snarks` directory
yarn start

Caches events from both mining and tornado cash instances