delphi.consensus.snapshot
Appended 17 Sept 2026, 05:31 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 - 1907
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 04bc3a9c-76fe-4aad-90b1-e3640e548e9c- logged_
at 2026-09-17T05:31:41.608033+00:00- previous_
hash 76d6c51384461b7de7637a9574b7212232cecc4dff388807b1767bace3fb0065- payload_
hash a8de548551adaa0b4a42c8dc3d09635d30b771c5524be8ef62028b7ab8c515af- entry_
hash ba65c8978e3a6fadca2a7071b14187780e86cbe7f4f91b3e4d5e6761c7787428
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-17T05:31:41.601150Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "04bc3a9c-76fe-4aad-90b1-e3640e548e9c",
"series_commitment": "c9e68c389f9d7c4ffdc5f5937e05693c27f5c63fff1018f01ddfef8453be1e69",
"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
f12be81f6ef63620b87aabf9c4c732f204ff16e4945e37efa4e34c8e519cf060- 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 - 1907
- tree_
size - 2285
- leaf_
hash 9e9493ac2728e745148931dc6bdefeb53ba0134303e73b8af8ce980ffabc5173- audit_
path (12) 0: c6dc12ba66b8cf2fa97093221953e8fc545216bda1b05875ba743e29f350c5201: be01d3db02ce6b44bc954067fde77d2686fdb2f041dfb6f5d0c883d493ec71742: b6301236da8f054cacf6d27877c3063005a0bac2f8d24ad5b88b69451272e17e3: fff713e27c9f73fdaeb0f1cc0f6921ea4e557b582b9b03fe258a9379082f93ee4: cc6b75f197277762b6837a9f28956ddb80000209e849f7395b445025b8a73d975: 8163d9522cee5c395b431cb6244dc9be07640c46717beda36e36f07660c958786: e58805ff3adab5c7bd3bd83274fc881f7ac4f076b0dd834beda95d34af7800d77: 250a7c52b8fa3c4932ca872a3a7842e2fb00579ab86c9b5fb8782329fdedf9fc8: 5ab1df6751f0dac25a6ce29d97587d6e08dcdd2d94987223ead725483527e08e9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: a95d574e00e9fefbc454b084e8cb19edc83831071366b2d8dc1af2f7114b646f- root_
hash 17330c6327e6363b8237bd4a68d5ee420a6d0f745c8d8bab0a90305d6bccba50
The earliest published head that covers this entry
- tree_
size - 1921
- signed at
- 17 Sept 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash de4645b3ae57c2a319bdaadccc8424330c3686a79d031b007b80eca0ed78c863- signature
XoarI5Mzcez/Mayoy5WfSvWoXgXCDcdhQdMw2EQ2bH4TFS2FfvvlUkHv+csOCREKJBJN95gFWB6udc2z582ZCw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12