Knowledge Base

Browse the concepts behind Truestamp. Follow the links between concepts, or search across everything.

t type code

Truestamp proofs carry no integer t type code; a proof names its subject in its type member (block, beacon, item, entropy_nist, entropy_stellar or entropy_bitcoin), and the proof's signature covers that member through the proof hash (0x50).

Overview

A Truestamp proof bundle has no integer type code. The proof names which kind of subject it is about in its type member, as text: block, beacon, item, entropy_nist, entropy_stellar or entropy_bitcoin.

That member needs no code of its own to be bound. The proof’s signature is made over the proof hash, SHA-256(0x50 || JCS(proof)), which covers every member of the proof, type among them, so changing a bundle’s type breaks its signature. This is what makes a beacon proof distinct from a plain block proof over the same block. The prefix 0x50 and the other bytes are listed in the byte-prefix registry.