delphi.consensus.snapshot
Appended 25 Sept 2026, 05:30 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 - 2125
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 29f1e88a-b6de-480c-bc2f-f234c647455d- logged_
at 2026-09-25T05:30:42.636918+00:00- previous_
hash a6e42e27d9d786644e2f057ff12c580cf967afaf31e60b325817c02023f5cba2- payload_
hash 3981cde47aedbf9c8c753584b3803f2e767ac3818960c3e1f9f0f6c81382adfe- entry_
hash b8a2cb4c7091bb0623ac9e8432dc853fd3e7de94286e913a80f9e0faf7c8e7fc
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-25T05:30:42.630619Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "29f1e88a-b6de-480c-bc2f-f234c647455d",
"series_commitment": "e11bcd66e95761a495267ad45ace82e010d7670a6daf276abe3ad389e72f57bc",
"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
152972a5e3c4fcd2b9e071e7e1a1189c6398a33a5f17c3292929b0cdb04a721d- 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 - 2125
- tree_
size - 2357
- leaf_
hash 7ac82b284d7a911e1f5ee0064ffb9eb783ccf240790074013d997e2278d28358- audit_
path (10) 0: 76b4b52967b66867c38e7a0b401a7071392722c073f638ce8c976449278b8c471: ea4f1269d097e15f33774463c9ad802e2716eb0be793f528469932d23b3878f42: 32edc6d61ad755463350f5d7e7e10af43a0f9889d2ac3e5d5a2833b32ba8bd7b3: 9958dd2f7a6055b116651c7bfb66a013f79bf3ac76ed1c646924a897672e45374: d939d81632dfc335e3bf2cb2617a9ef02fad423763ee0ed0672db12825d2348c5: 559bc6d68b20ef3ce754297613d102bda419cb61cab1971c2f441622cd86f40c6: f4d02cca79f588f9c172b1dc53f54784db35848f8f8b4fa96ae1493d76b463787: 32d97e61743fccf6d32da7a407cb944cdd5c52aa0de4e874e2c78dadf7892a908: b2c4aa6040f878f3778bb1b9f9de1e703711b5846ca7e47c80f789c39ae1714b9: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 58c8c5ab99dba36e8c6b398578e37592253a716c9cf756f72e78b6606a198d59
The earliest published head that covers this entry
- tree_
size - 2135
- signed at
- 25 Sept 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 45e4998f74d5c216e9d9da4088fefb456c0aa83e21edb4035f581e57b15431a0- signature
zdy+vfo0PbejA1KdjFDDhWpugBbEt8J/FMJk2Vz2wJbl7wwNofT7wjsVH+qSOXUuNAQhUmxVRVTnm/IWY5iEDA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10