delphi.consensus.snapshot
Appended 15 Aug 2026, 15:53 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 - 21
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 28453d7d-6676-414d-a36b-2fcf2cf13265- logged_
at 2026-08-15T15:53:35.821171+00:00- previous_
hash bcf0243eb3edd56523057d527e924b66ec4b4475fbb1859da47499b9e5aefd67- payload_
hash a64defd587cf6d2a12cb99c5927d21f73b19e47b6e64175de55635379bb7fc57- entry_
hash e227fc9279a7c4af43461d3d69860d0ca75abab22268d967866c4e2a04d25f66
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-15T15:53:35.817623Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "28453d7d-6676-414d-a36b-2fcf2cf13265",
"series_commitment": "e8a9ab506d147ac4a6dc0d9461a833dfc05731d7f23a4bafc37015b3f8644c2d",
"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
cfe6046a1c35407261624147712dfa3348aeaad1b13c4950783468bce9444c28- 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 - 21
- tree_
size - 2285
- leaf_
hash 0011d6cd00b47ffe57ad6f7209e4857f07a79e56a2c35ef63146d35ed880e490- audit_
path (12) 0: 085ffef0d20f3b42dc8c29dc574983e9828e3fb13c5fcb8163fc5c8b96af51801: 2f08fcac42823221564dd36e63a81a14a39ecb043fcb9addb4a658669178ee632: fff3ff54516ca778b8e41f50d52d7589f9d0bba05294a5394fc970f39a5e3fd13: e4b9ee89b03a1049049e4b184c49c6dae3ebfbec9a890141323ea71fdb33b0ed4: 7d6682fa6e600d077f7841e30621efe19877a3f61ce600d24a3eb3948d17dd255: b74c92a6356a40d4a8987db99772ead75d18bf349905054ba53bbc3401d9b2b96: 432b3bec17cc8d9bd118f5d2d11fc56d0578ec1940af60be2192f2f1b8d43dc67: 925d039cfaa2795efce751d71988395a9d8544d4910a71d82c761e6c8e51ba2e8: 6e5b02022079dc614c5f74ca1c784cf9700d832e05c2eec11f0ad0a37376b46d9: 2fb679aab258481705c982e553094522ea7bb93361711a8387ebf359e8c3e43110: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: a95d574e00e9fefbc454b084e8cb19edc83831071366b2d8dc1af2f7114b646f- root_
hash 17330c6327e6363b8237bd4a68d5ee420a6d0f745c8d8bab0a90305d6bccba50
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