Contract Deployments

Mainnet

Rinkeby

Deploy Process

See Deployer for a guide to the deployment process. Each deploy has the following outputs:

  • A new contract is deployed from the master branch.

  • After deploy, the contract source code is verified on Etherscan.

  • New contract addresses are written to deploys.json in each package. (Both on GitHub and NPM)

  • New contract ABI is written to build/contracts in each package. (Only on NPM)

Contract Versioning

Packages are versioned based on deploys. Major versions e.g. 1.x.x are mainnet deploys, while minor versions e.g. x.1.x are rinkeby deploys. Packages that are not deployed increment patch versions e.g. x.x.1.

MAJOR.MINOR.PATCH (Semantic Versioning)

  • MAJOR is incremented on MAINNET deploy

  • MINOR is incremented on TESTNET deploy (specifically RINKEBY)

  • PATCH is incremented to publish to NPM, unrelated to a deploy.