Previously with hyperlane, the bridge contract on our settlement layer did not use foundry for deployment. Consequently we had to pass the bridge contract address to the whitelist deployment script as an environment variable. Now that our bridge contracts reside within this repo, we can use a single deploy script that deploys both the Whitelist and SettlementGateway together. The gateway contract is deployed first, then the whitelist, and finally the address of the gateway contract is whitelisted. This simplifies scripts that use DeploySettlementGateway and prevents the need for greping addresses out of deployment stdout
Previously with hyperlane, the bridge contract on our settlement layer did not use foundry for deployment. Consequently we had to pass the bridge contract address to the whitelist deployment script as an environment variable. Now that our bridge contracts reside within this repo, we can use a single deploy script that deploys both the
WhitelistandSettlementGatewaytogether. The gateway contract is deployed first, then the whitelist, and finally the address of the gateway contract is whitelisted. This simplifies scripts that useDeploySettlementGatewayand prevents the need forgreping addresses out of deployment stdout