Updating the Contracts

When any of the contracts get updated, their corresponding expected build artifacts need to be updated as well.

To do make this update, run:

yarn build

Migrations

The networks folder contains the migration files for the different Ethereum networks the contracts have been migrated to. The ID of the respective networks are used as file names. The mapping of some of the major Ethereum network IDs to network names is:

| Network ID | Network Name | | ---------- | --------------- | | 1 | Main net | | 3 | Ropsten testnet | | 4 | Rinkeby testnet | | 42 | Kovan testnet |

Not all of the networks will be used for the Counterfactual contracts, but you can find a more comprehensive list here. To run a migration against a target network:

• make sure the target network configuration exists in truffle.js (or truffle-config.json for Windows)
• cp .env.example .env and make sure the right env vars are set in .env
  • note that the address of the account that needs to be funded to deploy the contracts is derived (in a node.js REPL) via: require('ethers').Wallet.fromMnemonic('ETH_ACCOUNT_MNENOMIC')
• the network account you're using to send transactions from is funded (eg. for Rinkeby: https://faucet.rinkeby.io/)
• run: yarn migrate --network <network name>