eth_getProof on Arbitrum

Measured 2026-10-04 by our weekly probe, which calls eth_getProof through the same Arbitrum endpoint customers use.

What eth_getProof does

Returns an EIP-1186 Merkle proof for an account and selected storage slots, which a client can verify against the block's state root without trusting the RPC provider.

Example request

curl -s https://rpc.swiftnodes.io/rpc/arbitrum?key=YOUR_API_KEY \
  -X POST -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_getProof","params":["0x0000000000000000000000000000000000000000",[],"latest"]}'

import { createPublicClient, http } from "viem";

const client = createPublicClient({ transport: http("https://rpc.swiftnodes.io/rpc/arbitrum?key=YOUR_API_KEY") });

// Any JSON-RPC method, typed loosely: eth_getProof on Arbitrum
const result = await client.request({
  method: "eth_getProof",
  params: ["0x0000000000000000000000000000000000000000",[],"latest"],
});

Other methods on Arbitrum

• eth_getLogsSupported
• eth_getBlockReceiptsSupported
• eth_feeHistorySupported
• eth_createAccessListSupported
• debug_traceCallSupported
• trace_blockSupported
• trace_transactionNot available

eth_getProof on other chains

Support differs by chain; the full measured table is on the eth_getProof reference.

• Ethereum
• Base
• Optimism
• Polygon
• BNB Smart Chain
• Avalanche
• Sonic
• Linea
• Scroll
• zkSync Era
• Blast
• Mantle
• Gnosis
• Celo
• Berachain
• Monad
• Unichain
• Kaia
• PulseChain

Frequently asked questions