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 - 2072
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id f69e4ff3-bcaa-42f5-a8f1-8044a9975b0f- logged_
at 2026-09-23T05:31:22.035421+00:00- previous_
hash 269aaf04f5917e06a045fedc0e0e5b1a9f91cffa5143da4825d4b24fb487ec61- payload_
hash 661315d3f0216d38614a2a6100fccd3fd29bae75afd9ad7782c556b9da23d4bd- entry_
hash b4906b4c43c49539a39c1c361e7d2e53336ea91d870104fdf8d422efa693aa98
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.016458Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "f69e4ff3-bcaa-42f5-a8f1-8044a9975b0f",
"series_commitment": "fbd87fc827041271d10116086c49971fd893eb73c569edc0df2af14759f13bf9",
"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
a5faeea3ec5da5f325de6c93dac0b143a1c439625a7bfc52e50f4edc87bb4f87- 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 - 2072
- tree_
size - 2285
- leaf_
hash 72585fd665dd2da71d988ab01c3645595e1efea81742eb3fcbefd4875cc1fa22- audit_
path (9) 0: 5e62137f5156e81adbefe2c59f1cf576d61f291cdfbf92a75d7ff6d09917eee31: 25343027cf577ac81460ba59a50a165c67a835dc994de561cb44834be35b89cc2: 64b188e7e6ed6adaed3d2e2386a758ada1760fe016515298d221c2d739b474743: 47f6fa8eb19b5b350ec3054214a6c4629129dff19ced8a87a6f0c54fa268741f4: bf44c0f23985ec73ba70f8bc29b0f6ad4f1e936885cc5a45e5476c3db4d6f6c85: 02d0dde49bb94e626ee08c2578f2d51d2b820b89a132a330ac2c7e0011eed04b6: 97e580b0f254128201e36dc81f73bca17443fd5e21d28fd611b3832d3123cce37: efcc4e356fa145279b69819abc96c5259a53132a5795adfcb75b75a472cb37b58: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 17330c6327e6363b8237bd4a68d5ee420a6d0f745c8d8bab0a90305d6bccba50
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: 9