Go to file
Alexey Pertsev 7feece2fc0
Merge pull request #1 from tornadocash/fixDesc
fix: description
2021-12-06 15:22:13 +01:00
abi initial 2020-12-15 18:10:11 +03:00
deployer@c6526c7f02 update salt 2021-02-14 11:02:24 +03:00
src fix: description 2021-12-07 00:16:06 +10:00
tornado-pool@32b8aeeec1 update submodule 2021-11-10 22:17:36 +03:00
.env.example update submodule 2021-11-10 22:17:36 +03:00
.eslintrc initial 2020-12-15 18:10:11 +03:00
.gitignore initial 2020-12-15 18:10:11 +03:00
.gitmodules WIP 2021-10-18 13:04:00 +03:00
.prettierrc initial 2020-12-15 18:10:11 +03:00
README.md fix: description 2021-12-07 00:16:06 +10:00
build.sh generates action.json for ceremony 2021-10-19 12:33:46 +03:00
package.json execute 2021-10-20 12:01:31 +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

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.

Verify addresses

cat actions.json | jq '.actions[] | {domain,expectedAddress,contract} '