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 - 1051
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3d483c76-6358-495f-9f25-5cbef90fc78d- logged_
at 2026-08-29T05:31:00.286625+00:00- previous_
hash 8b839d1e31e47118eb551d6c65c6c1c9057f802509a7627a4c2d04063dd82ca7- payload_
hash 730ef0ab5adbfb2183082c898d90b5e6217b62b4f1d1641c5e260d291b0fe7f4- entry_
hash df545e65226f64ed237f9fc229a82f5216dbd143beedb6cb10ac67a1e410d847
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.284339Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3d483c76-6358-495f-9f25-5cbef90fc78d",
"series_commitment": "f4af39ffd4d8c0d6d445bfc22f32eba8c6bf6d8e376db763e3c3d5ca5629f0ad",
"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
c06b80e4ff0e7109b9d3e0c6fbee46568f98a252df4e424c70bcc18705941032- 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 - 1051
- tree_
size - 2357
- leaf_
hash 13ee0e916773813e0c5da732a18c09b7f4a8e25979eaf376d97747bb75cbd443- audit_
path (12) 0: 235d9efed52bd76ee95a6dadecf86ce3e7c03d04bdeba2f4993624a88681a8711: 51b75cc4af8126b70bba6280b0670f111912ce49d9ea74ef1de01a21d47b973d2: 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