delphi.consensus.snapshot
Appended 15 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 - 1856
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3b91df80-00fc-4a4b-b86e-3310edcb9332- logged_
at 2026-09-15T05:30:21.956558+00:00- previous_
hash e0ee5d2451b1d052b346e0ad33d63d0f540401a831bba30ab2704f3c1356ab54- payload_
hash 15ee02c50c6c62560fada4cdc7a954798d6346656c08f08480967ce3cbfaf414- entry_
hash 1e65fc83d3d1b3e93f0057aff7e8a2168a3f96330b0c67f452582c054bfc790f
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-15T05:30:21.953636Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3b91df80-00fc-4a4b-b86e-3310edcb9332",
"series_commitment": "7c2ae06980127c7472a3571cfc9964c211a6e097571a907a5ca7dbf31c39cce9",
"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
abda37b1af428a3dc80dfbfbd4b852a38e81d3829fc51ea7b5ccb8f9598d3eec- 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 - 1856
- tree_
size - 2479
- leaf_
hash a2f00cd82d8dd5b83d81f0ca3b235a608064fb6e0b7381d14303ad1127cd7bc0- audit_
path (12) 0: e1449e286543a178a9c6d93e405c357f9056e9302ea70977abc469d0fb8f5c241: 5b4a3f887f3dd77d2b725a135d84c675c671211b5accdb43802c124ee39873752: 77651fc75f1468e2949916a814094a43204589e1eef0080486c11b2d23078b203: 0f72edbd00b7e20318851e9d772c9f1bcca9dd35f9b2d22d6a058a2ccb6bc1cf4: 202befe4b65cb05878a1d8057927d70f7369b2933880a3e13df111e36b9806015: 43eb768390db459ff2c2ed043a4367c5e85067784799ab09a2d0ea1fb483838c6: e58805ff3adab5c7bd3bd83274fc881f7ac4f076b0dd834beda95d34af7800d77: 250a7c52b8fa3c4932ca872a3a7842e2fb00579ab86c9b5fb8782329fdedf9fc8: 5ab1df6751f0dac25a6ce29d97587d6e08dcdd2d94987223ead725483527e08e9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 8d949d6aef53b2e3322ef5e232755263eaea63b886b405d936c87ac0c842b6a1- root_
hash 2135d33fc3b42de9408df8505e145fcd175142e943af391ea41c56bc99a1e5e2
The earliest published head that covers this entry
- tree_
size - 1865
- signed at
- 15 Sept 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 427bf2bb2a98f93b15991ac63679b5a7f92ae8259a18db989996a524a71b76be- signature
EcGlY9qjqofgO7lsm+1/zVG9o/1xzsbo+7505gXxzgCW8Wq/LV/2deEp+x9fw83j8tPY4Khkq0kRQqf6RXRzBg==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12