BSC Archive Node RPCFull history archive with eth_getProof, stateOverride & debug/trace
BSC archive node RPC with eth_getProof on ALL historical blocks — not just 128 or 200k. stateOverride, debug/trace API. Free 80M RU/month.
Why BSC Archive on BlockReq
- eth_getProof on ANY block — not limited to 128 blocks (QuickNode) or 200k blocks (Erigon)
- Full BSC history since genesis with complete state
- eth_call with stateOverride for DeFi simulation
- debug_traceTransaction for MEV and bot analysis
- PancakeSwap, Venus, and BSC DeFi contract debugging
- No 'missing trie node' or 'State was pruned' errors
Supported Archive RPC Methods
All methods work on any historical block — from genesis to latest.
eth_getBalanceeth_getCodeeth_getStorageAteth_getProofeth_call (stateOverride)debug_traceTransactiondebug_traceCalltrace_blocketh_getLogseth_getProof on early BSC block (not possible on most providers)
# This works on BlockReq but fails on QuickNode/NodeReal
# because they limit eth_getProof to recent blocks only
curl -X POST https://bsc.blockreq.com/YOUR_API_KEY \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"method": "eth_getProof",
"params": [
"0x10ED43C718714eb63d5aA57B78B54704E256024E",
["0x0"],
"0x989680"
],
"id": 1
}'Frequently Asked Questions
Does BlockReq support eth_getProof on BSC for all historical blocks?
Yes. Unlike QuickNode (limited to 128 blocks) and BSC-Erigon (limited to 200,000 blocks as reported in node-real/bsc-erigon#738), BlockReq provides eth_getProof on ALL historical BSC blocks from genesis.
Why is BSC eth_getProof limited on other providers?
Most BSC RPC providers use pruned nodes or Erigon configurations that only retain recent state proofs. BlockReq maintains full archive state with commitment history enabled, allowing unlimited historical proof generation.
Can I simulate PancakeSwap trades using stateOverride on BSC?
Yes. Use eth_call with stateOverride to simulate token swaps, liquidity additions, and arbitrage strategies on BSC without spending gas. Combined with debug_traceTransaction, you can analyze complete execution traces.
How do I fix 'missing trie node' errors when forking BSC with Hardhat?
The 'missing trie node' error on BSC is caused by pruned RPC nodes that only retain recent state (typically 128 blocks). Use BlockReq's BSC archive node as your forking endpoint — it stores complete state since genesis, so you can fork from any historical block without errors.
Why does debug_traceTransaction fail on BSC with other providers?
debug_traceTransaction requires access to the complete historical state at the block where the transaction was mined. Most BSC providers only offer pruned nodes where old state is discarded (see bsc-erigon#203). BlockReq archive nodes retain all historical state, so debug_traceTransaction works on any BSC transaction.
How do I fix 'State was pruned, archive access needed' on BSC?
This error means your RPC provider's node has discarded old state data. Switch to BlockReq's BSC archive endpoint to access complete historical state from genesis. All plans include archive access — even the free tier with 80M RU/month.
Can I query BSC eth_getStorageAt on historical blocks?
Yes. BlockReq archive nodes support eth_getStorageAt on any historical BSC block. This is essential for reading past contract storage slots, verifying historical token balances, and auditing smart contract state changes.
Start using BSC archive nodes today
Free 80M RU/month. No credit card required. Archive nodes with eth_getProof, stateOverride, and debug/trace on every plan.