delphi.consensus.snapshot
Appended 23 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 - 2070
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id cd22f6a9-1eb7-4927-a2e9-6736a77b75cc- logged_
at 2026-09-23T05:31:21.986369+00:00- previous_
hash 704b1fd166b494399a78fdb5ea2288e7ffdb972072aabf317f19e9e18286728c- payload_
hash 7b5348a7ee4f27b092190047133a936544f4f75d2906c57fb709fbd193ebb34d- entry_
hash 0db8f616d9af9ff3ef6c8309a347f4cd9b336476e342483981f882a4b7e63ada
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-23T05:31:21.976284Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "cd22f6a9-1eb7-4927-a2e9-6736a77b75cc",
"series_commitment": "9f1f34e81f4349f15d9e3d52dc36c3839aa3499b7dc9b8940c91bc7d09f95591",
"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
0702358e398fe24477623d8dcedadb0eab7e2e7f67c2e67fad9bcf158d4934c6- 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 - 2070
- tree_
size - 2285
- leaf_
hash 9bac54a9dd7d3ec0d8cff15cd1ea373a5cd63f82ab2cb8ad562a008f18045baa- audit_
path (9) 0: 35ae597f55fce9c9a9262d18342f62429a06a1e651b8102bdfdeac6a70874d671: fb1b7d60f0a5c25e12baccf38bac25eae3825444acf6855189e600113663247a2: d32a87b7968883fa9c7fa42881917d7e3914388c6a671574cc6feec9155ae6e63: 44e1a1fb424e8a9f11882d388d4f79dd7eb4569de094906e7796a8304b6cb2134: bf44c0f23985ec73ba70f8bc29b0f6ad4f1e936885cc5a45e5476c3db4d6f6c85: 02d0dde49bb94e626ee08c2578f2d51d2b820b89a132a330ac2c7e0011eed04b6: 97e580b0f254128201e36dc81f73bca17443fd5e21d28fd611b3832d3123cce37: efcc4e356fa145279b69819abc96c5259a53132a5795adfcb75b75a472cb37b58: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 17330c6327e6363b8237bd4a68d5ee420a6d0f745c8d8bab0a90305d6bccba50
The earliest published head that covers this entry
- tree_
size - 2083
- signed at
- 23 Sept 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash d6c88688a6cd2ce0afacd2220cfe05c6666fc242ec7f9ac09129b8d0bc00fb0f- signature
bLHEfkVSe/EJZc/PD8usy+UPLY2Y2/f+Mxks+W/Ea8Ln6XdDXICDe9lU9Oos68dZVS29/4k0IitE7SmvpTB5AA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 9