1) AMB contracts 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.
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.
Replace all variables templated with tags (<>) with actual values. Learn more about variables here
# The private key without 0x part.
# The maximum value of gas for one call to be allowed for relaying.
# The maximum value of estimated gas for one transaction in Wei.
# If several validators are used, list them separated by space without quotes
# E.g. VALIDATORS=0x 0x 0x
VALIDATORS=<address of validator>
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
Deployment of contracts with usage of the docker image is very straightforward:
docker run -it --env-file amb.config poanetwork/tokenbridge-contracts deploy.sh
After successful deployment the following information about the bridge contracts is displayed: