delphi.consensus.snapshot
Appended 31 Aug 2026, 05:32 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 - 1171
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3d483c76-6358-495f-9f25-5cbef90fc78d- logged_
at 2026-08-31T05:32:18.884588+00:00- previous_
hash a0385c40661fd540f05df48386cc8d9a73e991fa82a0e89da39afc95bc2975d7- payload_
hash fe13f1dfd8e5be9987b90b3017ce2905caeea863e789f096c571b3dd6ede3a28- entry_
hash 431e01104856f3d1c211a486f20de36c54aaeac1eae5b9e0c455322cc8422cf7
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-31T05:32:18.882190Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3d483c76-6358-495f-9f25-5cbef90fc78d",
"series_commitment": "b07e175482a5034e6b2c787c9a18cf74f0e257e848ab4eb3df9b29b64b186fde",
"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
fba299266aa926b863ae8b6a8467b85ebe2a3cd4fe41de0f1b7aa03a4175ace7- 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 - 1171
- tree_
size - 2285
- leaf_
hash 538f04b564d7164baefb105b8a240207f77a6eed6944dd6db399dfb31cebb605- audit_
path (12) 0: 801b2c5f62e179e50ee55064d351ad9c589e641785b4d5437128a397416ce01e1: b400b71fa442e20f82aeb09c2cd6f1b28bdc12f8a9ef90b0d0a6d033872db1f72: dac12f99484dabd51573f86ceafe30f8f34d19263a8de3cbf4f16fa8a6d6adaf3: c24b8ebe729efb0844caf33ea93bce0da177a1922130e5e68980e96d67edc3fe4: 05e1ee3fdb63fd0cbe9859ca8f3232f6bd4133b7f87556de328354b396ec52e35: aaf78ed005cc51b57fcd96f4935a1f3c7fdd88f0303aa876df637cf03ce662466: 6af623eac90aa3987584d839f2701ff98677b56e888f60118d80a93d701c74b57: ccb0e9f17cd47f20723bd8ade751778a3fd4e9649264dffce135260eaca872fa8: 6ce18fb0b650e54a2c9454c3e9abde48f8386826f5bd1752662ede2993ff557e9: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: a95d574e00e9fefbc454b084e8cb19edc83831071366b2d8dc1af2f7114b646f- root_
hash 17330c6327e6363b8237bd4a68d5ee420a6d0f745c8d8bab0a90305d6bccba50
The earliest published head that covers this entry
- tree_
size - 1193
- signed at
- 31 Aug 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 15e3eb7357c2f6396dd33e1f606888695ff95a2f9b08f8019ac153af57c87266- signature
oYDFeMwvTGSzL/7VBsEVI+Y0GdW8Zywth+2mJP8ClwrkwRB8E6GNcFw3Uymh+sQFClvxu4FaueeuBpxLmZwNBg==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12