The digest job batches revealed bounty pulls and shared draw records; standalone raffle proofs are not in this chain. Each batch links to the previous one. Save a tip outside our control, then use it to test later continuity. Without that external copy, we control both the database and the published feed.
Cache this hash today; verify it tomorrow:
5b774ff83199b171205e0d528ff1764de4bb19bbd25b13a6ddd74992a60afdecDigest #1 · root f8af7e09…c6afef · 1 leaves · published 25 Apr 2026, 17:10 UTC
Most recent first. Each row's chain_hash = SHA-256(prev_hash || root). Walk forward from any earlier digest by re-applying that formula. If your computed value at any step differs from the published one, something between has been rewritten.
| # | Window | Leaves | Root | Chain hash |
|---|---|---|---|---|
| 1 | 23 Apr 2026, 20:57 UTC → 23 Apr 2026, 20:57 UTC | 1 | f8af7e09…c6afef | 5b774ff8…0afdec |
| genesis | before any commitment | — | 00000000… (zeros) | 00000000… (zeros) |
Older digests via /api/verify/chain (paginated, JSON, CORS-enabled).
chain_hash = SHA-256(prev_hash || root).This is a hash-linked log, not blockchain consensus or an external timestamp. Its rewrite-detection value begins when someone stores a tip outside our control.