Taiko Archive Node RPC

Query the full history of Taiko — balances, contract storage, and transaction traces at any past block — with archive node access included on every paid SwiftNodes plan. No separate archive tier, no per-request fees.

Endpoint

https://rpc.swiftnodes.io/rpc/taiko?key=YOUR_API_KEY

Archive queries use the same Taiko HTTP endpoint — just pass a historical block tag. The matching WebSocket endpoint is wss://rpc.swiftnodes.io/ws/taiko?key=YOUR_API_KEY.

Query historical Taiko state

// Read historical state at a past block on Taiko (archive query)
const balanceAtBlock = await client.getBalance({
  address: "0x0000000000000000000000000000000000000000",
  blockNumber: 1_000_000n,
});

// Replay a transaction's execution trace (requires archive data)
const trace = await fetch("https://rpc.swiftnodes.io/rpc/taiko?key=YOUR_API_KEY", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    jsonrpc: "2.0", id: 1,
    method: "debug_traceTransaction",
    params: ["0x<txhash>", { tracer: "callTracer" }],
  }),
}).then((r) => r.json());

What archive access unlocks

• eth_getBalance / eth_call at any historical block number
• eth_getStorageAt for contract storage at a past block
• debug_traceTransaction to replay and inspect old transactions
• Point-in-time analytics, accounting, and reconciliation

Taiko is an Based zk-Rollup (Type-1 zkEVM), with ~~12 seconds (aligned with Ethereum slots) block times and soft: ~12s. hard (l1): ~10 minutes (zk proof submission) finality. Historical queries reach back across its entire chain history.

Frequently asked questions

See the full Taiko RPC page for chain details, or the API reference for the complete method list.