delphi.consensus.snapshot
Appended 2 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 - 1288
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id cd22f6a9-1eb7-4927-a2e9-6736a77b75cc- logged_
at 2026-09-02T05:32:20.849877+00:00- previous_
hash bc61f9e4a49eb23b24f9ddcc1e846a99bdb4bd11feeb931c2614fb7ceacb1897- payload_
hash e2c5b742ee92a2bda2af6d070b474cf446bd14bb587198ca6ac28892b69f6927- entry_
hash 039d3185a07b5d7c8935c7a5a078342f946ac6e44d24e56c1348105e0748e342
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-02T05:32:20.846396Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "cd22f6a9-1eb7-4927-a2e9-6736a77b75cc",
"series_commitment": "068b24ad443035e65fa867b7f1e9b23fa38fe57ce4bf296b18b7c66317dcca8e",
"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
07b6c5991ee3004a9198f088ff177a15918081ab3f06a41afacbfcb3ddb4efc6- 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 - 1288
- tree_
size - 2285
- leaf_
hash 9d62b34f05848a4e666147f60e2e1085aed2c41b8aaeba71926bdad9425be447- audit_
path (12) 0: d78d9df94de0827ec18334c8d9b013eb765d947e088ec1e1525755793fa89f171: d17252fe3338728ce42923ab21ea289844088bcdb19af80293bc9452a86197772: c25d0d885e226a87abec335e5e813f3ef7d710b02fcd748042bbea1dc148b4a43: 595b2fc835f327f57ed8373d99169f59746d5a4224184477d33f3e0921e83d2a4: 3bab3dfacdb4663eededa2dd912fa671e084bbce8b9478f98ff785f76bc67f205: 338aa13e9ab3bf9fc959251d8ac5778963ee124660725c2266d53394765b5c306: 1856e988c0ca2de1232e3499545b496b7d991e639165b9289a3c3dc3f273d8d47: 00aa16d00eabe2b61089fea4a6c3044cf3b1ced9f2af168276f93e239a98dae48: 73b80563a47162cfa99809097caf5d77512af3a28ebfbf76c6bcfd5f572cc1d29: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: a95d574e00e9fefbc454b084e8cb19edc83831071366b2d8dc1af2f7114b646f- root_
hash 17330c6327e6363b8237bd4a68d5ee420a6d0f745c8d8bab0a90305d6bccba50
The earliest published head that covers this entry
- tree_
size - 1301
- signed at
- 2 Sept 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 7412c3bb0fe0de978d577bfb7d7e6c78c4415aac29193a116b150bd1dc28f398- signature
NpyT4m8rheEfWbFdEQNnccQG0Zzl3KXO1wHnZx7zD3lNnn81UHz/zavu3VUhzj72XmrSmaJLQKo1iyyww27pAw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12