delphi.consensus.snapshot
Appended 17 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 - 288
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3707c33d-0301-4c72-8c13-ee685e8a0a88- logged_
at 2026-08-17T05:32:22.721142+00:00- previous_
hash 2d9eecc04c1d9570f961bdff955f436d43e958d998d272570da9d974c147fd0b- payload_
hash 38848ecc66d6b898d424cef0f93691a021569654704bc8f02ba87a0746b5c61f- entry_
hash dd6332a199a57915e930ad0ea8a3e077f9367d34027ed96332f21ee9a3d9ffd0
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-17T05:32:22.716031Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3707c33d-0301-4c72-8c13-ee685e8a0a88",
"series_commitment": "eaf02a0361f094ce95ff9477006298348a659e380156e07fde28af39a790ad7d",
"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
d77ec550f995349bb1c261bbc189b276796becf1d4e4413d3a6c0c9b526de0e8- 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 - 288
- tree_
size - 2341
- leaf_
hash 7636935520c19490a2b0a2dcd71384487e50a745f2f2bef9cba83e1477d52296- audit_
path (12) 0: 99530734c88fa513d9f7a3d6595bbb3c3b316a6518ca4d00dfbc6d2542bcc5691: 85ccb0c4529f518c438ddcd9e1c605a0330211ed1de670fd0e351153efea96922: be5901401bcc725e17c41100a50696fb528805c0268ad2a5ce5cca67588e50f13: ca2a804ff9b09129977f1ab7cb53c96f5d05294b26a314b0beb78a43677a19ce4: 19a3889f100c5eab2697382ed100cf758f0b6296422368f382c326833dd3b4975: 6931fb0c142b59f19d81382dd8524b01ba9099a77bc8e26b2ed6ccdbefd738616: 9640f2238aad678a6c39ef2afc9894d61a7aa5d18f0e3d98352873acf175f1757: b6b1a03b6c4cb71ca9f74b67d202bb3853e053dac5fde4936e3466bfa6ad09fd8: 895db6b8306be0a0cab88cc38987289ed45422a6223f6a873d831c26678719179: 2fb679aab258481705c982e553094522ea7bb93361711a8387ebf359e8c3e43110: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: bd18df2de60e205be411a53ea96887ec76f5a16c15250bf48e3f90dc788abbaf- root_
hash 9f32e37b52a81f4fc0f11a1b956464ef6acde09c58b0ce26dc44277199cb7df0
The earliest published head that covers this entry
- tree_
size - 374
- signed at
- 19 Aug 2026, 20:25 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash ecf4adc708ae542a0339e03fd4cc181cf49d0329768627c5345c915a58bd813a- signature
3yL+JZfMhiQ6rm5rCTTg7iT+or04nCGVcQ08ILMw/d7eqvR4Jid7cEg2rQU5fCX7llStjVkTC9jVZjfGQvtMAg==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12