delphi.consensus.snapshot
Appended 2 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 - 2298
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id a8c36f16-c0df-49f5-92d5-29bb1d0e58a9- logged_
at 2026-10-02T05:31:30.692769+00:00- previous_
hash 98bafb6c18b60814c3c5b08281ce05fa1e92a32b3298463371ea17186f72686b- payload_
hash 7d2fd98c0f912672beef91427032aa9b45653e3ac3b80b25a6163dbd9c465c36- entry_
hash 882aa29f6908c55efa91108f741851671b06260347e95a608db77da938cce63a
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-10-02T05:31:30.688882Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
"series_commitment": "86465a7f9ab0332b12cdb5e3abe2c8e4e1615032efbf66d0a5c6ef414f6d1d08",
"commitment_version": "v2"
}Shown indented so it can be read. The hash is taken over the canonical form of the same object — keys sorted by code point, no insignificant whitespace, UTF-8 rather than escaped ASCII, timestamps RFC 3339 in UTC to microseconds, decimals as their plain string form. The check below re-encodes the object canonically before hashing it, which is why an indented display cannot make it pass or fail.
Which digest recipe applies
The entry names its own version, so a reader can pick the right recipe without knowing when the salt was introduced.
sha256(canonical_json({question_id, computed_at, salt, readings})), where readings is the batch's populations sorted by population, each carrying exactly {population, method, method_version, sample_size, distinct_operator_count, value}
- salt
d3672c21844093ed8a3cafd43c6e8c37248fb1f72383cad15b6e86d1a9d547a6- readings
- 5
- recompute
- sha256(canonical_json({question_id, computed_at, salt, readings})) must equal series_commitment in the payload above. Take question_id and computed_at from that payload verbatim, sort readings by population, and give each reading exactly the six keys served here — the values carry their stored precision and are hashed as the decimal strings they appear as
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 - 2298
- tree_
size - 2479
- leaf_
hash 99437004a00d803c1cc7b55d489ccd1312ba5dafbe9e1b8252e6ccc9800f2192- audit_
path (10) 0: f5e49653235c005ff62d57bf9ca40adcc2f09c2c3d7988a2e5f4e4e1e7f07e001: 1d820cd19d678cc0be6d6fa06c5b5a9f50678e79c3b982ed1c78618f5f8eab962: 76b5915f856c519d46a8cbe892b50a47986862cacde062904ed0413e9dab9ff33: 821975498b70a458978b1728f99394b548b3d496bb3484413e2074cc663cece14: 56269504fdfcf4e0dc0a82cf9e12acaf348018dfa924c5db971bbf8af75594fb5: 453a26486f28dbe1e75e2f01f0d5e9fd3fe713113fe66b00eb5763b442ca537c6: cbc4db984571c13242d6f4b551c8d58b2ac60b14ae1df2945b6a2428d447c0bb7: 126596474757e47b31a2f4c9d89412108fada5bcdc7a19a9a1de3d4012be0b578: fc41f233aac25cd7d868667ffe62e2d6bc79ebfa41e20ba3937ba4144f68af369: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 2135d33fc3b42de9408df8505e145fcd175142e943af391ea41c56bc99a1e5e2
The earliest published head that covers this entry
- tree_
size - 2305
- signed at
- 2 Oct 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 9259657b60d7c54c7f061a7a621bf2f8747cab0885ee335ac1ed3b6657c9740d- signature
WfaSA8uSPhU8mvAT09WSYyaV+8AjW2OH2C29VedwxnNkQky7NRQ2w/7a45+O74SQ2CV2uNogXj7mAjlPE7C7Cg==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10