fix: update Alchemy API host URLs to the new domain format #5052
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.
eth-mainnet.alchemyapi.io
has been replaced witheth-mainnet.g.alchemy.com
.This PR addresses the incident report from Alchemy, which reported an outage on the legacy "alchemyapi.io" endpoints. The
AlchemyProvider
in ethers.js creates a provider based on internal URL mapping, where all known chains utilize the new domain, except for Ethereum Mainnet. This PR aims to rectify this discrepancy.Instantiating a provider using
AlchemyProvider
encountered connectivity issues due to the use of the legacy domain.Resources: