Initial Deployment of Gateway Contracts
How to set the Ethereum gateway controlling the bridge on the Ethereum side. This guide is specifically for setting the gateway address when deployed initially, not when the contracts are upgraded.
Build and Deploy Contracts
To build and deploy the new contracts, follow these steps from inside the Snowbridge repository:
Generate BEEFY State
Set the following in .env file:
The BEEFY start block can be selected from a recent block that has a BEEFY commitment.
Run scripts/generate-beefy-checkoutpoint.sh
. This will leave the beefy state in the contracts folder.
Deploy Contracts
Set the following in .env file:
Run scripts/deploy-contracts.sh
Back up contracts.json
and contract artifacts to s3: https://s3.console.aws.amazon.com/s3/buckets/snowbridge-rococo-demo?region=eu-central-1&bucketType=general&tab=objects
Confirm settings with the team and get ETH for the deployment.
Add contracts to tenderly
Update the EthereumGatewayAddress on BridgeHub
To update the EthereumGateway
contract address, a set storage call is executed:
Example call hash:
0xff00630003000100d50f03082f000006020700c817a804824f1200a400040440aed97c7854d601808b98ae43079dafb3505b4909ce6ca82d2ce23bd46738953c7959e710cd
Last updated