infrastructure-upgrade/lib/tornado-governance
T-Hax 735546619e
init
Signed-off-by: T-Hax <>
2023-04-08 18:46:18 +00:00
..
.github/workflows init 2023-04-08 18:46:18 +00:00
contracts init 2023-04-08 18:46:18 +00:00
resources init 2023-04-08 18:46:18 +00:00
scripts init 2023-04-08 18:46:18 +00:00
test init 2023-04-08 18:46:18 +00:00
.editorconfig init 2023-04-08 18:46:18 +00:00
.env.example init 2023-04-08 18:46:18 +00:00
.eslintrc init 2023-04-08 18:46:18 +00:00
.gitattributes init 2023-04-08 18:46:18 +00:00
.gitignore init 2023-04-08 18:46:18 +00:00
.nvmrc init 2023-04-08 18:46:18 +00:00
.prettierignore init 2023-04-08 18:46:18 +00:00
.prettierrc init 2023-04-08 18:46:18 +00:00
.solcover.js init 2023-04-08 18:46:18 +00:00
.solhint.json init 2023-04-08 18:46:18 +00:00
config.js init 2023-04-08 18:46:18 +00:00
hardhat.config.js init 2023-04-08 18:46:18 +00:00
LICENSE init 2023-04-08 18:46:18 +00:00
package.json init 2023-04-08 18:46:18 +00:00
README.md init 2023-04-08 18:46:18 +00:00
yarn.lock init 2023-04-08 18:46:18 +00:00

Tornado governance build status Coverage Status

Description

This repository holds all the tornado.cash governance upgrades and original governance contracts.

Documentation

All high-level documentation can be find here.

Code architecture

Tornado governance infrastructure consists of two types of repository:

  1. Governance repository (this one) - contains the original governance contracts and parts of proposals that upgrade governance itself via loopback proxy. So here you can compile the actual version of the governance contract.
  2. Proposal repository - a separate repository for each governance proposal. It contains the full codebase of a proposal.

Loopback proxy

Loopback proxy is a special type of proxy contract that is used to add the ability to upgrade the proxy itself. This way governance proposals can upgrade governance implementation.

Proposal creation manual

To create your custom governance proposal you need to:

  1. Create a proposal repository (for example):
  • a proposal is executed from the governance contract using delegatecall of executeProposal() method
  • as a proposal is executed using delegatecall, it should not store any storage variables - use constants and immutable variables instead
  1. If your proposal is upgrading governance itself, you need to create a pull request to the governance repository. PR should add folder with governance contract upgrade (separate folder in contracts folder - for example).
  2. Deploy proposal. The proposal must be smart contracts with verified code.
  3. Go to Tornado governance UI to start the proposal voting process.

Tests/Coverage

Setting up the repository:

git clone https://github.com/tornadocash/tornado-governance.git
yarn
cp .env.example .env

Please fill out .env according to the template provided in it. Please ensure that all of the example values are set to the correct addresses.

To run test scripts:

    yarn test

To run tests coverage:

    yarn coverage