1) AMB contracts deployment
Create accounts for deployment
1) Generate private keys for the following using MetaMask or MyEtherWallet. Save as json keystore file + password. Note the json location, wallet address, and password for each account.
DEPLOYMENT_ACCOUNT
FOREIGN_BRIDGE_OWNER
FOREIGN_VALIDATORS_OWNER
FOREIGN_UPGRADEABLE_ADMIN
HOME_BRIDGE_OWNER
HOME_VALIDATORS_OWNER
HOME_UPGRADEABLE_ADMIN
VALIDATOR
This data can not be recovered through an account after creation, so be sure to store accurately and safely.
You will need tokens for deployment on both sides of the bridge. This means the DEPLOYMENT_ACCOUNT and VALIDATOR accounts will require tokens. The DEPLOYMENT_ACCOUNT will deploy bridge contracts and initialize the bridge, and VALIDATOR accounts use tokens to pay for txs with bridge operations.
Configure and Deploy Bridge Contracts
1) Create configuration file amb.config
amb.config
Replace all variables templated with tags (<>) with actual values. Learn more about variables here
Optional: If you plan to use Etherscan or BlockScout for exploring your chain, find information on the correct parameters to include in the .env file here: https://docs.tokenbridge.net/about-tokenbridge/features/contracts-verification-in-explorers
2) Deploy Contracts
Deployment of contracts with usage of the docker image is very straightforward:
After successful deployment the following information about the bridge contracts is displayed:
Last updated