delphi.consensus.snapshot
Appended 29 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 - 2230
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3b91df80-00fc-4a4b-b86e-3310edcb9332- logged_
at 2026-09-29T05:31:20.822791+00:00- previous_
hash 4af7eddc8c1b0d4e173f476db66420dd94aacea6a32628ceaa27f8e0624925b8- payload_
hash 4421c81fed54f934a276992ed2d3ef93253d3d2dc311e2d087d3a155fabbeabf- entry_
hash b7b6298731f27f410ce8abb402396808fd59e6f3c4e1ebdfee40cb3a0492b440
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-29T05:31:20.819358Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3b91df80-00fc-4a4b-b86e-3310edcb9332",
"series_commitment": "d57652d8d5f62281d90e35e3011ee4e03e8e12d02a517c705996fe8e7663b22b",
"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
3c7b1b427ff59c0d9ef9960f538929b9aa18c35392463fada55e1119a07cd5e2- 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 - 2230
- tree_
size - 2389
- leaf_
hash e5025c8516080e40f4afcb6186acb3c82be0ea1e04d34526578b911f4b875182- audit_
path (10) 0: b9bb53b0ac6977c3404388d8eb6f93b02e1524332574eb9d79097836e4e857791: e10f4c2f5ec334ec8d5742fe2e9509c908cd6e505891efb638d325cadbfa30c22: fdd5bd9205a2a4540976078b110f171fe552b84c4a6c8742c90db46426c88d9d3: 8ecfa0211918b2e9d96b6da731a3372dc96703f1648e49caae3b3b8476b6eac34: d2c68d760af74d87740ca89ff1ff67d32bd189e548ad56ef83ea1334e37149175: ff576d5d5ebff608e9a429939d33e803b4f824aa935c65d508ae2b3f2eec66696: f30320e32b01d85ee25d3699765f61034c40add7177cc53ee3e39fdfed97b4367: 126596474757e47b31a2f4c9d89412108fada5bcdc7a19a9a1de3d4012be0b578: 03c349147789bfb063beb6c472906eef54792e9077566daa1ada925b4ce9b91b9: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 4f7f1a3085d540e3b69ac022c801823029c04ad350f74966858670c2038ea3cd
The earliest published head that covers this entry
- tree_
size - 2239
- signed at
- 29 Sept 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 03dd6fb33b4bd65222257eec0069956926795f14f7354795bcb42af5fe51ba08- signature
u8ChL0jIyB0SQwYB26vHeURVL3Ia2DcWQObp46M30jJWJb4SKWQ36EVhUNp29FUDMGkSZ7aAlkHhiTbNS6OGAA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10