delphi.consensus.snapshot
Appended 26 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 - 2151
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 29f1e88a-b6de-480c-bc2f-f234c647455d- logged_
at 2026-09-26T05:32:12.199634+00:00- previous_
hash c5d7fa098864ba62f6d7fdf5ad70219dd4d3ba72c1f03b9600bfcab78d0c09bf- payload_
hash 442ad533f50fce66efa8e6980836eacf823cd5342951840462a0750463cab63e- entry_
hash e4c8b3dc534f9b25cdd5cd0cb07e448edf35f334a661635495cc1aea587df48b
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-26T05:32:12.192759Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "29f1e88a-b6de-480c-bc2f-f234c647455d",
"series_commitment": "79c142f49d9bc8a13bc95ba826edd2a8251ec89f0aa7139106c80e2846354e0a",
"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
fc9e693c4a9c70c3b7746dbd76058c6977672975abc9b0d4cc29d6b3163005d3- 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 - 2151
- tree_
size - 2389
- leaf_
hash cdbe66bfae7400a133ab80b38a1478f2cf6c20352e6803823af1be396aec4eb6- audit_
path (10) 0: 9d9877415d0380488832c7aade78a13eed1ba1a9fc966a84aef733848aefc6071: 016536415d1a69846ffc123121d9ba756d3107e6149d1c22ca09f59a708432322: 0edd2559db6e25e879ec30d5a24eb4387010244c4728d4461457c7891253138c3: 06ebb63ecc5f3ba91762a4967f1e1f7ededfb1029c017a34c598d9aabd16be0c4: ce84c24a1d3f5de3d333368de28d51a29649a866b4d9ce9379de23fb6e76ac895: 50cc49d79f0f3c552cc19006c4d6b819801e07bb4acb2a3fb50f66393c28555e6: f4d02cca79f588f9c172b1dc53f54784db35848f8f8b4fa96ae1493d76b463787: 32d97e61743fccf6d32da7a407cb944cdd5c52aa0de4e874e2c78dadf7892a908: 03c349147789bfb063beb6c472906eef54792e9077566daa1ada925b4ce9b91b9: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 4f7f1a3085d540e3b69ac022c801823029c04ad350f74966858670c2038ea3cd
The earliest published head that covers this entry
- tree_
size - 2161
- signed at
- 26 Sept 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 08d42dfc1a68825e48c5ebd6ef8deb02090b8acb5d1f2be9a9e2101b015a8fb2- signature
dB1NOOKbGZYlf8tpl8m7au97B5M49+4SOWOT1aR1A4WPqRzn123pmio+rP0C6SWMEK2kx1MBdDcTjVaJKZkTAA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10