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 - 356
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id d1b83331-68f7-4be7-a625-f7824bccab5b- logged_
at 2026-08-19T20:25:53.684797+00:00- previous_
hash 06c7c5e3fcc4454670465e3f421340ddd9746c2a4d3dda955ff27f89292c7250- payload_
hash 6ac764d6ec98343f42f13d6f3d4788d3201d6995f4c7420b57ef75eb7c326689- entry_
hash 8244ecbae1bb6dbb3cfc0a0db01f95cb88cf83e88c0eccabae618e96dfe5502d
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.682393Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "d1b83331-68f7-4be7-a625-f7824bccab5b",
"series_commitment": "20e2caf8b84d935a06861fe364f5973793fcee3300f7292f7b0e0d94879b5982",
"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
a6c47ff857267bb94f740943ef95219656ed1539843215d00ef0b91030e8bff0- 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 - 356
- tree_
size - 2341
- leaf_
hash 66c1571727ab7db5d2cfb608f943e2096116db438f14726f75c3ffb1d2925488- audit_
path (12) 0: 7708a8463251db2b213ed9bd1e7957f5448b6d773373813a98735d247cfeb08a1: 8067f982de164c81163435f9a07476bb3b7e7eeb60244dba380cd75f7b2682822: 76e5890693b567f316c794d9f7ee04420052b0f012a9783279606f7db30096293: 577e146fd59a527ad4c814ae5a2c69f780bc933856790cc65b82bdd386f9a0b14: 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