delphi.consensus.snapshot
Appended 15 Aug 2026, 15:53 UTC. Its place in the chain is fixed by the hash of the entry before it; what follows is whether that place is covered by a signature.
The entry
- sequence_
number - 11
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id - withheld with the payload. this entry records a consensus reading on a blind question, and it is appended whenever somebody forecasts on that question — so naming the question would say that somebody just did, which is precisely what blind mode withholds. The reading and the salt that opens its commitment are released when forecasting closes. The hash chain and every proof over it remain verifiable meanwhile.
- logged_
at 2026-08-15T15:53:35.401867+00:00- previous_
hash e4f4242fc96b20c3f6a74c2ff568960fba5fa14517c70c043ffd5b848835d43e- payload_
hash fc02e83f9431bdf33349205ad7de8b003d15d9de26b9a88cb868c99e6929249f- entry_
hash 70edc25e2d5cd73128a4eac170a2cc52ec3566b69c52f1087d0056cf6ac0f533
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload withheld
Payload
withheld by the blind gate
this entry records a consensus reading on a blind question, and it is appended whenever somebody forecasts on that question — so naming the question would say that somebody just did, which is precisely what blind mode withholds. The reading and the salt that opens its commitment are released when forecasting closes. The hash chain and every proof over it remain verifiable meanwhile.
The entry, its hash and its position in the chain are all here, and every proof over it below is fully verifiable — a verifier can confirm this entry exists under a signed root without being told what it says.
Which digest recipe applies
This entry carries no version key. Absent means v1 — the unsalted recipe from before migration 0021 — and that is the log's own rule rather than a guess made here. It is worth stating plainly because it is the opposite of the default a reader would assume: the newest recipe is the one that has to say so.
as above with no salt key at all. The shape every entry written before the salt existed was computed under; those entries are immutable and stay verifiable this way
No opening is served for this entry, so the digest cannot be reopened here. On an unsalted batch that is not a barrier — the digest opens from the readings alone — and on a salted one the salt is released on the same disclosure gate as every other surface.
Verify it here
Recomputing the hashes in this browser… If this sentence stays, this browser has no Web Crypto and nothing here has been verified locally.
The proof, as served
- leaf_
index - 11
- tree_
size - 179
- leaf_
hash 83756849c974b77d4758d4b9b842ee374adace5ea6400c54f7549a6d57339455- audit_
path (8) 0: b995d45c818eaa2918ffbfc0eb9e3af44883664545e905b554480a63a45f701f1: 47df66d308a32e7021b325d9d3dab64f38814a100bd3a4e4f89259e5cd0f084a2: a77f24677127c7bb35e52e72ee1428c6a7bfe467916fe7deeba51f69a6c00b483: d7c05425bf6e3fadbed68d9552781d28647454d6dad43f268ec9145a2b4220fe4: b70d290aa081a17cfd1dd59b61f1a28551b4aa8df2915bb773f8eda8b60841055: b74c92a6356a40d4a8987db99772ead75d18bf349905054ba53bbc3401d9b2b96: 432b3bec17cc8d9bd118f5d2d11fc56d0578ec1940af60be2192f2f1b8d43dc67: 3f76b135a3f3ce5dc862e0e2e004c9eff2bbf99040ca47c64d64cec42062fd34- root_
hash b6268ac6224d3cfeaf4fdd2e07881a4bb21cf8ed320580fb2a683f4427a55006
The earliest published head that covers this entry
No published tree head covers this entry yet, so there is nothing signed to check it against. That is the ordinary state of an entry appended since the last checkpoint, and it is neither a failure nor a permanent one.
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 8