Knowledge Base
Browse the concepts behind Truestamp. Follow the links between concepts, or search across everything.
Tagged: commitment
16
Blockchain
Item Commitment vs Block Commitment
A commitment binds a record hash into the Merkle tree one level up, an item's item_hash into its block's tree or a block's block_hash into an epoch's tree; Item Commitment and Block Commitment mean those commitments exist, and why a proof needs both.
Public Ledger Explorer
The public ledger explorer pages, no account required - the /blocks index and /blocks/<block_id> detail with proof downloads, the /entropy and /entropy/<observation_id> observation pages, and the real-time /timeline visualization of entropy, items, blocks, and commitments.
The Epoch and Block Commitment
How Truestamp batches block hashes into an epoch for each chain, writes the hash of the epoch record (its Merkle root and leaf count) to Stellar as a hash memo and to Bitcoin in an OP_RETURN output, gives each block its commitment into the epoch, and replaces an abandoned Bitcoin epoch.
Glossary
Bitcoin
A public proof-of-work blockchain Truestamp uses two ways - new Bitcoin blocks are captured as entropy observations, and each Bitcoin epoch's epoch hash is written in an OP_RETURN output, which a proof carries as its commitments.bitcoin entry on mainnet, testnet or regtest.
Block Commitment
Block Commitment means a block's commitment exists: a commitment row binds its block_hash into the Merkle tree of an epoch whose epoch hash Truestamp recorded on Stellar (a hash memo) or Bitcoin (OP_RETURN); a block still finalized moves to committed in that write, at its first chain's commitment.
Commitment
A commitment binds a record hash into the Merkle tree one level up - an item or entropy observation into its block, or a block into an epoch whose hash is recorded on Stellar or Bitcoin - and its inclusion_proof walks to that tree's merkle_root; no commitment is signed.
Committed
The normal resting state on both Truestamp levels - an item is committed once its commitment into a finalized block's Merkle tree exists (Item Commitment), and a block once its commitment into an epoch whose hash is recorded on Stellar or Bitcoin exists (Block Commitment).
Epoch
The batch Truestamp uses for Block Commitment: the blocks after a chain's last recorded epoch form one Merkle tree, and the hash of the epoch record {leaf_count, merkle_root} goes on Stellar or Bitcoin; each chain advances its own series of epochs, and epochs are not signed.
Epoch hash
The hash Truestamp writes on a public chain for each epoch - SHA-256 under prefix 0x40 of the epoch record {leaf_count, merkle_root} over the epoch's block hashes - as a Stellar hash memo or a Bitcoin OP_RETURN output; a proof carries it in each commitment entry's epoch.
Item Commitment
Item Commitment means an item's commitment exists: a commitment row binds its item_hash into the Merkle tree of a finalized block, holding the inclusion proof to that block's merkle_root, and the item moves from processing to committed in the same write.
Stellar
A public blockchain Truestamp uses two ways: closed Stellar ledgers are captured as entropy observations, and each Stellar epoch's epoch hash is a transaction's hash memo, which a proof carries as its commitments.stellar entry on the public or testnet network.
Product
Submission Window
The submission window is the time guarantee of a Truestamp proof, that data was submitted after public records it witnesses and before a public chain recorded its block's epoch hash, each edge drawn by a verifier from public reads, which is why we say submitted rather than created.
What Truestamp Proves
The affirmative guarantees of a Truestamp proof, that the exact bytes existed unchanged and that submission fell inside a submission window a verifier draws from public records the proof names and from the public chain that holds its block's epoch hash, every hash it compares recomputed.
Verification
Proof Claims by Availability
Claims matrix for a Truestamp item proof - which of eight claims (bytes existed, unchanged, both submission-window edges, signature, key binding, ledger position, entropy freshness) hold from the proof alone, from chain or source reads, from a keyring, from Truestamp's records, or never.
The Proof Lifecycle
How a Truestamp proof comes to exist and strengthens over time as an item is submitted against a set of witnesses, committed into a block via item commitment, and that block is committed to Stellar and Bitcoin via block commitment, through an epoch whose hash goes on chain.