delphi.consensus.snapshot
Appended 4 Sept 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 - 1387
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 29f1e88a-b6de-480c-bc2f-f234c647455d- logged_
at 2026-09-04T05:30:40.499656+00:00- previous_
hash d148a0ddf40e0ade7894d8aa57dee7578e40612c152d03da2607f454a465459d- payload_
hash e8a8030b35c009368844e4d25ff4ca617b2cd9ae8d0be791f375a1ecc78f8e7b- entry_
hash 80be4e0f37eea7878f92a50cb2e6f978c9f1e65df8760ca4c82e193300614550
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-04T05:30:40.497664Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "29f1e88a-b6de-480c-bc2f-f234c647455d",
"series_commitment": "dfb42b60f7e68eb4f672cd88ed27607940d69919b0b021dc6fdaeb72397f700e",
"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
8cdebb45debf8199490f209c89d6a6794117e11be850a48ced7209ee018603ae- 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 - 1387
- tree_
size - 2341
- leaf_
hash 180ef1e82e42d9e2121a22a6738a6c05d628935bf952af66d559804910a8e633- audit_
path (12) 0: 2f9bdf4cc73df3e1d84c2d8f6de01d981c492ad8e87251148678800598887d691: 30b5fd82a53610d877ecaaaecbb41fd4e16f4584387a563c19f3736fbbdbfb7f2: bd0273d7e91e228169bb2022efb0d3876af31108c8e76dfcc1fed36fb322a2413: a692dc39911baaa8fffb28b5e7512ae464d5c9a3b20b1f7479ad65f057c9f67b4: 13f28f3407a29ccc4c44d00c691dfee5d2a85ff0d643ac7fa01890f2db8136605: 3d3a958791e28b79f550cca07dae62a1e556e0e03bb681620fd44cb3c0b449456: 3347dae74325660c6b1e768277c0a7f2169b7554b58c0815e1d6311ce75bfca77: 00aa16d00eabe2b61089fea4a6c3044cf3b1ced9f2af168276f93e239a98dae48: 73b80563a47162cfa99809097caf5d77512af3a28ebfbf76c6bcfd5f572cc1d29: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: bd18df2de60e205be411a53ea96887ec76f5a16c15250bf48e3f90dc788abbaf- root_
hash 9f32e37b52a81f4fc0f11a1b956464ef6acde09c58b0ce26dc44277199cb7df0
The earliest published head that covers this entry
- tree_
size - 1397
- signed at
- 4 Sept 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash dcdf356cdf9dc7ebf6b15487b75fbf56f1dd13b64c18428b5b1c3def4a10dd7a- signature
3byga8XRhlKNr2NA4ABo68hmWG9n+zteILiR72i24nQlgkl2AHzxfRM3GAGCw7aUDx0eN916Oq0zGWs0D7mPDA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12