delphi.consensus.snapshot
Appended 24 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 - 2098
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id f69e4ff3-bcaa-42f5-a8f1-8044a9975b0f- logged_
at 2026-09-24T05:31:21.437029+00:00- previous_
hash 26d81baa8d589a1ac894e9050df990c1c27336785666ebada138b246bb3a19e5- payload_
hash 3f3657efff5a12ba413c2ea74ce041cf82185d6217da2dd4dc89a540e4de62f6- entry_
hash dc56f70b185ea6f15040b8b5125cf0859335a52f8d7a227f2809593d3f6fe103
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-24T05:31:21.433116Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "f69e4ff3-bcaa-42f5-a8f1-8044a9975b0f",
"series_commitment": "cfc8b07998a7d7a49e07374052d90a9371472a687c94dc147b12c1ca80393a86",
"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
279cc5e65c0dfc323e49047db7e8454d34c87e0e592dc032754ec78e64a40f75- 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 - 2098
- tree_
size - 2305
- leaf_
hash 50900c2e377d607bede4b6230932b1279205bf7fd1ed3baefeb2a625b1ed82eb- audit_
path (10) 0: e813b931b84b50773e522c9b828d2e3ac679a111f7b6b30c2d0bb52f4cc926751: 01ff86e99d74e60c74345e7e7dd94dbf01b907a607a4f457bc811d63b90d361b2: 2fd8dc370210302f797dc17c7bb703d39e6323787121c0bca21549ed81f22c743: c8c67b194d77a900b07fea27ce0fa8a7320de5ac55608eb16fe714e19dd2f0f24: b50be66eb4e6d6522ae5a50862f42e8f6a5663bd96a07ce297353a7a9eac28d85: 3409250b2a7726d8587c9c1abf72ab8a5f5c9da864649b1684c0d122c06aa26c6: 97e580b0f254128201e36dc81f73bca17443fd5e21d28fd611b3832d3123cce37: 32d97e61743fccf6d32da7a407cb944cdd5c52aa0de4e874e2c78dadf7892a908: 473a4b5543605f153f443f2ff2003dcedaf99566d17832dbb7bf9b100555c5ac9: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 9259657b60d7c54c7f061a7a621bf2f8747cab0885ee335ac1ed3b6657c9740d
The earliest published head that covers this entry
- tree_
size - 2109
- signed at
- 24 Sept 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash a31f6b62ecd0a5a7c1047a6a100107a943b510cb76232ce57ee7beb14ed29366- signature
XPXY8TNF05VBXoAX7JDAXHp2GQM3ww78P37YW9pWBrGYGusEDyuG6M7S/0ia9+KBJ+KmQC26izeb9cFfRf3XBw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10