delphi.consensus.snapshot
Appended 16 Sept 2026, 05:32 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 - 1884
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3b91df80-00fc-4a4b-b86e-3310edcb9332- logged_
at 2026-09-16T05:32:03.487298+00:00- previous_
hash 5851e95eff5f9f4ab6dbe8c8f0d6a3503fde426567200b4a4d9ada7f44ac0c02- payload_
hash bd2409c283d18ab016b46d95f8d00113e7188555f88560765614f8e48a3041ae- entry_
hash 44dbc9c1118b51a63bd0f2d9f18217100c662e3bd0bf64195cc3440a38b6399c
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-16T05:32:03.483952Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3b91df80-00fc-4a4b-b86e-3310edcb9332",
"series_commitment": "03d66bd16a2d04a77ef878896046903dba99de33dd53eb8ca97a8fc8fa308e20",
"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
01eb864cf4392fb880a8c801cc2bff5a7724cf807d265b12757e69009047fc13- 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 - 1884
- tree_
size - 2491
- leaf_
hash 87d45cb93953237042c093571bd469acda6d8944914b8b307e4fc11809ef4e32- audit_
path (12) 0: fa00c2b0061821de312c889c7617dd1821d4ae8ff031bac70ee01b0933d87cc41: 54e5c10a497ab1eb2e02e49d751353542d7de7241895148815d36e68d0af74cc2: 0c4327f795403f4e43d2cff789c60e942178daea4a1e08b91b9b8217381f28a53: 4c2db70f824b3c5e61332f3a5a550f0712c09a15e9e55d607b0955378e1d1ec24: 39f827cd96cb94a9f98d2fe79f258dadd64b7a357c8a9207a06aa935859d31eb5: 43eb768390db459ff2c2ed043a4367c5e85067784799ab09a2d0ea1fb483838c6: e58805ff3adab5c7bd3bd83274fc881f7ac4f076b0dd834beda95d34af7800d77: 250a7c52b8fa3c4932ca872a3a7842e2fb00579ab86c9b5fb8782329fdedf9fc8: 5ab1df6751f0dac25a6ce29d97587d6e08dcdd2d94987223ead725483527e08e9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 083d0806ed3c3d656f2d8c4762013d3fb4c0ed984cb03e95e8ae46936f2431df- root_
hash a9a1dac66ff7c8ec3d4b27b434ff70fbde5df3ef3dcd4b4fe4b41bb80f78a7c7
The earliest published head that covers this entry
- tree_
size - 1893
- signed at
- 16 Sept 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 2945d3fce4b045e69d9f4dcd9ec3245d9f33df6a4fad1e28da7f262978dd2df3- signature
wd6goG5LLThX3fPZ+aTodS8ZIhvpUh8GQnsa24awFJptoxP1GOtak9J2qUa7SXysOEjki45TElUl1ol36o+ZCA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12