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 - 1850
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id d1b83331-68f7-4be7-a625-f7824bccab5b- logged_
at 2026-09-15T05:30:21.895033+00:00- previous_
hash 7ff59746a2fb908bd7384a8326003b7198f2c5886e9cac07a1c7b8997e2d1f9e- payload_
hash 752b8a6fcb54f9ecc198890facd0b9595756644d2fe10334f829c616597b351e- entry_
hash 5e57871c7757eb9b20f574a647ed4b7bbd1f1e214a85e4894d64c453b53bf532
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.889478Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "d1b83331-68f7-4be7-a625-f7824bccab5b",
"series_commitment": "01b469a6bfc11d758aafb19502c52dc6e8c989e110e4068c86c4ec4875d8f6b1",
"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
2576c2f6762a864bd1a646bbb5d8ad712c687df6e0f4347831c45ed1f22d2923- 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 - 1850
- tree_
size - 2239
- leaf_
hash 2ea2fe2780fe0121d56cc000176bff5372e3f1f00572a2b8972d0f0fe46a85ac- audit_
path (12) 0: 76a131135e0300646ed0b1547cbc11fb572a0847ae4e7cc8fdd8feefb0ca8a7b1: d68aadea18699b8f21c32c5f0bd04e87cc622759d681ae2e5f820b6bcd724d5e2: fad128965d1671c0ae9d3dad9d3dcc2387a8f80a0b3268940c9fa51e81cc331a3: 3c8b0e6179eabda78c695921c289317d14c291d50f46002c91a983657a5c78cf4: 28d95a796c3415f603452c087463ddc938a2da9111fbd6a9d3a058ba3fe979ab5: c9a4df0ae6aa1a7081046c730d33552311719b12e159dc5c1f9f2784f0628ab76: 66e877548a61fd36a62ff399c81b1533c5b6efa4d42185e861a4558efb824d297: 250a7c52b8fa3c4932ca872a3a7842e2fb00579ab86c9b5fb8782329fdedf9fc8: 5ab1df6751f0dac25a6ce29d97587d6e08dcdd2d94987223ead725483527e08e9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 9203a1600de814d3afb819f841569332c7e3b58c4d0e0ea56c377729f25dca49- root_
hash 03dd6fb33b4bd65222257eec0069956926795f14f7354795bcb42af5fe51ba08
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