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 - 2227
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3b1bf8d0-fa87-4392-b4cf-333e6cba3622- logged_
at 2026-09-29T05:31:20.792168+00:00- previous_
hash 0e5988e08daf4090038f117db915d5690ae9e2fac2459d69fa6f69e231a2b023- payload_
hash 576430cef8cb9ffae5b6ba3cfd1b75c80944ce1be6fabeae5d1a6a341edec086- entry_
hash 439afbc06f103fe94baa4f056b0e07c0a908a3d6ec4593f874fdcba47ac549ea
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.788251Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3b1bf8d0-fa87-4392-b4cf-333e6cba3622",
"series_commitment": "77124da8cf8e86b71605495a50ef93d550543054b466b930b8d165e5f2fd39e6",
"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
e348a7f50e87818ac9121bb4b6ec3b0c21624c626d7a8afb43fc64c3561fb2dc- 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 - 2227
- tree_
size - 2389
- leaf_
hash 46499966d9521bf299276e9e50028d17c70beae22ac9232a7be872585de4e751- audit_
path (10) 0: 67ce02eda23b88e98c1ba2652cf00896c63a8116c055bda3c37d47f4e53dc13b1: c24c6b97e1110c73cbb20bdf0e1bffc16563b6478faa17cebc8ec368fc49aaf42: cf5fd565c9492bf39c2afcc7a5c99b2cbb05d05c09e1dbb9b55183deafe4ee0f3: 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