Migrate Arbitrum Network from Goerli to Sepolia #607
Merged
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.
Summary
This pull request includes changes to migrate the Arbitrum network from Goerli to Sepolia.
Key changes include:
Update ChainIDs: The ChainID for Arbitrum has been updated from ArbitrumGoerli to ArbitrumSepolia in the chains.go file. The corresponding ChainID number has also been updated.
Update Configurations: The .env_validator.example and config.json files have been updated to reflect the change in the Arbitrum network. The API key and endpoint for Arbitrum have been updated from Goerli to Sepolia.
Update Endpoints: The endpoint URLs for Arbitrum in the chains.go file have been updated to point to the Sepolia network.
Update Contract Address: The contract address for the Arbitrum network in the chains.go file has been updated.
These changes ensure that the application is now interacting with the Sepolia network for Arbitrum instead of Goerli.
NOTE: Doesn't add the healthbot config since we have stopped using healthbot on optimism and arbitrum