deploy: whitelist with gateway #84
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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