delphi.consensus.snapshot
Appended 30 Aug 2026, 05:30 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 - 1107
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 7fc5454c-0827-492e-a574-d01f70586fc4- logged_
at 2026-08-30T05:30:41.031589+00:00- previous_
hash 1ec172ba18a9188e43204cb59f70110ba247bc82992374989ee8c3ad0b32b872- payload_
hash 585ada7a7524a57253036ac884eab038be3bd521bebf862af32eaad528fa0cda- entry_
hash 63518eb388834012493dd1d5a3547d971d0c82a8b459f9acc12fe206bd11e7e2
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-30T05:30:41.028823Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "7fc5454c-0827-492e-a574-d01f70586fc4",
"series_commitment": "b92f5737ea80f10b3d7991cc428d0127d6e8c8d0d8b4da4fb31cd1f4f3f9fb04",
"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
298f8bc899e357a350d85fbe15656ede1d42369b2b5cae07786af2c006719d3d- 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 - 1107
- tree_
size - 2373
- leaf_
hash 339b59e47682cd14979a03736f19d61ea3a96b58012250878c618cd5e82d2bfb- audit_
path (12) 0: 7dcc4b02d1a8e0e50d45cf841fb2dc7725039ba2e6256bc025443bd957a451431: 01c27f745378fb8b4db9bf4153cbd46fbfd64dccfc07013ee5f410bedc4847732: fd8ec32b13db99052cdd607269250b883def71713b9a259810beca7357bd93e23: 9e64e9935c6d2296157cfea59d898a4bd91cb5c1b4af8af1c4fcad08cf04d66c4: 082abd3851e6828c8ff227c8cb876ad3b2f35792788c1ec7782d22c728720ade5: 8947d8a1e70be2b634115b93456cd4640838c379021b8f3207e435521e78989e6: 3330710dd5fef91aa0e763e3b3c0b21b7b27e549cf2bfbc05fee8e8bfb1f42b77: bbfee2f96690132143d2a2a16089df72535201b31174873b1f1a4d4c85a029a98: 6ce18fb0b650e54a2c9454c3e9abde48f8386826f5bd1752662ede2993ff557e9: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: e804ff886a070163c1b488ec61deb30f2df369da799b5000bbf882ab4514b647- root_
hash 1e267d0ac014ebb6f08aba71abcf460d744c241ab259158739e916a593073e40
The earliest published head that covers this entry
- tree_
size - 1133
- signed at
- 30 Aug 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash f93488269a5aeaf9d50291920769e871ba9d361f0fb72089c9ba41c88a2727b6- signature
nnzoG8Yk362jKSvRmRO456zSfVqvhFq0AoyJZsV0jjpigKArT+n7iaJbA8sAIeqGXEUgCqPLF9MrRlQug43xAA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12