delphi.consensus.snapshot
Appended 26 Aug 2026, 05:31 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 - 863
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 0485b0c1-a674-414e-9778-a898c974bd9d- logged_
at 2026-08-26T05:31:21.288326+00:00- previous_
hash b566737a675bf8c62c2d542074ff82e60475adf06fc2bc5729655c634041bf06- payload_
hash 2c9bd2937107f9ea3c19332e8229032eb4bf120933b654c65eb9eff0f97264b2- entry_
hash 0b5310b55f853fa9e7efc12e73919f09b697356a4740fca9fef4fba889cca495
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-26T05:31:21.284785Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "0485b0c1-a674-414e-9778-a898c974bd9d",
"series_commitment": "66786effaae121bb11d8934d79c8399d089010209b641ba664073b81800b48cd",
"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
8ce65c5807cc3c67b4c121eb61589b8d68186d4e8d727b82bc50583e852d76de- 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 - 863
- tree_
size - 2285
- leaf_
hash 2389c189aab4d83ac2ba2e4366409330c9b4e993d8dbc53f9c126b0a7d41c649- audit_
path (12) 0: 01c9219cfce3c2d9bed0e08d3b3e589d9d289b48d4b39e710c01aebfd49dc7a21: ca525be6a045a66c8ffe292699316181da571980a2d298875bdaedd0f407cc9e2: 9c2a0dafc21ad532f67907528664bdcf887db442800e20fdcd4eb44e2a29c4a03: e65a6deeecdf188eab482b9915848609a900ef35fd583f0f2856a1f3c72f7cbc4: 9cd8a6bfba6591cfa3f8b70078a79ff86cc289427dd3e966e21beee04548c0445: 0b8d901001123ed160fe9a78454fe298b537c0333de7419007d606d829d3e4336: 4d2bb962b08e7d02e1409329aa3652b71103484fd25b8d3f56baa89c1b2c43407: bc6ace31149b3e9c1ba9d5f2b34ffb85a63422d9dcf2ebf241b2cac10329bca88: 184a24c3b623669a5fc418f1a01a448ab12c5b650e771370beaf16f761dd2e6c9: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: a95d574e00e9fefbc454b084e8cb19edc83831071366b2d8dc1af2f7114b646f- root_
hash 17330c6327e6363b8237bd4a68d5ee420a6d0f745c8d8bab0a90305d6bccba50
The earliest published head that covers this entry
- tree_
size - 891
- signed at
- 26 Aug 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 1b6242aee4572bc1cf018b1691811ecd6b368592cda0591cf6a4aeeddde5c07b- signature
Y/2YtRN8eDjfqUhrXHsTAsGI7CAljXh3GfV+XD3uVfaQMz3fIUak14+OLTbFm9tgH9HQdSJtHTtyD/roGWLnCg==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12