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 - 1879
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 04bc3a9c-76fe-4aad-90b1-e3640e548e9c- logged_
at 2026-09-16T05:32:03.425822+00:00- previous_
hash 73bad39473fcad7685e1d027a2506597f761dd75652b86445adb49e8809816a7- payload_
hash c5f8885044644ae39a1814271691f538c1408bd3576c84bd1ae56751afef981f- entry_
hash 671b885182f765d608726712955c5b199b36dcf15014a8c1a537c2b242784daf
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.413031Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "04bc3a9c-76fe-4aad-90b1-e3640e548e9c",
"series_commitment": "cc0e1100cbf8fba82a193644b79d46fcf0a8090d529cbc78938af3eb17b03321",
"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
f68ae4457df507b9a20ec419c92ab9570baf192ee32d486ff689ca2d01066fc9- 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 - 1879
- tree_
size - 2285
- leaf_
hash 2040e011af77835be0df6e8e014e92ae004538aa612ed44ea85b1664fcca1e77- audit_
path (12) 0: aab7b00ea9866f1bd86be87314abbf523ffcd9a86625993dcbb0bf5f79d11b6a1: 687c336e3f3234357043fc4c15940474a2a4d0579f6b32dcfa9930224b214b792: 2ff1e0109e473c3bcc2bc702368429b56a015daa8176718132154d2486a65ee93: 415f6050d928b30314511ff15ac5355032f9894cde70629c64619cecda7edc5b4: 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