Add BlockReq public RPCs for 25 EVM networks

[luanxu-dev]

If you are adding a new RPC, please answer the following questions.

Link the service provider's website (the company/protocol/individual providing the RPC):

https://blockreq.com/

Public endpoint documentation: https://blockreq.com/docs/build/public-endpoints/

Network identities: https://blockreq.com/docs/build/supported-networks/

This adds one keyless public HTTPS RPC to the end of the existing arrays for 25 EVM networks:

1, 10, 25, 56, 100, 130, 137, 146, 204, 4663, 5042, 8453, 10200, 42161, 42220, 43114, 59144, 80002, 80094, 81457, 84532, 421614, 534352, 11155111, 11155420.

Provide a link to your privacy policy:

No public RPC privacy-policy URL could be verified for this submission. All entries are explicitly marked tracking: "unspecified"; no no-tracking or limited-tracking claim is made.

If the RPC has none of the above and you still think it should be added, please explain why:

The provider website and public endpoints are available without an API key. The missing privacy information is disclosed above and represented by unspecified metadata.

Validation performed on 2026-10-01 at approximately 17:51 UTC:

• All 25 RPCs returned the expected eth_chainId and a valid eth_blockNumber.
• 24 of 25 returned a latest block with a block number using eth_getBlockByNumber(["latest", false]), the query used by Chainlist's browser probe.
• All 25 POST responses allowed Origin https://chainlist.org; OPTIONS preflight returned HTTP 204 with POST and request headers permitted.
• npm test passed the repository's syntax and duplicate-key checks. The repository does not define a preflight script.
• Verified the additions are appended and existing RPC entries are unchanged.

These are point-in-time checks, not an uptime or latency guarantee. Known issue: Polygon mainnet (137) returns JSON-RPC -32601 for Chainlist's latest-block query (eth_getBlockByNumber(["latest", false])), despite successful chain ID and block number queries. The Polygon entry is included in this consolidated submission; its latest-block query needs to be repaired and rechecked before it can display as healthy in Chainlist.

Polygon Amoy (80002) uses the verified canonical product address https://polygon-amoy-rpc.blockreq.com/v1/rpc/public. The provider documentation currently contains an incorrect polygon-amoy-bor-rpc.blockreq.com hostname; this is being corrected at the documentation source.

Your RPC should always be added at the end of the array.

[luanxu-dev]

Hi @DefiLlama team, could you share why this PR was closed? We're happy to fix whatever didn't meet the requirements, for example by adding a privacy policy link, removing any chain that isn't healthy (such as Polygon 137 or Blast 81457), or splitting it into smaller PRs, and then resubmitting. Thanks!

[luanxu-dev]

cc @Define101, since you closed this PR, could you let us know what we should fix? Thanks!