delphi.consensus.snapshot
Appended 29 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 - 1049
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 54324c2e-b8fd-4bfd-afc4-1b6e799c095d- logged_
at 2026-08-29T05:31:00.266429+00:00- previous_
hash 7b52b98d844411e172ebe5b671d9c0debf7723a673ecc4e8bf90493d9af49d70- payload_
hash e6f104407c79560313ed05a2612c680a23f51f981cdeb21c296f81725603be23- entry_
hash f4e3334e7f75283ce061a86541b18afc73f69a4690885966bebe0a37b0c0a1d3
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-29T05:31:00.262175Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "54324c2e-b8fd-4bfd-afc4-1b6e799c095d",
"series_commitment": "eff0d41d0dde923689a98f62e38bdd55c0b90268b7b1c226ee1687f8ee4d0347",
"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
9c654fb473d99fec811341d0f688b73d42da090c785228e9528e7db2aa0496cd- 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 - 1049
- tree_
size - 2357
- leaf_
hash 78af35e2394ed5b760b3ec502289498c1ea1c5b3eb7d78b6315a7ae69d3626df- audit_
path (12) 0: 6d6f124d8bc33223f7517da50bfdf0718d4d3f44daae8f7afa614cc1d474beb21: ea492a325de1109338c831243d3d157203e7a7f9bf320187a98d1346649863142: 106e4f28aa154fcaeac38ea9eaae778dca00cee21788ef4016068ca103e53d6c3: bf2849adbdef1631e2422a3c4196e5268cb93f4e1028d15715db6f030c56b9b64: 114eb5b6aea14939359b7d1545e319dafb313fd370da56fdb25158f4c7c458625: 734ede06fe461c17a65d80d7f64f6bb703132ccfb952d1a5a6f953f7e23c592c6: d82a2e270b0289b874ebb92edc37695f28bdf9f53266c9bda129fd6b58431b787: bbfee2f96690132143d2a2a16089df72535201b31174873b1f1a4d4c85a029a98: 6ce18fb0b650e54a2c9454c3e9abde48f8386826f5bd1752662ede2993ff557e9: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 2f361a0c4a49843181536f3a7baa572ba4bc0573be4bb8272112c3d056aa1031- root_
hash 58c8c5ab99dba36e8c6b398578e37592253a716c9cf756f72e78b6606a198d59
The earliest published head that covers this entry
- tree_
size - 1073
- signed at
- 29 Aug 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 5dba160bb906a884e1f1fb90970356c08cd125402790a82dec37eed1ce1dbf60- signature
pp/gqpXj883uC3rBTWjoYIk190+lqVqjxj7iskZY/ZhrKiUo7PHanG0AwhJgLmVKUeHax3qxw2kQjeT8SweHCw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12