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 - 354
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 05901165-61de-4a02-b759-02a9bf89ef70- logged_
at 2026-08-19T20:25:53.672615+00:00- previous_
hash cdbf77f9bef8976b9f01f3f007551a13b42d765b39755725313a057c6e6fb7b9- payload_
hash 28ec1ff49b2c473ea502ea27e872ef3ea632a797de6d8d60e56547b90ff3c84d- entry_
hash 56ae6550cae741f049a77ce476f3bd3a850eaa868ee439143dd6167e194d9a54
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.669273Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "05901165-61de-4a02-b759-02a9bf89ef70",
"series_commitment": "97f4c243a3aaf263a062a4f40bad9ad9e17621514879b95affba54ac1fd0f96f",
"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
6aae645c9ed893efacbc55073ff46bf734ca9d1b3290d80395568341f7b0e143- 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 - 354
- tree_
size - 2341
- leaf_
hash a168ccb294aecb019e51cf615b8d72c9b961ed6a87750a158cca71d17d795c02- audit_
path (12) 0: 383047ef9f5bd418c99c7f7a26ba1fe0cc839613f8ad42c8ac72b802f9cc496e1: e4b14d7215ca7711d41755073545b22032b622e5087fe6a20502374b4493cdb92: deb30d1afa2d19bd7baca46d872e76cbb21c17f75d10315447d5554178b14a1b3: 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