feat(protocol-contracts): add modularity to deploy protocol contracts script #1110
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.
Add arguments to the script to select the network on which the
ZamaOFTcontract can be deployed.Prior version was locked to deploying on
arbitrum-testnet(Arbitrum Sepolia).Proposed version allow the user to deploy on a network off a list (currently
arbitrum-testnetorgateway-testnet), to limit risk of deploying to the wrong network.Once deployed, the
ZamaOFTAdapterandZamaOFTcontracts must be wired, based on the LayerZero config file, which can now be provided by the user, if multiple config files exist for the different supported networks ; It defaults tolayerzero.config.tsNote: It also adds the
RPC_URL_ARBITRUM_SEPOLIAvariable to the.env.example, as thehardhat.config.tsis already configured to use this value if provided