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 - 341
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 6eba5275-6e6a-4119-81bb-48c75288862c- logged_
at 2026-08-19T20:25:53.544148+00:00- previous_
hash c9606373cfea30bbb2308b81a8cd720cfaa85bd9fa1ae7a838fe06641b1b3851- payload_
hash c85720803e9f383e60c72e963bd968801e137c720356a9edf385ff0143d2cca7- entry_
hash 23976452cb680922a449e1c2fea51f4b6a76d886d1a0d2e2de22cdf2ed19bcde
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.541661Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "6eba5275-6e6a-4119-81bb-48c75288862c",
"series_commitment": "d63c53447f174ee878c2cda18e10d86f5ecd62b58f0b6a23e3929b5f2984ec94",
"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
edc57ccdadefef91ee33032d43fb2c6958ed9f1811a1ce6a0955ab18ab36e0ce- 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 - 341
- tree_
size - 2341
- leaf_
hash fce466c4ae2f3c169c48b47afa0d9c350666ddf2497e28395aeed831be537812- audit_
path (12) 0: 7551922399924fd3b617fdbec1733a1db2ef62ffb6804217a49a92d469f4a1281: f9b6d8b33aad6d108550a00e8969c77a1358c012b1fcc3770273346b1bdcc8f72: 0ac925972f717b9cf05ea0451e5e5d1b8b6f6b01ea5487a2875acfce3b9aaf5e3: 8fb3842661ad1d619fd073e66adaa8a02664e448e6724e3f4d0caf978256ede74: c0cd4812074f5f388511a2d0756f0a78a9124ef683e80f56885caa56bd9863a45: bda7215e9b8112e350fb03b23e4ae251a3c477789703c621f65deb841e56eb1f6: 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