Latest Merkle root
The most recent signed receipt for our audit log.
- Day (UTC)
- 2026-06-09
- BLAKE3 Merkle root
- f312daab18b902ace2cdd55e64674d1ba2df619362f1a0ff9b37e8a5b367414d
- ed25519 signature
- 6111917f2dd6347d22f0761df821daea26d929b5923e7ba930369980156c31c7847fb0f54195ed23e2883559f3b19d4ef22f889d2a65e0456457a1ebb9632209
- Signed at
- 2026-06-10T04:40:54.804+00:00
- Events in the tree
- 50
- 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.