Offline verification
Checking a Truestamp proof bundle using only its own contents with no call to any Truestamp server, by recomputing domain-separated hashes, walking the Merkle inclusion and epoch proofs, and verifying the Ed25519 signature; on-chain confirmation is the only optional network step.
Overview
Offline verification means checking a Truestamp proof bundle using only its own contents, with no call to any Truestamp server: recompute the subject hash with domain-separated SHA-256, walk the Merkle inclusion proof up to the block’s Merkle root, derive the block hash, walk each epoch proof up to the committed epoch root, and verify the Ed25519 signature over the signed payload. The only step that touches a network is confirming that the commitment transactions actually exist on Stellar or Bitcoin, and it is optional: run with the offline flag (skip_external) and those checks report as skipped rather than failed. The step-by-step walk is in verify a proof, and the fields it consumes are defined in the proof bundle wire format.