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 - 1854
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3b1bf8d0-fa87-4392-b4cf-333e6cba3622- logged_
at 2026-09-15T05:30:21.940270+00:00- previous_
hash b67b1a1fe307c78c6f930b8085ff5a78170f8f9fe87891a5b82f14d37fa62ddf- payload_
hash a359172b9b54bc5da274005395af42d9f2bc40a7ff8ee13379fac0be198f8a9e- entry_
hash 50f40f3ece398c3dec482eda6d30438b1b1fef03ba90ccdbb2abed07de67a828
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.936795Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3b1bf8d0-fa87-4392-b4cf-333e6cba3622",
"series_commitment": "35ba7a82a23ba2ed2738c31a4fa088450d2433a3b0e4462f891b7fc0a00d1103",
"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
75b168f8c0b1c9dfe95b9e40438d982e5aa4c511e674545fcf2d078f0a9d64d4- 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 - 1854
- tree_
size - 2479
- leaf_
hash ae258bc809d495e61f04d05917b23b3517becfe69b2353b108cff6ac6ec8333a- audit_
path (12) 0: 6b7a5cb31512e01d554feab26031550361e7ed1a27989cd4ccd81b957cf8a24c1: 3ea884f767bb4c87666623c26c825c9b7dfc8ce093993d3ddebfa07930c9696a2: d80e150f1e749d5a9ffc8fe2463b164fa85ec87cdbd30f02632804f2e55588bf3: 3c8b0e6179eabda78c695921c289317d14c291d50f46002c91a983657a5c78cf4: 28d95a796c3415f603452c087463ddc938a2da9111fbd6a9d3a058ba3fe979ab5: c9a4df0ae6aa1a7081046c730d33552311719b12e159dc5c1f9f2784f0628ab76: 66e877548a61fd36a62ff399c81b1533c5b6efa4d42185e861a4558efb824d297: 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