Proof bundle
The self-contained, signed JSON file Truestamp serves for a committed subject - the subject and its record, its block, the block's commitments to Stellar or Bitcoin with their epochs, an item's witnesses and one Ed25519 signature, each declared hash beside its record.
Overview
A proof bundle is the single self-contained file you download when you timestamp something
with Truestamp: a .proof.json file of at most 65,536 octets that is an object with two
members, proof and signature. The proof carries the subject (an item’s claims and
record, or an entropy observation’s entropy object and record), the block that includes it
as a block node (for a block or beacon proof, the subject itself, and for a beacon the
latest observation of each source in it too), that block’s commitments to Stellar, Bitcoin or both with the epoch each one wrote, an item’s
witnesses, and the inclusion proofs
that tie the subject into the block and the block into each epoch. Its type member names
the kind of subject (item, block, beacon, or one of the three entropy types), and the
one Ed25519 signature covers it with everything else in proof, so a bundle carries no
separate t type code. A proof is generated only once the
subject’s block has a final commitment on at least one chain.
Two properties are worth stating plainly, because they are what make a bundle stand alone.
- Nothing in a bundle is opaque. Every hash a proof declares sits beside the record it is the hash of, and a verifier recomputes it and compares, starting every walk from a value it computed itself. No record contains its own hash or its own signature.
- An item’s bundle carries its witnesses. It holds the record of the head block and the entropy object of each source the item named at submission, so the submitted-after edge can be read from the public sources a verifier consults rather than from Truestamp. Every proof of an item carries every witness its record names; no variant leaves one out.
The field-by-field reference is the proof bundle wire format; checking a bundle is covered in verify a proof, and the path from submission to a downloadable bundle is the proof lifecycle.