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 - 1846
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3707c33d-0301-4c72-8c13-ee685e8a0a88- logged_
at 2026-09-15T05:30:21.838325+00:00- previous_
hash 1e49667255db18faae3b3cf13de65d424dddacb285b908f5339ff30631b8a61f- payload_
hash a969af0984c7bd07fd33478c9eb4c881c6e565bfe548966b3b2ae8970599d4ce- entry_
hash 128b1209d507d9568f16f7bb3e6abe3c4a7f50660b98e450e4ddc3cff3f6bcaa
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.831111Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3707c33d-0301-4c72-8c13-ee685e8a0a88",
"series_commitment": "ab6845575abada1d00a2e4da18614636587aa344915179ec80a4501364a4a1f1",
"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
42cd30774eee0f2c1ca7244866d79fcc231c30c44a651710c51967e74e2fb0df- 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 - 1846
- tree_
size - 2239
- leaf_
hash 7d71586a2227ac47a76446e6100d6d7709d01ccb6d1ecfe6582c7b5a50289e20- audit_
path (12) 0: 11aedb855965da9cacf802043f9ff4eb381aea108021da05aede75c4f2d013811: 6c18a79cb40cbd87b28864802818be94efc9a91397d92e3adf7482741d498bf32: 74e9c9967059fea86760f5a416ad9aa78a7fa49852bfe7c274b18458e80030003: 0e4ac6384eb340188315033d2d821c859a243c1f5c124a12c070a5a066a9e24f4: 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