eth_createAccessList on PulseChain
Measured 2026-10-04 by our weekly probe, which calls eth_createAccessList through the same PulseChain 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 PulseChain: what we measured
- Default PulseChain routing keeps state for roughly the last 1,000,000 blocks (about 118.6 days of PulseChain 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/pulsechain?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/pulsechain?key=YOUR_API_KEY") });
// Any JSON-RPC method, typed loosely: eth_createAccessList on PulseChain
const result = await client.request({
method: "eth_createAccessList",
params: [{"from":"0x0000000000000000000000000000000000000000","to":"0x0000000000000000000000000000000000000000","data":"0x"},"latest"],
});Other methods on PulseChain
- eth_getLogsSupported
- eth_getBlockReceiptsSupported
- eth_feeHistorySupported
- eth_getProofSupported
- debug_traceCallSupported
- trace_blockSupported
- trace_transactionSupported
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
Frequently asked questions
Does PulseChain support eth_createAccessList?
Yes. eth_createAccessList answered correctly on the SwiftNodes PulseChain endpoint in our weekly method probe (2026-10-04), which sends real requests through the customer path.
Are there limits on eth_createAccessList on PulseChain?
Default PulseChain routing keeps state for roughly the last 1,000,000 blocks (about 118.6 days of PulseChain history). Simulating against a block older than that needs historical state. Add &archive=1 to send the request to archive upstreams (paid plans).
PulseChain endpoints, live block height and WebSocket status are on the PulseChain RPC page.
One key covers every chain we serve, and SwiftNodes has a free tier.