debug_traceCall on BOB
Measured 2026-10-04 by our weekly probe, which calls debug_traceCall through the same BOB endpoint customers use.
What debug_traceCall does
Executes a call against a block's state and returns its execution trace (with a tracer such as callTracer), without sending a transaction. It is the standard way to see what a call would do internally before you submit it.
debug_traceCall on BOB: what we measured
- Default BOB routing keeps state for roughly the last 1,000,000 blocks (about 23.1 days of BOB history). Tracing 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/bob?key=YOUR_API_KEY \
-X POST -H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"debug_traceCall","params":[{"to":"0x0000000000000000000000000000000000000000","data":"0x"},"latest",{"tracer":"callTracer"}]}'import { createPublicClient, http } from "viem";
const client = createPublicClient({ transport: http("https://rpc.swiftnodes.io/rpc/bob?key=YOUR_API_KEY") });
// Any JSON-RPC method, typed loosely: debug_traceCall on BOB
const result = await client.request({
method: "debug_traceCall",
params: [{"to":"0x0000000000000000000000000000000000000000","data":"0x"},"latest",{"tracer":"callTracer"}],
});Other methods on BOB
- eth_getLogsSupported
- eth_getBlockReceiptsSupported
- eth_feeHistorySupported
- eth_getProofSupported
- eth_createAccessListSupported
- trace_blockSupported
- trace_transactionNot available
debug_traceCall on other chains
Support differs by chain; the full measured table is on the debug_traceCall 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
Frequently asked questions
Does BOB support debug_traceCall?
Yes. debug_traceCall answered correctly on the SwiftNodes BOB endpoint in our weekly method probe (2026-10-04), which sends real requests through the customer path.
Are there limits on debug_traceCall on BOB?
Default BOB routing keeps state for roughly the last 1,000,000 blocks (about 23.1 days of BOB history). Tracing against a block older than that needs historical state. Add &archive=1 to send the request to archive upstreams (paid plans).
BOB endpoints, live block height and WebSocket status are on the BOB RPC page.
One key covers every chain we serve, and SwiftNodes has a free tier.