Every block since genesis. At the price of the tip.
Unpruned archive on mainnet and testnet, queried through the same endpoint you already use. On a half-second chain almost every historical read is an archive read, so we never charge a multiplier for one.
Where “archive” starts, 127 blocks behind the tip
On Arc almost every historical read is an archive read. We bill it at the same rate as a call against the tip.
Seven datasets, all from genesis.
Everything Arc has produced on both networks, retained unpruned. No rolling window, no pruning preset, no gap before a start date.
On Arc, history starts one minute ago.
The industry treats anything more than 127 blocks behind the tip as archive, and some providers bill archive calls at twice the rate. On Ethereum that boundary is about 25 minutes old. On Arc it is about 64 seconds old, which turns reconciliation, reporting and support lookups into archive traffic by default.
So archive is on every plan, and an archive call costs exactly what a call against the tip costs.
Query it, stream it, or take it in bulk.
Archive JSON-RPC
eth_getLogs, eth_call, eth_getProof and traces at any block, on the same endpoint as the tip, at the same price.
Pro and Scale
Backfill into live
Set from_block on any stream and history replays, then continues live on the same subscription, with a signed gap report.
Scale
Bulk export
Any dataset, block range or address set, delivered as files. Coverage is confirmed before delivery.
Quoted per request
The rest of the platform
Read last minute like it was last block.
Archive on every plan, at the price of the tip. Bulk exports quoted per request.
Common questions
No. Archive is on every plan and billed at the same rate as a call against the tip. At half-second blocks the usual 127-block archive boundary is about a minute old, so charging a multiplier would tax ordinary reconciliation.
To genesis on mainnet and testnet. Testnet backfills switch emitters at the Zero5 hard fork, where NativeCoinTransferred gave way to EIP-7708 Transfer events; the transfer feed handles that boundary for you.
No. Arc finalises a block on commit. There are no reorgs, no uncles and no confirmation depth, so a webhook is safe at one confirmation and a delivered record never needs a compensating write.