Latest Merkle root
The most recent signed receipt for our audit log.
- Day (UTC)
- 2026-07-01
- BLAKE3 Merkle root
- 4315f92ed8338814a7215c0ffb66ee7f0f6dec578c49ecc04aaaff7868aa2206
- ed25519 signature
- 13b11df01ebaf9fe64c6ca5539f441fed04171032a8467151ff8adc1da9c36e894a1f57211dee0249af48dae807ce493e86c0c2c75ab533f344c121413d88e0f
- Signed at
- 2026-07-02T21:45:12.770+00:00
- Events in the tree
- 8
- Signing-key version
- 1
What this proves
Once a day, every event in our audit log — moderation decisions, policy changes, the things we should not be able to rewrite quietly — is hashed into a BLAKE3 Merkle tree. The root of that tree is signed with an ed25519 key and published.
A published root is a commitment. If we later changed or deleted even one event, the recomputed root would no longer match the one we signed — the receipt would expose the edit.
Consecutive days are chained: each day's first link must equal the previous day's last. Deleting a whole day leaves a visible gap. And the receipt holds no user data — a date, hashes, a signature. Nothing else.