Skip to content

Add NodeFlare public RPC endpoints for 8 EVM chains#8359

Open
BabyScope wants to merge 5 commits into
ethereum-lists:masterfrom
BabyScope:add-nodeflare-rpc
Open

Add NodeFlare public RPC endpoints for 8 EVM chains#8359
BabyScope wants to merge 5 commits into
ethereum-lists:masterfrom
BabyScope:add-nodeflare-rpc

Conversation

@BabyScope

Copy link
Copy Markdown

Summary

Adds public RPC endpoints for NodeFlare, a multi-region EVM RPC provider with nodes across Europe, Asia, and North America. Requests are automatically geo-routed to the nearest region.

Endpoints added

Chain EIP URL
Ethereum Mainnet eip155-1 https://rpc.nodeflare.app/eth/public
Base eip155-8453 https://rpc.nodeflare.app/base/public
BNB Smart Chain eip155-56 https://rpc.nodeflare.app/bnb/public
Arbitrum One eip155-42161 https://rpc.nodeflare.app/arb/public
Optimism eip155-10 https://rpc.nodeflare.app/op/public
Viction eip155-88 https://rpc.nodeflare.app/vic/public
HyperLiquid EVM eip155-999 https://rpc.nodeflare.app/hl/public
Avalanche C-Chain eip155-43114 https://rpc.nodeflare.app/avax/public

Notes

  • All endpoints are publicly accessible without an API key
  • Rate-limited per IP to prevent abuse
  • Heavy methods (eth_getLogs, trace_*, debug_*) are restricted on the public endpoint — a free API key at nodeflare.app removes this restriction

NodeFlare (https://nodeflare.app) is a multi-region EVM RPC provider
with nodes across Europe, Asia, and North America. Requests are
automatically routed to the nearest region.

Added public endpoints (no API key required, rate-limited) for:
- Ethereum Mainnet (eip155-1)
- Base (eip155-8453)
- BNB Smart Chain (eip155-56)
- Arbitrum One (eip155-42161)
- Optimism (eip155-10)
- Viction (eip155-88)
- HyperLiquid EVM (eip155-999)
- Avalanche C-Chain (eip155-43114)
@github-actions

Copy link
Copy Markdown

You successfully submitted a PR! Due to the amount of PRs coming in: we will only look at PRs that the CI is happy with. We can also not hold your hand getting the CI green - just look how others that where merged did it and RTFM. So as long as there is any CI check that reports an error - no human will look at this. You might be able to ask for some support after supporting the project - e.g. by sending funds to lists.eth. When you fixed things after a requested change - then you also need to (re-)request a review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants