delphi.consensus.snapshot
Appended 25 Aug 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 - 807
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3d483c76-6358-495f-9f25-5cbef90fc78d- logged_
at 2026-08-25T05:30:32.477977+00:00- previous_
hash 0bed580ad0e7ebe7a7f3a02baf96fe2169e3f15eaf192b156aa4bbab42034e41- payload_
hash cc1b8af277eb211a5a7aec6db008d3fa039ecba33a83687a0dbf6a409ebdf346- entry_
hash 932070494fc991df98ab752a0aefefc844679f0edf3274ab223d693e2bd75fe1
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-25T05:30:32.474981Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3d483c76-6358-495f-9f25-5cbef90fc78d",
"series_commitment": "e7682c6154dab0e66103ebe9b31259ba8036866ce17b3b2867b0dfc7213fea0f",
"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
3548b3681bf2e1810e2aea5141b918c92176795a9b1c17df67d03115f15f12a2- 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 - 807
- tree_
size - 2341
- leaf_
hash 34d52aa77fd7ff557a115141245ca8d83e2996bc7ee508b6cfe8fac640f1ed2d- audit_
path (12) 0: 96e835afdc9801b178d37456580ba5935ec0af972f36f72406ae53059d1cc5bc1: 427574cecefeca6964493cce15be23b600cfbc09de9684e151621d3eecad93582: 3a75ad03be329cf48352910490af11a07d7a2a15c4c2e25ebe26b6741e3351203: 84c50d556640e0bf10b54008faff28f1734e158bf3ffd43e408bb653e9680df04: e6504495f678413fa3a87a90cefb204f1530ef75a986eb88378995f192b6ccb15: 8b9f3a56401822e1e4af04086c31b37e1a9eecead0bcd104e08f30953092e6426: c715192dae6aca65ceed9c8b6f8df435b8f926e7881a91f9813cc86bda106cd87: bc6ace31149b3e9c1ba9d5f2b34ffb85a63422d9dcf2ebf241b2cac10329bca88: 184a24c3b623669a5fc418f1a01a448ab12c5b650e771370beaf16f761dd2e6c9: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: bd18df2de60e205be411a53ea96887ec76f5a16c15250bf48e3f90dc788abbaf- root_
hash 9f32e37b52a81f4fc0f11a1b956464ef6acde09c58b0ce26dc44277199cb7df0
The earliest published head that covers this entry
- tree_
size - 829
- signed at
- 25 Aug 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 54d12dac3124cabdb4202235d36c70565cfe886be49d70b227ac5a5505091895- signature
mdeQG8QhQ6dRyM1bYFxhqIK4IU3G7uoqpGdqrdWIkJxP5SKMG/wuhFxNgJXg0tqbSG6msFkc8y3L0Pyf/W6XDQ==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12