Skip to content

fix: hardcode EVM chain IDs#185

Merged
TaprootFreak merged 1 commit intodevelopfrom
fix/hardcode-evm-chain-ids
May 8, 2026
Merged

fix: hardcode EVM chain IDs#185
TaprootFreak merged 1 commit intodevelopfrom
fix/hardcode-evm-chain-ids

Conversation

@TaprootFreak
Copy link
Copy Markdown
Contributor

@TaprootFreak TaprootFreak commented May 8, 2026

Summary

  • Chain IDs are fixed per chain, not deployment-specific — they don't belong in env vars
  • The env vars contained stale Goerli/Mumbai testnet IDs from the old Azure DEV setup
  • The Alchemy SDK uses chain IDs to determine endpoints, so testnet IDs → deprecated testnet URLs → ENOTFOUND errors every 8 seconds
  • Hardcodes mainnet chain IDs: Ethereum=1, Arbitrum=42161, Optimism=10, Polygon=137, Base=8453, Citrea=5115

Test plan

  • Deploy to dfxdev
  • Verify no more eth-goerli.g.alchemy.com or polygon-mumbai.g.alchemy.com errors in logs
  • Verify /v1/boltz/balance returns Ethereum and Polygon balances

@TaprootFreak
fix: hardcode EVM chain IDs instead of reading from env vars
eb162c5 
Chain IDs are fixed per chain (Ethereum=1, Polygon=137, etc.),
not deployment-specific secrets. The env vars contained stale
Goerli/Mumbai testnet IDs from the Azure DEV setup, causing the
Alchemy SDK to query deprecated testnet endpoints.
@TaprootFreak TaprootFreak marked this pull request as ready for review May 8, 2026 16:15
@TaprootFreak TaprootFreak merged commit c4db6a5 into develop May 8, 2026
1 check passed
@TaprootFreak TaprootFreak mentioned this pull request May 8, 2026
Merged
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@TaprootFreak