Select the correct archived Blobstream commitment for a Celestia height

Legacy Blobstream proof queries identify a range with an exclusive upper bound. Historical verification needs the commitment actually recorded by the destination contract.

Resolve the interval first

For a recorded interval from 1200 to 1220, request a data-root inclusion proof for 1219 against that interval. To verify 1220, locate the next appropriate recorded range. Keep the destination chain, contract address and commitment identifier with the proof so a verifier cannot silently substitute another deployment.

archived commitment covers [1200, 1220)
height 1219 → inside
height 1220 → find another commitment

Distinguish two levels of inclusion

A successful root proof binds a Celestia data root to the historical commitment. A claim about actual application shares also needs their path to that root. The documented Succinct-operated SP1 deployments stopped receiving new commitments, so check the archived contract's last covered height before requesting proofs.

Sources