delphi.consensus.snapshot
Appended 19 Aug 2026, 20:25 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 - 361
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3b1bf8d0-fa87-4392-b4cf-333e6cba3622- logged_
at 2026-08-19T20:25:53.715373+00:00- previous_
hash e77008d49624574c4338355a9ff15577680316b6c1087c3a3a85b106ce41727e- payload_
hash b93b61abd0895016ce3ec7fc6a1fb504325de55b3b79db888129d0d5ceb18c8b- entry_
hash 98e5e751f7a74c65e318131fade75818c79306323f730c833d4e775d32d0ee62
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-19T20:25:53.712933Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3b1bf8d0-fa87-4392-b4cf-333e6cba3622",
"series_commitment": "84ba46da210d983d562da999d9d2cce176201a99497ae51b2d2500aa78a21825",
"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
f146fd6ced0785725fede9b5f865c0a2f799a34c267b7873b2b4c8881c50c3d3- 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 - 361
- tree_
size - 2341
- leaf_
hash 03172b31698dfa7d6159d7c5c62ed11994b6f6198c92fc65b63dc4f78fd67030- audit_
path (12) 0: 6748a1dcd1a34c58f21bcd5dab673ccfc2a35a998059734094624513f00c4fa41: 73b9061f52d61aad60594d5d43704840f23f80e425271e056089a4d0b054667d2: 2cd127b3db2f119c4a79815991911893f5483c72a834d79f181728b7a3d4e1573: ab0c3d0e50ed0ab8cfa40ec3ec8863963131a73a7138ccac1cc2e902ae3be17c4: 5017bed2539c89027a362051b3f615ec6a6b5c4d6636a5c0dc982357d57262d35: 2595355eed4d48ec0c80ac31f76e58b5020ff9a705ae14cb94e2e491fcaf2c3a6: 4e2b3509b8ca9f9d4bd60d1a8236d9ff586b63b2e0bf7572cd8261d81af879617: b6b1a03b6c4cb71ca9f74b67d202bb3853e053dac5fde4936e3466bfa6ad09fd8: 895db6b8306be0a0cab88cc38987289ed45422a6223f6a873d831c26678719179: 2fb679aab258481705c982e553094522ea7bb93361711a8387ebf359e8c3e43110: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: bd18df2de60e205be411a53ea96887ec76f5a16c15250bf48e3f90dc788abbaf- root_
hash 9f32e37b52a81f4fc0f11a1b956464ef6acde09c58b0ce26dc44277199cb7df0
The earliest published head that covers this entry
- tree_
size - 374
- signed at
- 19 Aug 2026, 20:25 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash ecf4adc708ae542a0339e03fd4cc181cf49d0329768627c5345c915a58bd813a- signature
3yL+JZfMhiQ6rm5rCTTg7iT+or04nCGVcQ08ILMw/d7eqvR4Jid7cEg2rQU5fCX7llStjVkTC9jVZjfGQvtMAg==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12