delphi.consensus.snapshot
Appended 17 Aug 2026, 05:32 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 - 269
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id d8d7d8bd-61ec-4918-b395-799de97e359f- logged_
at 2026-08-17T05:32:22.506712+00:00- previous_
hash 0d86ddc79e6b07827b43519828e5b218023f0f75f9e56048971cd5a05fe5b34f- payload_
hash eb11e4d661fd55730ee9e807e98142fb363759e2cacbedf65f22a0031ed3d3f9- entry_
hash cc6ddb6dcf69ade69359b0b06234ef1fba060503f17fd520f26a120336085be7
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-17T05:32:22.501365Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "d8d7d8bd-61ec-4918-b395-799de97e359f",
"series_commitment": "5db1b2d1837deeef2ef7bc11202a6d9f621afc2b2497f54accfd006912f812d9",
"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
3457131af477597d077c7fdade5dbd7d7efd0c1738c35a0c7022a5f6da9712a7- 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 - 269
- tree_
size - 2341
- leaf_
hash 58c75b41a2bd8b8ff3849b353e2b7ec6af8891062f3b67c611d5f03d63fd10cd- audit_
path (12) 0: 54bf460e7cbcde66c0bacd357ab8b9d75b0a4746bc901752b43e0f4c33e2cfd91: 7a81e01f4cf0b06ed9670829025286721d72acd2b200688c614face07df35dd32: 1c5e6dea3254b72ac3e42a44ba51cbccad1f00d0ae892812ec5731f6bf9b1f4b3: fa710e9b98f8842811cec9e46f7bbe191c53aebc42dc7e9519a9cb17bc56386c4: b72aa60f23412fb51abcda53b6fcf69f02631da2699b85803cd382de35469fd75: a42809d126c568e62025f792d0dceaf9cd24a755d024064f710db9f30bff07b06: 9640f2238aad678a6c39ef2afc9894d61a7aa5d18f0e3d98352873acf175f1757: 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