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 - 1880
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id cd22f6a9-1eb7-4927-a2e9-6736a77b75cc- logged_
at 2026-09-16T05:32:03.447599+00:00- previous_
hash 671b885182f765d608726712955c5b199b36dcf15014a8c1a537c2b242784daf- payload_
hash f022ba1849ad89cad47718c3b0e0d576ca0fe2acfecf14fdb084f4b00c62b413- entry_
hash 987e8b5067f8cd0df94b926ad3a3ebbceec5637e05a329a0351cc494cbf9556d
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.440125Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "cd22f6a9-1eb7-4927-a2e9-6736a77b75cc",
"series_commitment": "920db8082b702e7da8c2ae763bd1134916f2afa76ead1d956f82bbb438fddcc9",
"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
4b4ac9db274bdfdd0c93d3c7ece847b02347ad0073217a83f27a446d68cc9185- 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 - 1880
- tree_
size - 2285
- leaf_
hash 4b4977bfd0b86bc74988b490496e8794580ebcc347cb4ebebf9f5fd261ba7527- audit_
path (12) 0: 43ec2345c13ecb8ceb2e435b578d9de4960e0e1b057497c00fb5c9f86e5da40c1: 7aaad9a07019d43a30605a090b96970a2694340f18d4e217959db0870fc4c1fa2: 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