delphi.consensus.snapshot
Appended 9 Sept 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 - 1618
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3b91df80-00fc-4a4b-b86e-3310edcb9332- logged_
at 2026-09-09T05:31:40.001219+00:00- previous_
hash 6b596812d6e26439ac52b7fdcbcb1ff86616753003c85bd8db29f4fab574cbd6- payload_
hash b81589bbbc41d7e393ffb253e9dde2184f76c88b673280e824f54da65b2a68c3- entry_
hash ceef474e7ebf92a51ca57af548ca49787924dad9b0036d62f11b0bddbb69f4b0
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-09T05:31:39.998266Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3b91df80-00fc-4a4b-b86e-3310edcb9332",
"series_commitment": "1cbe0bae8f24bb0255485a2b065897b48d2337ade1a39557aff666c2b1017f55",
"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
6880b3804168f0cd11569c37c29efee5f5e2558c3680cf8c55a45c3cde275683- 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 - 1618
- tree_
size - 2503
- leaf_
hash bd11816045cbfad3ea856eede34d1f0004ad5cdd6b07305958dce95d8200b13d- audit_
path (12) 0: da9b41094575235f2546edba0fdc84adbe5cb980303b9a868b29d3d2de6dc5441: 3eddc6e1853a3634151ee4023e3d20aab49cb3de30227ba16433fc1d5277466c2: e2bee6078cab5d96c2149861db42809bf25236c697364ea39843bb5575eb155a3: 8753f1be42017423934c927b70f4f93cc52e17689d46b8dc7dada07b371857b04: 39e5a5ba254b25c20bebf782d08143403c4b5fbda8f81bf64e319f7e1cc16d865: b1b6fae7089c27926a3b967b88f7de369c00e69d47160c303e67fd8ad3c0702c6: 00d36260786b8ce290bee853db49e73fdd5d2800eb992fa1e6e2b98e2e9d62487: f4a858c5afd6d2bbfe79825cc00005d2e5bc4cb6a3723b70509ff06cb4f713008: 49fbc719d10777c21e02e255a1174dbc47e89c67c7b327c5f50e8ea1ffbb5bad9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: aa4b429c2497df4f846fe6b3e60223989226aaf0ba6013dc6f90c17afe986d9d- root_
hash c97f540ea605dcd0a8a4165044c60093cb885a8303800b87d215a424a4d5258d
The earliest published head that covers this entry
- tree_
size - 1627
- signed at
- 9 Sept 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash ece15eb8383aee9bbf3f3bec9ccc72d87819c3947b61ecb8093ec13082289977- signature
9dr5EA8ZzKRK0L5i3/Zn8Rt3+PevClFJSGpb1IzYaNtVr+QKTJT2R+Qd9oJ77HQMV4y5WBTzci9qRcxNN4MqAg==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12