Register changelog chain verified ✓

An append-only, hash-chained record of every register change. Each entry commits to the one before it and to the resulting register digest, so the history is tamper-evident: recompute the chain and any alteration breaks it. Nothing is permanent, but nothing can be quietly rewritten.

Current register digest: defd46f5eaa4ac6584a04106b3024894c38cfb82ed9275dad085025b7f74986a · GET /api/v1/register.json (canonical bytes) · GET /api/v1/changelog (full chain + the recompute recipe).

1. #1 ratified claim-tag register 0.1.0 2026-07-31T20:06:43+00:00
   entry 3ff738115fd41b7e… ← prev genesis · register digest defd46f5eaa4ac65… · ₿ pending (in calendar) · .ots · canonical

Each version's register digest is anchored to Bitcoin via OpenTimestamps — a trustless not-after proving the digest existed by a block time, with no dependence on this site. Verify it yourself: ots verify -f {version}.ots {version}.canonical (both linked above; the canonical bytes' sha256 is the register digest). Fresh stamps show “pending” for a few hours until they land in a Bitcoin block. See /api/v1/anchors.