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 - 1185
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 4bfc7aa0-f12f-479c-ba06-d8e4cebfe625- logged_
at 2026-08-31T05:32:18.977117+00:00- previous_
hash d8b581fe00ec1a2d4f95b03f0a927099106ee221e67ac4a8c2b20663932bd402- payload_
hash a50caed57c8257d882ce19bb11f1789ba33e7a167dc8f22cf2dee54ebc63497a- entry_
hash 0eb09208df68713a5e0e7f3edc526d1d20cdf37242b70400a9c9f5a9a93c5d20
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.974622Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "4bfc7aa0-f12f-479c-ba06-d8e4cebfe625",
"series_commitment": "8159e33c2f6b07b22c0478492c1597cd554ea9ceacc482abae420c462b8a7ee4",
"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
5089b9544485b687b53407e92a7753ca318b39c3e67b50eb045665cbecbf73f9- 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 - 1185
- tree_
size - 2515
- leaf_
hash 9c49feab6d78e8dd633be08d0de5064902c32e1020ba4dd783af67453f40ae10- audit_
path (12) 0: b437f28cfc3bf5e87358f8f0177cc5aae09ad0c5cbeeaeba46c6d8b0f7c03d8d1: 8c43c6631007558ed719065d64d316a4dbdaa24dbde678905427a2a2deafbc992: ae9b101df3ca2af3fb8497bae5899cc82aefb26c597e60c37e1e45ee479a9e503: 196c3aeccf25de8c0b2caf67aee58b24fd8b25f56b8d08d65d2cce0893a0c1904: ff2eba9055d063f1eabd41bb3cc64d9a12fd4fe9865d9328c5dfe09eb11429b45: ebc9cfa74b1bc3e652fec47fce860a35b43577ddf0a7dd243ead4ace7f4529856: 6af623eac90aa3987584d839f2701ff98677b56e888f60118d80a93d701c74b57: ccb0e9f17cd47f20723bd8ade751778a3fd4e9649264dffce135260eaca872fa8: 6ce18fb0b650e54a2c9454c3e9abde48f8386826f5bd1752662ede2993ff557e9: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 07e77d0b86e68e9f9b9a10013a0034c87fc2ef91312163906ab27730e4a116c8- root_
hash 94ed3e67e0f3ca6ab90e872a7f03020d191548311e8610028e47ddc18fbfbf90
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