RPC Accelerator
Delivers faster responses by caching recent blockchain data.
RPC Accelerator dramatically improves read-performance across all supported chains by serving responses directly from tip-level cached blockchain data rather than waiting for full nodes to recompute the same information repeatedly. This results in ultra-fast rpc apis, smoother application performance, and significantly lower latency during traffic spikes.
By caching frequently accessed data — such as block headers, balances, receipts, and transactions — the RPC Gateway can return results instantly without repeatedly querying upstream endpoint providers.
Performance upgrade included: Most read calls targeting the tip of the chain are significantly faster when served from Tatum’s blockchain cache. The RPC Accelerator automatically enhances supported RPC methods with no configuration required.
How to enable RPC Accelerator?
Open your custom gateway
Open the custom gateway where you want to enable the RPC Accelerator

How RPC Accelerator Works
Instead of resolving every request from an RPC node, the Accelerator strategically caches canonical chain-tip data across multiple internal layers. This eliminates redundant recomputation and significantly reduces response times for frequently accessed data.
Methods That Benefit Most
Due to the block-tip caching model, the following commonly used methods experience the most significant performance improvements when querying data from blocks created within the time windows shown below:
| RPC Method | Accelerated Window |
|---|---|
| eth_blockNumber | 1 block (latest) |
| eth_chainId | ♾️ |
| eth_getBlockByHash | 4 hours |
| eth_getBlockByNumber | 4 hours |
| eth_getBlockTransactionCountByHash | 4 hours |
| eth_getBlockTransactionCountByNumber | 4 hours |
| eth_getTransactionByBlockHashAndIndex | 4 hours |
| eth_getTransactionByBlockNumberAndIndex | 4 hours |
| eth_getTransactionByHash | 1 hour |
| eth_getTransactionReceipt | 5 minutes |
Equivalent blocks times on different chains for 4 hours
- Ethereum: ~1,200 blocks (avg. block time 12s)
- Polygon: ~7,200 (avg. block time, 2s)
- BSC: ~14,400 (avg. block time, 1s)
- Base: ~7,200 (avg. block time, 2s)
- Arbitrum: ~57,600 (avg. block time, 0.25s)
Sending an Accelerated RPC Request
Simply call your existing RPC methods against a Gateway with RPC Accelerator enabled:
curl -X POST https://ethereum-mainnet.gateway.tatum.io \
-H "x-api-key: {YOUR_API_KEY}" \
-H "Content-Type: application/json" \
-d '{
"id": 1,
"jsonrpc": "2.0",
"method": "eth_getBlockByNumber",
"params": ["latest", true]
}'The Accelerator detects supported methods automatically and returns cached results when safe.
Performance Gains
Reduced Latency
Depending on method and the block range being queried the performance is drastically improved. Generally improving the the performance by 3-4x for calls listed here.
Smooth High-Volume Traffic
Even during network congestion or analytics scraping, Accelerator:
- Shields providers from overload
- Eliminates rate-limit burst failures
- Provides stable low-latency results
Does RPC Accelerator Affect Data Freshness?
No – Accelerator only serves responses when the cached value matches the chain tip.
If the Gateway detects new chain data or block advancement:
- Cached values are invalidated
- The next request is resolved from a live provider
- Fresh data is immediately re-cached
Data freshness is never compromised — RPC Accelerator never returns stale block data.
FAQs — RPC Accelerator
Do I need to change my code or integration?
Does it accelerate write calls?
eth_sendRawTransaction bypass caching.
Can it return outdated data?
Can I disable RPC Accelerator?
Updated about 5 hours ago