fix: hardcode Alchemy gateway URLs#186
Merged
TaprootFreak merged 1 commit intodevelopfrom May 8, 2026
Merged
Conversation
Alchemy gateway URLs follow a fixed pattern per chain (e.g. https://eth-mainnet.g.alchemy.com/v2). The env vars contained stale Goerli/Mumbai testnet URLs causing NETWORK_ERROR in the ethers.js provider used by MonitoringService for ERC20 contract calls. Only ALCHEMY_API_KEY remains as env var (it's a secret). Citrea keeps its env var (non-Alchemy, deployment-specific RPC).
This file contains hidden or 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
1 participant
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
EvmClientcreates anethers.JsonRpcProviderwith${gatewayUrl}/${apiKey}that is actively used forcontract.decimals()calls in the MonitoringServiceNETWORK_ERRORon every monitoring cycleALCHEMY_API_KEYremains as env var (it's a secret)CITREA_GATEWAY_URLstays as env var (non-Alchemy, deployment-specific RPC)Test plan
NETWORK_ERROR/noNetworkin lds-api logs