delphi.consensus.snapshot
Appended 23 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 - 2073
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 29f1e88a-b6de-480c-bc2f-f234c647455d- logged_
at 2026-09-23T05:31:22.071283+00:00- previous_
hash b4906b4c43c49539a39c1c361e7d2e53336ea91d870104fdf8d422efa693aa98- payload_
hash c0872682ea1a4d4f386c92a2b156c27e0f6fd7aaa85e51e80c9c112016c41d05- entry_
hash d2c5102b693fcb759dcbd23bc255d4ef29eba0515c4a4ad8477d3e23afad1aa9
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-23T05:31:22.055424Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "29f1e88a-b6de-480c-bc2f-f234c647455d",
"series_commitment": "b15811109933fb8130e8f6597c83d87da76334a0553ad91611be9a2dff4dff4e",
"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
e924e20e634190d2c15f7bc95d7dcfb8f9662475578f05560326f15f11df54f2- 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 - 2073
- tree_
size - 2515
- leaf_
hash 5e62137f5156e81adbefe2c59f1cf576d61f291cdfbf92a75d7ff6d09917eee3- audit_
path (10) 0: 72585fd665dd2da71d988ab01c3645595e1efea81742eb3fcbefd4875cc1fa221: 25343027cf577ac81460ba59a50a165c67a835dc994de561cb44834be35b89cc2: 64b188e7e6ed6adaed3d2e2386a758ada1760fe016515298d221c2d739b474743: 47f6fa8eb19b5b350ec3054214a6c4629129dff19ced8a87a6f0c54fa268741f4: bf44c0f23985ec73ba70f8bc29b0f6ad4f1e936885cc5a45e5476c3db4d6f6c85: 02d0dde49bb94e626ee08c2578f2d51d2b820b89a132a330ac2c7e0011eed04b6: 97e580b0f254128201e36dc81f73bca17443fd5e21d28fd611b3832d3123cce37: 32d97e61743fccf6d32da7a407cb944cdd5c52aa0de4e874e2c78dadf7892a908: 42bcd2f1a75494aef2c027c7b7df37127b336fd1fc6fe4575a64ee72af9e41b19: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 94ed3e67e0f3ca6ab90e872a7f03020d191548311e8610028e47ddc18fbfbf90
The earliest published head that covers this entry
- tree_
size - 2083
- signed at
- 23 Sept 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash d6c88688a6cd2ce0afacd2220cfe05c6666fc242ec7f9ac09129b8d0bc00fb0f- signature
bLHEfkVSe/EJZc/PD8usy+UPLY2Y2/f+Mxks+W/Ea8Ln6XdDXICDe9lU9Oos68dZVS29/4k0IitE7SmvpTB5AA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10