Anatomy
What the Genesis Block Contains
The genesis block is not a transaction. It is the origin proof that every subsequent record in the network derives its authority from. It encodes the founding parameters, the identities of the signers, and the cryptographic commitments that bind the network to its initial state.
Every TIP-ID issued, every trust score computed, every VP accredited traces its chain of trust back to the genesis block.
chain_idtip-mainnet-v2
Network identifier. Distinguishes mainnet from testnets and future protocol versions.
timestampISO 8601 UTC
Exact moment the network came into existence. Immutable once written.
founding_signersML-DSA-65 public keys
Public keys of every founding Council member. Their identities are permanently recorded.
protocol_versionSHAKE-256 hash of spec
Cryptographic hash of the TIP Protocol specification the network launches under.
trust_parametersScore weights, thresholds
Initial trust score weights, revocation thresholds, and cryptographic algorithm requirements.
signaturesML-DSA-65 per signer
Each founder signs the SHAKE-256 digest of the canonical JSON payload. Post-quantum secure.
Cryptographic ceremony
How the Genesis Block is Signed
Each founding Council member holds an ML-DSA-65 keypair (post-quantum, FIPS 204). The signing ceremony produces an immutable, cryptographically bound record that no future technology can forge or alter.
The ceremony is designed so that every signer produces an independent signature over the same deterministic payload. No signer can alter the payload after another has signed. The block is complete only when all founding signatures are collected.
Payload assembly
The genesis block payload is assembled with all protocol parameters, initial trust score weights, and the ML-DSA-65 public keys of every founding signer.
Canonical serialization
The payload is serialized using canonical JSON with deterministic, sorted keys at all levels. This ensures every signer produces the same byte-identical representation.
SHAKE-256 digest
The canonical JSON is hashed with SHAKE-256 (FIPS 202) to produce a 32-byte digest. This is the value each founding member signs.
ML-DSA-65 signing
Each founding Council member signs the digest with their ML-DSA-65 private key (FIPS 204). This is a post-quantum signature, resistant to attacks from future quantum computers.
Signature collection
All signatures are collected and appended to the genesis block. The block is complete only when every founding signer has contributed their signature.
Network publication
The completed genesis block is published to the TIP Protocol DAG. It becomes the immutable root. Every subsequent record in the network traces its authority back to this block.
By design
What the Genesis Block Does Not Contain
No private keys
Only public keys are recorded. Private keys never leave the signer's device.
No personal information
Only cryptographic identifiers. No names, addresses, or biometric data.
No commercial terms
Licensing and fees are governance decisions, not protocol parameters. They can evolve. The genesis block cannot.
No expiration
The genesis block is permanent by design. Protocol upgrades create new blocks that reference it. They never modify it.