Skip to content

Add eRPC to Blockchain Access / Node and Archive Services - #111

Open
kasrakhosravi wants to merge 1 commit into
bnb-chain:mainfrom
kasrakhosravi:add-erpc
Open

kasrakhosravi wants to merge 1 commit into
bnb-chain:mainfrom
kasrakhosravi:add-erpc

Conversation

@kasrakhosravi

Copy link
Copy Markdown
  • Adds eRPC to Blockchain Access → Node and Archive Services in data.json (BSC, opBNB).
  • eRPC is an open-source (Apache-2.0), self-hosted EVM RPC proxy, not a hosted provider; it sits in front of several RPC providers or your own nodes and adds failover, retries, a reorg-aware cache and rate limiting.
  • node scripts/validate-data.js passes.
  • Tested on BNB Smart Chain mainnet (chain ID 56) with eRPC main at f3c7eff2, using 2 upstreams: bsc-dataseed.bnbchain.org and bsc-rpc.publicnode.com. eth_chainId, eth_blockNumber, eth_getBlockByNumber(finalized) and eth_getBalance return correct results; with one upstream unreachable, 5/5 eth_blockNumber calls succeed through the other.
  • I work on eRPC (Goldsky).

@hashdit-bot

hashdit-bot Bot commented Oct 25, 2026

Copy link
Copy Markdown

Pull Request Review

This PR adds eRPC to the BSC and opBNB “Blockchain Access → Node and Archive Services” catalog in data.json. The new entry describes eRPC’s self-hosted RPC proxy capabilities and provides its logo, repository, documentation, and contact metadata.

Sensitive Content

No sensitive content detected.

Security Issues

No serious security issues detected.


Generated by Hashdit Bot. This tool can absolutely NOT replace manual audits.

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.

1 participant