fix(rpcs): remove dead and defunct RPC endpoints for Ethereum (1) - #3181
Merged
Merged
Conversation
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
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.
Removes 29 Ethereum Mainnet (chain 1) RPC endpoints from
constants/extraRpcs.jsthat no longer work.I checked every chain 1 endpoint in the file with an
eth_chainIdrequest from two locations (Bangkok and Helsinki), three times two minutes apart on 2026-09-24, and once more right before opening this PR. Only endpoints that failed the same way every time from both locations are removed. DNS failures were confirmed with Google and Cloudflare DNS.Endpoints that were rate limited, timed out, returned 5xx or failed from only one location are left in, and so are commented-out entries. The
wss://URL on the same NXDOMAIN host as a removedhttps://URL is removed as well.https://api.securerpc.com/v1https://api.zmok.io/mainnet/oaen6dy8ff6hju9khttps://eth-mainnet-public.unifra.iohttps://eth-mainnet.diamondswap.org/rpchttps://eth.nodeconnect.org/https://ethereum.therpc.iohttps://gw-aql.tomo.services/v1/ethereum/aql_li...wss://gw-aql.tomo.services/v1/ethereum/aql_li...https://main-light.eth.linkpool.iohttps://public.stackup.sh/api/v1/node/ethereum-mainnethttps://rpc.builder0x69.io/https://rpc.lokibuilder.xyz/wallethttps://rpc.nodifi.ai/api/rpc/freehttps://rpc.payload.dehttps://rpc.poolz.finance/ethhttps://rpc.public.curie.radiumblock.co/http/ethereumhttps://rpc.public.curie.radiumblock.co/ws/ethereumhttps://eth1.lava.buildhttps://endpoints.omniatech.io/v1/eth/mainnet/publichttps://rpc.graffiti.farmhttps://eth-mainnet.4everland.org/v1/37fa99...https://rpc.ankr.com/eth/c4cc6a...https://go.getblock.io/aefd01...https://eth-rpc.keccak.iohttps://virtual.mainnet.rpc.tenderly.co/7355b2...https://api.stateless.solutions/ethereum/v1/demohttps://rpc.notadegen.com/ethhttps://rpcfree.com/ethereum-rpchttps://openapi.bitstack.com/v1/wNFxbi.../DjShIq.../ETH/mainnetNone of these URLs are touched by the open PRs #3169, #3106 or #3173. The diff only deletes whole entries (a URL line or a complete
{ url, tracking, trackingDetails }object). 30 other Ethereum endpoints answered0x1every time and are unchanged.