delphi.consensus.snapshot
Appended 7 Oct 2026, 05:31 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 - 2388
- 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-10-07T05:31:41.200037+00:00- previous_
hash caf087ed679ed11f5e3f7636ef3ae002718ab4cabba15dcb45b7337fdf3d8c42- payload_
hash d9232ae695c9a9141bf42337d4ed80587f1ecd7589526ab5a4c3294732dc3656- entry_
hash c47eabebf3c26b0baf97f3ca3d85734ede4e636106aa40d916c6ea8c430bcbc0
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 - 2388
- tree_
size - 2389
- leaf_
hash 3d180480d4b938455f9bfc979250cffcc1f4b8ad0d256c32c6e08cf2617e950f- audit_
path (5) 0: 9a28383f6ab75565f2cb8666739e4a3965fac43da27d79c9ee84220590813cbc1: 5a9b5c3bbfe4872d51680afcd853c4eed3977ea9a65a63d48e58875c83d6ee142: 834c6985c52ea8f25de55920638ea90cbddfd15c7f0b1819c969144787359e5b3: 765303d6f29939e50694ecde6538ee53e894bb299166d5a65c9a000adbb546d94: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 4f7f1a3085d540e3b69ac022c801823029c04ad350f74966858670c2038ea3cd
The earliest published head that covers this entry
- tree_
size - 2389
- signed at
- 7 Oct 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 4f7f1a3085d540e3b69ac022c801823029c04ad350f74966858670c2038ea3cd- signature
UvlhE38UEMJnByU4DF/P6uC9M52OV15VOwl/s2iGtS9adIxo97fOZi78iEbiFPZnaVezyW7TYC3vGMp7K4L4Aw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 5