Resume a Solana address history scan after an interruption
A worker that remembers only the last slot can skip transactions when a page ends halfway through that slot. The signature at the page boundary gives the worker a precise place to resume.
Read a short page first
POST this body to a Solana HTTP RPC endpoint. The Vote Program address makes the ordering easy to inspect on an active cluster. Replace it with your tracked address when building the index.
{"jsonrpc":"2.0","id":1,"method":"getSignaturesForAddress","params":["Vote111111111111111111111111111111111111111",{"commitment":"finalized","limit":3}]}
Read result from top to bottom. If the three signatures are A, B and C, A is the newest. To retrieve older entries, repeat the request with before set to the full base58 signature C in the configuration object. Keep the same address, cluster and commitment.
Save the rows and cursor together
In one database transaction, insert the page and save its last signature as the backfill cursor. Use the cluster, tracked address and signature as a uniqueness key for these rows. A retry then repeats the same page safely, even if the process died between receiving the HTTP response and committing the database transaction.
Interpret the oldest result
An empty page ends the history visible to this endpoint for the query. For an archival import, compare the oldest returned slot with your required coverage and record any unresolved interval. Each row means the transaction referenced the address. Inspect the transaction instructions, its execution result and balances before classifying a row as a transfer.