delphi.consensus.snapshot
Appended 17 Aug 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 - 274
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id be56b97e-fbba-4073-8b29-04e6afa28138- logged_
at 2026-08-17T05:32:22.549954+00:00- previous_
hash b7026fe3d18b465305c4810bc09ca6afbb6f7b578db6fe9175fce2a9ce4eaebd- payload_
hash 1711d613cf87697de23040a57aa13fb127904da30bb59f657be0738dec6925fd- entry_
hash fd1ba15d57fdcaa20a6fcc57c21ab0982588e37c6ab86177b4ce2f8db5a6ad1c
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-17T05:32:22.546936Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "be56b97e-fbba-4073-8b29-04e6afa28138",
"series_commitment": "1b93d1d137999e4214ae993237f0b0474b09db684b9539b3653bb230d18c9de8",
"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
db01ff07e1a0d248731260d18525d82214a9d7cf6555e7243d111ba8774c5cdc- 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 - 274
- tree_
size - 2341
- leaf_
hash 9a1df751411d6938ebc1631a3b9ce7feac5d2be6d756157b215fc759e7e78189- audit_
path (12) 0: 1ef50c5c6a43a1bf447ae38977c33761a05b6e13338c80f99db29550bd8610fb1: 9736892d9aeec339159982841d3de253a8a7290add3b99736d67d1558b64a0bf2: 892b4ec85270287992d13c16372637f939e6a59872bf3626e81bacfd79e898853: 732d67f9ef932d06ac595d8f73c605d40e2392c8a05d3a55f1222184590026f24: f25a811785c25e7d742c40730060345403f02a4e8cba08e0b564ee4f98018e505: a42809d126c568e62025f792d0dceaf9cd24a755d024064f710db9f30bff07b06: 9640f2238aad678a6c39ef2afc9894d61a7aa5d18f0e3d98352873acf175f1757: 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