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 - 1173
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 05901165-61de-4a02-b759-02a9bf89ef70- logged_
at 2026-08-31T05:32:18.897211+00:00- previous_
hash 940dc23dd725d524aecf52150f2c4da3e52d5a5e7626b32afbde551831cb5b54- payload_
hash 9e0a9a01903b213e26d7b0edc46abff921b2ea2d4295e468e547e4e564f00ecc- entry_
hash 73068f7d1a66932f2ec978af2a0a0de6b34439e023129f03f664f43227897603
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.894866Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "05901165-61de-4a02-b759-02a9bf89ef70",
"series_commitment": "96b0d3a7a5a561231b4478e8949daa8eea133bd1b37f5dafd648a65726152d4b",
"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
bac91258efa70bfcde62e712c809b497ce1e140d187e9132ce456fcb040b1d2c- 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 - 1173
- tree_
size - 2265
- leaf_
hash b82e4e3aff77b69308b212cc80eb81172d2d69383bfe3c533de8f9c97b6d6876- audit_
path (12) 0: 3a17ce941ccb64f9ed70d37e0fdc6f79f75dcc198e1f59d8f06b6052071f70141: 301dcf2300ccc0ba40fd2c708b1969d5ef42e67c1df792c92426ef637925a9172: c1f026b09f5bb96cc72b8382e09106adfe3add220ad0c8e86698248a85da64b33: c24b8ebe729efb0844caf33ea93bce0da177a1922130e5e68980e96d67edc3fe4: 05e1ee3fdb63fd0cbe9859ca8f3232f6bd4133b7f87556de328354b396ec52e35: aaf78ed005cc51b57fcd96f4935a1f3c7fdd88f0303aa876df637cf03ce662466: 6af623eac90aa3987584d839f2701ff98677b56e888f60118d80a93d701c74b57: ccb0e9f17cd47f20723bd8ade751778a3fd4e9649264dffce135260eaca872fa8: 6ce18fb0b650e54a2c9454c3e9abde48f8386826f5bd1752662ede2993ff557e9: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 15428b80842f9a0801cf7667918b216c9ce4186d9825e806ba86972b039c03f9- root_
hash 0feab2262fa1e39174e25fc17ea9383a6fe15fa5d22c96afd722849e59baa3f5
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