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 - 55
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id b6f50ed5-05a7-40ca-90e0-588fcc89df0b- logged_
at 2026-08-15T15:53:37.359992+00:00- previous_
hash b4f6975d9ad75e5ac1b3d71576f570364f5621327b2c252ba06971fd9ad7d2b0- payload_
hash 4b66ce271bf14fbb61adedaa68568cc24f1b3cc8042d3b93535689efd1c843a2- entry_
hash 3f333ce6b26689d3be3fbbb42b7adefe72f129b75f3133768f75c11412ce654a
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.356741Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "b6f50ed5-05a7-40ca-90e0-588fcc89df0b",
"series_commitment": "0fba345e51a6f5e911feefc5902c3a3a8738a3223eef0ff6354d0daca2d6234c",
"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
995a1ea8f13fad873809d1e8a5c10d4b09333dbb1abce8435394999fd4add1ba- 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 - 55
- tree_
size - 2265
- leaf_
hash e5cda8ebb9c4ebb21a6e06bcf6fc8bec14de2cc86c30f5ba693617d9ce670662- audit_
path (12) 0: c4175b4560485a13adc2a6d8997a9b2357f74ecc5640b33f9c5f645ea3f1b5b01: 96e406adc6053a4110a5cffc307df681ba31180996cd9c9f58cc4646df497b1e2: 2c888ed5658ad74af4eec38d1bf83a7f45f6f309547e37a50916a13b27e43a743: 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