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 - 1852
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id f69e4ff3-bcaa-42f5-a8f1-8044a9975b0f- logged_
at 2026-09-15T05:30:21.922993+00:00- previous_
hash f679bf23df1b9ce6d6540b977d81b3959775c8e58750ab5878df3eafa85093c5- payload_
hash a2f85974e0b3b09494111494bfef64ac70ca2494190b72cfff87d10d0bc8b3de- entry_
hash 9d393dca2e22236f61331ce49b36442b4ca2801573d73dd3a8f8fbc905d50304
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.917033Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "f69e4ff3-bcaa-42f5-a8f1-8044a9975b0f",
"series_commitment": "7ac452fb6066121827c17cfdb2cc3b04977e59d2b4e1fe91e20d49e93b2bd1b8",
"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
47b128eac0a06f5b663db8a59af5a45b8ce7ed2ce4a3c4fc1de4b7d8b91aa453- 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 - 1852
- tree_
size - 2479
- leaf_
hash cfe03246a832964491c2ffe0396df34cc422a603907b105f3de5d554c69c6722- audit_
path (12) 0: f9f4603dfd8dc1a4c5a0ba09f79b87e822d3c8fc456b35c1d20221e21041f0301: 57106e0c81dfe59d8d95c8af83e277cb37b7f7a93212e44b89aa820d4b0978e12: 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