Knowledge Base
Browse the concepts behind Truestamp. Follow the links between concepts, or search across everything.
Tagged: inclusion-proof
5
Glossary
Audit path
The path member of a Merkle inclusion proof, RFC 6962's audit path and RFC 9162's inclusion path - the sibling hashes from a leaf up to the root, each 64 lowercase hex and at most 32, with no side markers, since leaf_index and tree_size fix each sibling's side.
Inclusion proof
The RFC 9162 proof that one leaf belongs to a Merkle tree, the object {leaf_index, path, tree_size} with at most 32 path hashes; a Truestamp proof walks one from the subject's hash to its block's merkle_root and one per commitment from the block hash to its epoch's merkle_root.
Merkle
Merkle Inclusion Proofs
How a Truestamp inclusion proof, {leaf_index, path, tree_size} of RFC 9162, proves a record hash is a leaf of a block's or an epoch's tree, the walk and its 32-step cap, the committed leaf count, how a submission window follows, and what is and is not provable.
Merkle Proof Encodings
The two encodings of a Truestamp Merkle inclusion proof - the JSON object {leaf_index, path, tree_size} that proofs and the APIs carry, and the fixed-width binary form Truestamp stores, 16 + 32 x d bytes - with their limits and a worked example.