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 - 1055
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id e732630b-b551-4965-92e6-7168c5a86d89- logged_
at 2026-08-29T05:31:00.324109+00:00- previous_
hash 909bb539b7128e2a07820d7edde7633a5a61b5329007b3c6c394ac7dee18567b- payload_
hash 3e0dae001d5882cb077369b60692d9e324e63f5f1f7a59912195d39e146fb4ff- entry_
hash d925741e316914c8859d5bc3b2d6d836f12b847dad087c17b5cd8febfd890a5b
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.320513Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "e732630b-b551-4965-92e6-7168c5a86d89",
"series_commitment": "4cba7e39f61c8af7c8f232b2d015631ea7ae418353b03ed9d74d9d71f11a4c47",
"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
1830f938f1437176529b1e14a8cc5eeb4e423d998df7bb086457dbc579b0635c- 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 - 1055
- tree_
size - 2357
- leaf_
hash f91d0689e6e180e3b4776796fbad5aaedf44ab70a002abfd337801f4223766eb- audit_
path (12) 0: f7e8beba4d39502897b1c4329449b0249aa72003a5371233161a530d64f351ab1: 0c67035d144d47e18f3b291b52adc19ab412cfe5afd529c802ca02ea61d6e85a2: b84c86380fbaee999574d6cee65ece4dd4dc55f2c1674477c86f9ce91b5002593: 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