delphi.consensus.snapshot
Appended 15 Aug 2026, 15:53 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 - 49
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 0485b0c1-a674-414e-9778-a898c974bd9d- logged_
at 2026-08-15T15:53:37.136135+00:00- previous_
hash 52cd1c8a9cb09ff218501a3fd4e5369d4f061218fc3089d9f4ec1028f225cbe0- payload_
hash 8c0cd33e8331fc96cf1adcfb32c154e5d0ea5ce0b23a0387e362a4fa8f275fb8- entry_
hash a6db08f4f2d4a8696faf5581922aee1c6217d9ed1966fade5d4ca3eccd8601cf
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-15T15:53:37.132184Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "0485b0c1-a674-414e-9778-a898c974bd9d",
"series_commitment": "9870a7c8ba617329240c5442296013f0bd1e2e93d45d664423b2a476adf43b4e",
"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
635713ba90a9e70442b5553ac56c1bc4f422ed5c1ef28d96c2652428570e0f07- 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 - 49
- tree_
size - 2265
- leaf_
hash 7fea16177ef493ab3ccd0b14d8533b98bfcea7d34f37c542dc82d2040132dc25- audit_
path (12) 0: b2877129ae69cc147865cdeccdd51cc80076f85e7e89b814c8410c245298c18e1: d68db828e59419a762bf836df25d0387f1cf937c9e958fb685938a519bc346db2: 575d95304450173ca4c6ce66d688d95c5abb0e6b923bcbf1c78a25de9ec4c02a3: 59b626cca7986be0b6ec44fe0d4d89e3fdbd22110dbe11bf0c1a9d22fcaf178b4: 2470c45a41e5b2338cd0a79e1b28f402a0e7e23251bee7ed256b2f8f028ccbe75: 0dec549ee6527dafc0e801068f2df8c4eef8fcb9972397c6eb58217673bbfe9c6: 432b3bec17cc8d9bd118f5d2d11fc56d0578ec1940af60be2192f2f1b8d43dc67: 925d039cfaa2795efce751d71988395a9d8544d4910a71d82c761e6c8e51ba2e8: 6e5b02022079dc614c5f74ca1c784cf9700d832e05c2eec11f0ad0a37376b46d9: 2fb679aab258481705c982e553094522ea7bb93361711a8387ebf359e8c3e43110: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: 15428b80842f9a0801cf7667918b216c9ce4186d9825e806ba86972b039c03f9- root_
hash 0feab2262fa1e39174e25fc17ea9383a6fe15fa5d22c96afd722849e59baa3f5
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