eth_createAccessList on Tempo
Measured 2026-10-11 by our weekly probe, which calls eth_createAccessList through the same Tempo endpoint customers use.
What eth_createAccessList does
Simulates a transaction and returns the EIP-2930 access list of addresses and storage keys it touches, plus the gas it would use with that list attached.
eth_createAccessList on Tempo: what we measured
- Default Tempo routing keeps state for roughly the last 1,000,000 blocks (about 6.7 days of Tempo history). Simulating against a block older than that needs historical state. Add &archive=1 to send the request to archive upstreams (paid plans).
Example request
curl -s https://rpc.swiftnodes.io/rpc/tempo?key=YOUR_API_KEY \
-X POST -H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"eth_createAccessList","params":[{"from":"0x0000000000000000000000000000000000000000","to":"0x0000000000000000000000000000000000000000","data":"0x"},"latest"]}'import { createPublicClient, http } from "viem";
const client = createPublicClient({ transport: http("https://rpc.swiftnodes.io/rpc/tempo?key=YOUR_API_KEY") });
// Any JSON-RPC method, typed loosely: eth_createAccessList on Tempo
const result = await client.request({
method: "eth_createAccessList",
params: [{"from":"0x0000000000000000000000000000000000000000","to":"0x0000000000000000000000000000000000000000","data":"0x"},"latest"],
});Other methods on Tempo
- eth_blockNumberSupported
- eth_chainIdSupported
- eth_getBalanceSupported
- eth_getBlockByNumberSupported
- eth_getTransactionByHashSupported
- eth_getTransactionReceiptSupported
- eth_callSupported
- eth_estimateGasSupported
- eth_gasPriceSupported
- eth_maxPriorityFeePerGasSupported
- eth_sendRawTransactionSupported
- eth_getTransactionCountSupported
- eth_getCodeSupported
- eth_subscribeSupported
- eth_getLogsSupported
- eth_getBlockReceiptsSupported
- eth_feeHistorySupported
- eth_getProofSupported
- debug_traceCallSupported
- trace_blockSupported
- trace_transactionNot measured
eth_createAccessList on other chains
Support differs by chain; the full measured table is on the eth_createAccessList reference.
- Ethereum
- Base
- Arbitrum
- Optimism
- Polygon
- BNB Smart Chain
- Avalanche
- Sonic
- Linea
- Scroll
- zkSync Era
- Blast
- Mantle
- Gnosis
- Celo
- Berachain
- Monad
- Unichain
- Kaia
- PulseChain
- World Chain
- Ronin
- Abstract
- ApeChain
- MegaETH
- Fantom
- Lisk
- Hemi
- X Layer
- BOB
- Plasma
- Fraxtal
- Zora
- Story
- Soneium
- Sei
- Hyperliquid
- Taiko
- Morph
- Ink
- Katana
- Ethereum Classic
- opBNB
- Mode
- Flare
- Core
- Chiliz
- Telos EVM
- Cronos
- Manta Pacific
- Shibarium
- Boba Network
- Arbitrum Nova
- Immutable zkEVM
Frequently asked questions
Does Tempo support eth_createAccessList?
Yes. eth_createAccessList answered correctly on the SwiftNodes Tempo endpoint in our weekly method probe (2026-10-11), which sends real requests through the customer path.
Are there limits on eth_createAccessList on Tempo?
Default Tempo routing keeps state for roughly the last 1,000,000 blocks (about 6.7 days of Tempo history). Simulating against a block older than that needs historical state. Add &archive=1 to send the request to archive upstreams (paid plans).
Tempo endpoints, live block height and WebSocket status are on the Tempo RPC page.
One key covers every chain we serve, and SwiftNodes has a free tier.