typalog Public anchors

Public anchors

Typalog's daily roots

Once a day, at 00:10 UTC, Typalog computes a single Merkle root over every session summary chained and every certificate issued that day, and submits it to independent timestamp authorities. No daily root has been anchored yet. A certificate's verification page names the day it was anchored; this is where you check that day's root and follow the receipts yourself.

  1. Countersigning key

    cfc2fe507f870893 · ed25519

    79MulCO6ALWzPqoBbbHu6nDxwqiEihVEIph9abjNEOg

    Every certificate an author issues is countersigned with this key, so a reader can tell a certificate the author signed from one this server produced alone.

    held by Typalog
  2. Root signing key

    P-256 · PEM

    -----BEGIN PUBLIC KEY-----
    MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE1CGorDjkBSN59tC+RCTxfTa9dKTN
    uutHn0ehsmpZqTdrOVnYjKtRk+hIMWSh+ezp2pvbxzZInL9SjRxcUeVZnA==
    -----END PUBLIC KEY-----
    

    Each day's root is signed with this key before it is submitted; the Rekor entry records the signature.

    held by Typalog
  3. Timestamp authorities

    —

    Receipts appear here the first time a root is submitted.

    held by third parties
Roots
1
Anchored
0
Pending
1
Leaves
0

Newest first · dates are UTC

  1. 01

    2026-10-01 daily root

    e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855

    • No receipt yet. The root is submitted at the next anchoring run.
    Leaves
    0
    Receipts
    0/0

    pending awaits the authorities

1 of 1 root · 0 anchored · 0 leaves Anchoring runs at 00:10 UTC

A leaf is either the chain hash of one session summary or the sha256 of a certificate id. Nothing in a leaf identifies a person or reveals text. The evidence bundle on any verification page carries the full receipts, including the RFC 3161 token and the Rekor entry, for offline verification with typalog-verify.