delphi.consensus.snapshot
Appended 17 Sept 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 - 1909
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3b1bf8d0-fa87-4392-b4cf-333e6cba3622- logged_
at 2026-09-17T05:31:41.634289+00:00- previous_
hash 05a35f93689419e47a2a3b22b190387f0f1f8f8f3fb5c7f2f92fc889126c04df- payload_
hash b52575f6a29c8275ea078dc92bbd4b4760b5d5e380969da0aefdc3da89980300- entry_
hash cc566805a86080a96f539d2989230029a261592b2a64715ad6b01201d1bf1dc0
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-17T05:31:41.625470Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3b1bf8d0-fa87-4392-b4cf-333e6cba3622",
"series_commitment": "5b7eb00d34c25998c43f6551a5c40b2fc86030741daef66a0938c613c4394860",
"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
94e17e3858d989aa8f176e0645c5a7ea3565d2a021f5735690505a14f002e81c- 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 - 1909
- tree_
size - 2285
- leaf_
hash c68738d2f71df69edac885d0680c939d3e75a2eabee2c5f32b4a60cef06615b3- audit_
path (12) 0: 89ad4e66e9887d99963f5f29087a1b6b0e7dd413c924dc218353f7cc553791941: 41b791d3a2e05e0d51de2419d676815f50c9c393eecdcaf7699aabd2541ac37c2: 13520e9dae773240e458313172c598e075b149eec5ab07ce6047d1dbe8450d2c3: fff713e27c9f73fdaeb0f1cc0f6921ea4e557b582b9b03fe258a9379082f93ee4: cc6b75f197277762b6837a9f28956ddb80000209e849f7395b445025b8a73d975: 8163d9522cee5c395b431cb6244dc9be07640c46717beda36e36f07660c958786: e58805ff3adab5c7bd3bd83274fc881f7ac4f076b0dd834beda95d34af7800d77: 250a7c52b8fa3c4932ca872a3a7842e2fb00579ab86c9b5fb8782329fdedf9fc8: 5ab1df6751f0dac25a6ce29d97587d6e08dcdd2d94987223ead725483527e08e9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: a95d574e00e9fefbc454b084e8cb19edc83831071366b2d8dc1af2f7114b646f- root_
hash 17330c6327e6363b8237bd4a68d5ee420a6d0f745c8d8bab0a90305d6bccba50
The earliest published head that covers this entry
- tree_
size - 1921
- signed at
- 17 Sept 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash de4645b3ae57c2a319bdaadccc8424330c3686a79d031b007b80eca0ed78c863- signature
XoarI5Mzcez/Mayoy5WfSvWoXgXCDcdhQdMw2EQ2bH4TFS2FfvvlUkHv+csOCREKJBJN95gFWB6udc2z582ZCw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12