delphi.consensus.snapshot
Appended 16 Sept 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 - 1882
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id f69e4ff3-bcaa-42f5-a8f1-8044a9975b0f- logged_
at 2026-09-16T05:32:03.467911+00:00- previous_
hash 9490ef635f009ed36b313583442dfc1f60d2af76fcec602eab7b2c3201e2dd76- payload_
hash 52faaef9f3e92900deb219416c89ac5b3b77c3865915591421c183cdf41ff439- entry_
hash b07384b413495e7d2601b3fdb93a6fd536b90e84cb929303f28a04d99fd0cc61
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-16T05:32:03.462983Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "f69e4ff3-bcaa-42f5-a8f1-8044a9975b0f",
"series_commitment": "9077402a770ef7b9370cc8403f8afd5a7400cbb2509ed54e3f5bee78c9caf1c4",
"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
3b74ac36991f230b0ad5d5ed95dbd000efa9e89e78d11ab9a42ee998b58342c8- 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 - 1882
- tree_
size - 2285
- leaf_
hash c089c050e12ae761e2c1ba398e7c9b441db21d9fe01cfbdd016a54e8027309fd- audit_
path (12) 0: f6327e76c5ed070e7da1fadec1b1d00d81e7cbefa777ed2abdec04e46bea468f1: 70b06b7d491bb57777bccd8e4d6644dab9acb99d0c2ae58a34ceb1ceaa5207032: 946d6855c159b9d2fcd2d7c361f6f13a248738cfd88b3e928e509991e5b5415a3: 4c2db70f824b3c5e61332f3a5a550f0712c09a15e9e55d607b0955378e1d1ec24: 39f827cd96cb94a9f98d2fe79f258dadd64b7a357c8a9207a06aa935859d31eb5: 43eb768390db459ff2c2ed043a4367c5e85067784799ab09a2d0ea1fb483838c6: e58805ff3adab5c7bd3bd83274fc881f7ac4f076b0dd834beda95d34af7800d77: 250a7c52b8fa3c4932ca872a3a7842e2fb00579ab86c9b5fb8782329fdedf9fc8: 5ab1df6751f0dac25a6ce29d97587d6e08dcdd2d94987223ead725483527e08e9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: a95d574e00e9fefbc454b084e8cb19edc83831071366b2d8dc1af2f7114b646f- root_
hash 17330c6327e6363b8237bd4a68d5ee420a6d0f745c8d8bab0a90305d6bccba50
The earliest published head that covers this entry
- tree_
size - 1893
- signed at
- 16 Sept 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 2945d3fce4b045e69d9f4dcd9ec3245d9f33df6a4fad1e28da7f262978dd2df3- signature
wd6goG5LLThX3fPZ+aTodS8ZIhvpUh8GQnsa24awFJptoxP1GOtak9J2qUa7SXysOEjki45TElUl1ol36o+ZCA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12