delphi.consensus.snapshot
Appended 21 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 - 2562
- 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-21T05:31:54.532651+00:00- previous_
hash bff336c73dcff90ed39f183def9c69defeb0aaeca0ab2a3a768b2a440c1f5f9e- payload_
hash 0b1b6832c960317387b17212c8a2533eb4a5fc641421f016cc74a4470b476eba- entry_
hash cb5daa7fefe45bd9b8f595742ac29621df5bf2ed73a8a9a0085929b3b91bf03e
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 - 2562
- tree_
size - 2563
- leaf_
hash 575ae53117a3e82e3671c201a4d3b18d1ce7a9bd11cde9368fd82b0377882c47- audit_
path (3) 0: 658c8e604c7efec5c2eac0ea4c5739d29e240d0919ceb46a68e854196fac0b631: 371d091b0ba6b30ac6aab06e789b8b90b7db91bbed00556d5744bcdd2326cda92: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 5603f1f84862ea78f51857aab4dd05ce73ba33470baa2f6affe3d552f8604398
The earliest published head that covers this entry
- tree_
size - 2563
- signed at
- 21 Oct 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 5603f1f84862ea78f51857aab4dd05ce73ba33470baa2f6affe3d552f8604398- signature
Cqp+axFzyxPS8tSyLtRdS2EbtQC8pjloQ2t0Q0PALdSiaCzMkP8VnzNanlqKxo4FA/c0msZH8TDD221doJwMBQ==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 3