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 - 1062
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id cd22f6a9-1eb7-4927-a2e9-6736a77b75cc- logged_
at 2026-08-29T05:31:00.389617+00:00- previous_
hash b80e9b059cebd3265c675890598caa431cd9060713211d4aefb4a945942561e0- payload_
hash 1e2ba52dbe2258eda8d7a1c1daee48074000fb558eca2d72b4f32c4f69e08945- entry_
hash ec4e69411075f019d8f4d3a7dad88fa9244c5cf1927c62a7f4f457d7b4f49d7b
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.386433Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "cd22f6a9-1eb7-4927-a2e9-6736a77b75cc",
"series_commitment": "d4b9626000621e809758ff9ffc0127b076091fe9f2250322206e23f7a4b2a32f",
"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
c0d0eeb8ddb6da2aacc8f94ef2cb17a357c123bd311d7d053b13783d4a3591f1- 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 - 1062
- tree_
size - 2357
- leaf_
hash a99b077ada9aa122b58f5174b35f67e3938cec15153ef91598c43612b530291b- audit_
path (12) 0: ed33982d3e8541d36fd68bbe77b679bbc8fe1da6d73e53d8f215f2b951857f431: f6b12b7c79de45cc26b602ff18e7b02433871279ab8d8b8de0e1fd1a757fa2392: 7c1bd85d04125d0d779993c83e7e7e53685c0ebb10fe88a8515b27637b8715273: cefd9d03f3c76d3d7de3e65a8238184df1c4f1757ab1a369726dbec6f31f084e4: d0267cbc326f3cc9e4ff338f21eb34ace34989c2f89b76c958e5491bfb9fa3ca5: de01980cc2d9fbeb76026da9c048d75551c73417ef383a31739b0bbf4a69e81d6: 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