tornadocash
/
tornado-deploy
mirror of https://github.com/tornadocash/tornado-deploy.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
29 Commits 8 Branches 0 Tags 170 KiB
JavaScript 97.7%
Shell 2.3%
Go to file
Roman Semenov e2a069810d
Update README.md 		2021-03-19 00:47:31 +03:00
abi initial 2020-12-15 18:10:11 +03:00
deployer@c6526c7f02 update salt 2021-02-14 11:02:24 +03:00
src goerli instances 2021-03-15 00:04:26 +04:00
tornado-core@3603b1c9e1 goerli instances 2021-03-15 00:04:26 +04:00
.env.example goerli instances 2021-03-15 00:04:26 +04:00
.eslintrc initial 2020-12-15 18:10:11 +03:00
.gitignore initial 2020-12-15 18:10:11 +03:00
.gitmodules update salt 2021-02-14 11:02:24 +03:00
.prettierrc initial 2020-12-15 18:10:11 +03:00
README.md Update README.md 2021-03-19 00:47:31 +03:00
build.sh update salt 2021-02-14 11:02:24 +03:00
instancesGoerli.js goerli instances 2021-03-15 00:04:26 +04:00
instancesMainnet.js goerli 2021-03-14 23:00:16 +04:00
package.json update salt 2021-02-14 11:02:24 +03:00
yarn.lock initial 2020-12-15 18:10:11 +03:00

README.md

Dependencies

  1. node 12
  2. yarn

Usage

git clone --recursive https://github.com/tornadocash/tornado-deploy -b tornado-core
cd tornado-deploy
cp .env.example .env
yarn

Edit instances.js config to choose what Tornado pool you would like to deploy

When you are ready, run

yarn build

The result of the build is actions.json file, that contains everything that is needed to deploy contracts on Ethereum along with expected deploy addresses.

Reproducible build

In order to generate exactly the same actions.json the code has to be compiled in /private/tmp/tornado-deploy dir because solidity compiler includes a hash of full path to files into contact bytecode as swarm hash. If you compile in other dir this swarm hash will be different. It doesn't affect contract execution but your actions.json will have a different hash from the initiation version.