RPC method

eth_getProof on Abstract

Not available on SwiftNodes

Measured 2026-10-04 by our weekly probe, which calls eth_getProof through the same Abstract 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.

What to use instead on Abstract

Abstract did not serve eth_getProof in our probe. Without proofs, read balances and storage with eth_getBalance and eth_getStorageAt, which you have to trust the endpoint for.

Example request

curl -s https://rpc.swiftnodes.io/rpc/abstract?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/abstract?key=YOUR_API_KEY") });

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

Other methods on Abstract

eth_getProof on other chains

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

Frequently asked questions

Does Abstract support eth_getProof?

Not on our Abstract upstreams: eth_getProof failed in our weekly method probe (2026-10-04). Abstract did not serve eth_getProof in our probe. Without proofs, read balances and storage with eth_getBalance and eth_getStorageAt, which you have to trust the endpoint for.

Abstract endpoints, live block height and WebSocket status are on the Abstract RPC page.

One key covers every chain we serve, and SwiftNodes has a free tier.