What NodeCache EVM does
- Caches responses to read-only JSON-RPC calls: eth_call, eth_getBalance, eth_getCode, eth_getLogs, eth_blockNumber and eth_chainId.
- Caches responses per method and request parameters for a short, fixed time (TTL, time to live): eth_chainId for one hour, every other supported method for a few seconds.
- Supports Ethereum mainnet.
What NodeCache EVM does not do
- Proxy or cache state-changing methods (transactions): any method other than the six listed is rejected with an error.
- Let you configure cache lifetimes: they are fixed.
- Support chains other than Ethereum mainnet today.
Not available today
- Multi-chain support beyond Ethereum mainnet
- A self-serve usage dashboard
- Self-serve API key rotation
Frequently asked questions
Which RPC methods does NodeCache cache?
The read-only methods eth_call, eth_getBalance, eth_getCode, eth_getLogs, eth_blockNumber and eth_chainId.
Does NodeCache cache transactions?
No. It does not proxy or cache state-changing methods; any method outside the six read-only ones is rejected with an error.
Which chains does NodeCache support?
Ethereum mainnet only today. Other chains are not available.
How long does NodeCache keep a cached response?
For a short, fixed time that depends on the method: one hour for eth_chainId, which never changes, and a few seconds for every other supported method. The lifetimes cannot be configured.