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.
Overview
Bitcoin is a public proof-of-work blockchain that Truestamp uses in two independent
roles. As an entropy source, each new Bitcoin block is
captured as an entropy observation whose entropy object is
{network, payload: {hash, height, time}, source: "bitcoin"}, evidence that whatever
names it was submitted after that block existed (see
external entropy sources). As a commitment chain, each
Bitcoin epoch’s epoch hash is written in
a transaction output whose script is exactly 0x6a 0x20 followed by the hash’s 32 bytes,
as part of Block Commitment, covered in
the epoch and Block Commitment. Bitcoin epochs go out at most
about once an hour, and less often when fees are high, so a Bitcoin commitment comes later
than a Stellar one.
In a proof bundle a Bitcoin commitment is the
commitments.bitcoin entry: the epoch (its epoch_hash and record), the block’s
inclusion_proof into the epoch’s tree, the network (mainnet, testnet or
regtest), the height of the Bitcoin block holding the transaction, its
transaction_hash, the raw_transaction and txoutproof, and the header_hash,
header_merkle_root and header_time recomputed from them. The entry appears only once
it is final, when the chain is 10 blocks past that block, and a verifier online reads the
submitted-before edge as the median time past of the best-chain block at height + 10.
- Bitcoin: A Peer-to-Peer Electronic Cash System
- Blockchain-based Infrastructure for Proof of Existence in eGovernment
- How Does OpenTimestamps Work (r/Bitcoin discussion)
- Stellar
- Taproot: SegWit version 1 spending rules (BIP 341)
- The Inventor of Blockchain Would Like a Better Bitcoin
- Tsunami of Blockchain Technology and Patents: A Strategic Data-Analytic Overview