Register · the public backstop

Don't trust us. Verify us.

The register is the public, append-only record that lets anyone re-check our anchors independently — canonical-primary where the product lives, plus a public backstop so your evidence survives us.

Two layers, one record

Canonical-primary, with a public backstop.

Canonical · primary

The register we operate

The authoritative, low-friction record where attestation lives — the product. Fast and convenient, and the place the recurring Seal is recorded.

Public · backstop

An independent substrate

By design, anchors are also committed to a public transparency log — the model behind Certificate Transparency — bound by independent qualified time, so the record need never depend on us alone.

How it's published and re-verified — by design

Re-checkable offline, by anyone, against published roots.

  • A Merkle root of anchored evidence is committed on a fixed cadence — a single O(1) head that any gap or reorder would break.
  • Published roots can be pulled and recomputed offline by anyone — the same math, no account, no trust in the issuer or in us.
  • Inclusion is provable in O(log n); the head is O(1). The artifacts are the audit — re-verification needs nothing from us.

Evidence survives us

The record outlasts the company that started it.

A canonical register you could only reach through us would make us a single point of failure. The public backstop means the evidence — and the ability to re-verify it — outlives any one operator, the way a qualified provider's records must continue by law even if it stops.

The public backstop is being stood up. Local, offline verification of every receipt already works today without it — the open layer never depends on the register.