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 - 2296
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3b91df80-00fc-4a4b-b86e-3310edcb9332- logged_
at 2026-10-02T05:31:30.671153+00:00- previous_
hash 25364807e6b4f37aaa30ca9485d725652cfb7b8e64e5b3bfe59e54b3d24c650a- payload_
hash 9a67e1adb5223ad54b2dc0bc906d6269d63543caebaa91f2d236f1a3ff59a759- entry_
hash c90353c460c384fd128a22189f6ba33c75037b9c90531617b8fa8b10bc157941
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.665104Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3b91df80-00fc-4a4b-b86e-3310edcb9332",
"series_commitment": "ca8efc787c1dd3539e2bde850ffa4cc392bfb5b0a84768b0257769ab8abdc39d",
"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
f4f7c2053535b09e5b113f4bc3cadc525d299f32bd3da54de4260b755ea66840- 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 - 2296
- tree_
size - 2389
- leaf_
hash 171f3addf0a8c58654bffac79cfcacbb711623406b0e806b4020ae1bb2b122eb- audit_
path (10) 0: 1584c85b8c2a9248f5633cbd1d692515b310b89bbe8d223fadac25163047cf1f1: 687357d75748708648639e689c8806987932dcc29de08775127a009bfbfe23d22: 76b5915f856c519d46a8cbe892b50a47986862cacde062904ed0413e9dab9ff33: 821975498b70a458978b1728f99394b548b3d496bb3484413e2074cc663cece14: 56269504fdfcf4e0dc0a82cf9e12acaf348018dfa924c5db971bbf8af75594fb5: 453a26486f28dbe1e75e2f01f0d5e9fd3fe713113fe66b00eb5763b442ca537c6: cbc4db984571c13242d6f4b551c8d58b2ac60b14ae1df2945b6a2428d447c0bb7: 126596474757e47b31a2f4c9d89412108fada5bcdc7a19a9a1de3d4012be0b578: 03c349147789bfb063beb6c472906eef54792e9077566daa1ada925b4ce9b91b9: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 4f7f1a3085d540e3b69ac022c801823029c04ad350f74966858670c2038ea3cd
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