delphi.consensus.snapshot
Appended 30 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 - 1113
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 05901165-61de-4a02-b759-02a9bf89ef70- logged_
at 2026-08-30T05:30:41.091354+00:00- previous_
hash 424be6d9f30a9c0074da4dff15103ded5b9ec65d51491a400cdfc0ca71c96e7c- payload_
hash 0db48616d111460c392ff36a282c33ac71ca9359f6d4666ca8565caec74828e9- entry_
hash 137fcb96a088e36e3e372ebddcd3704d0fa77bbee9221d17dc7c801db84db276
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-30T05:30:41.086495Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "05901165-61de-4a02-b759-02a9bf89ef70",
"series_commitment": "9b091c3c1a29f1305d59479b41ce84f6cce26f2c876619fa6e9a50ba9cb17fee",
"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
eed918a39f3d62523b7090220346b426f7d56401144648749730746969d1efe2- 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 - 1113
- tree_
size - 2341
- leaf_
hash da65221dc917bce5ec28b2c079bc4bd8b4d7cc96c300587ce1cf3fa7de056b42- audit_
path (12) 0: 189d71b21ea029689b82231b80dc9eab756133b3218da5647b55fedaa5fa8c7e1: 3961c3f423cbbdb93a74327663cf57afd50d77d0821851d40dbf34ff76619c532: 799c3a6aa595c47272afee3666801253dd9a664400e5d61191fe71fabdacaf413: b869cc8d3f31b12410ee823ecd52d0049f7a284c3697e5e89443df5aa9f62c2c4: 082abd3851e6828c8ff227c8cb876ad3b2f35792788c1ec7782d22c728720ade5: 8947d8a1e70be2b634115b93456cd4640838c379021b8f3207e435521e78989e6: 3330710dd5fef91aa0e763e3b3c0b21b7b27e549cf2bfbc05fee8e8bfb1f42b77: bbfee2f96690132143d2a2a16089df72535201b31174873b1f1a4d4c85a029a98: 6ce18fb0b650e54a2c9454c3e9abde48f8386826f5bd1752662ede2993ff557e9: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: bd18df2de60e205be411a53ea96887ec76f5a16c15250bf48e3f90dc788abbaf- root_
hash 9f32e37b52a81f4fc0f11a1b956464ef6acde09c58b0ce26dc44277199cb7df0
The earliest published head that covers this entry
- tree_
size - 1133
- signed at
- 30 Aug 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash f93488269a5aeaf9d50291920769e871ba9d361f0fb72089c9ba41c88a2727b6- signature
nnzoG8Yk362jKSvRmRO456zSfVqvhFq0AoyJZsV0jjpigKArT+n7iaJbA8sAIeqGXEUgCqPLF9MrRlQug43xAA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12