delphi.consensus.snapshot
Appended 15 Aug 2026, 17:40 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 - 180
- 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-15T17:40:22.571506+00:00- previous_
hash 07f23e9f2de2eafedbb1fd593b21627734ff68e292f880d7306000e1e46cf913- payload_
hash 92400c35bf06fed1c51cccf8025dbcc55b523433e7609ea131e280b272d88b43- entry_
hash 12f64915676705d30b61e34baa6d6b62dd2bf1ea38bbc80b0ec8de410ebb1036
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 - 180
- tree_
size - 182
- leaf_
hash 13b468c9082ddff23deee69d5c68e9422064281cf6175b010091bb481ccabf8c- audit_
path (5) 0: 4ab87c386288217d0876a2dbfb9fb31f25b6ab09a744216fac869769da3daf7a1: a7fb9e117bbd933cf360bde5ff374dfc3f1fdbd44ae75b28e7196f469438a1dc2: 4c662827fbc2b2e4df650edfb1debb0bf2901593e38d586ed8826b0586b79d183: dc65f705f8825b65cd837fbc21e908be23ce2e3613f86cab80adfa745e5e0d034: 8e3ada3865734ef89cf9ebd82b633327831f303fabc83306d43c8e1c4685702d- root_
hash 78d677b49a83d955e860fdeb8dc15d851c8ccab49527b7c4916ade29ac21adbe
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: 5