delphi.consensus.snapshot
Appended 8 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 - 1562
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 28453d7d-6676-414d-a36b-2fcf2cf13265- logged_
at 2026-09-08T05:31:41.809607+00:00- previous_
hash 5f3b916ed8b9dad67437d8b23c76db01dd8d70bc46ad0ecb570f5bfff2d0c062- payload_
hash a0d435a80bb1e18922bb7fc13bcc43d793efd93fd8ee1f8d85eb50201d19cec2- entry_
hash 5632d7ebedd9b166fec254764333640a9cc9639675e0a9d62409d2d0d6e1d0ba
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-08T05:31:41.800359Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "28453d7d-6676-414d-a36b-2fcf2cf13265",
"series_commitment": "e559adba660d545b9b846d5916c87d54a4897e60304c8f50a94f89999ff19e52",
"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
a9839c0de0bd62c1cdedbc4c0c199a488487069062c36ab012ee76936c412e16- 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 - 1562
- tree_
size - 2239
- leaf_
hash 0e53262ef9263c2844375e2d515088d18656c1817dcc3818f965151245860202- audit_
path (12) 0: 8dbbcde48d82cc2a82af44ca4e4515ac0f7e3be35c0539e48b26ac44d7ee2ec11: 199ad6ede52b2aaa0cbe513a17c22db31547807abc86a7c51dd919d0f446ed342: 0a93b80d40db716eba19f534bf0101387e36ebf6b06c1c51c15d75ed745e91923: aada6ebd03991fa1d61f61964da5ddf98cb3d8156ef9befae4c29aee12f5668d4: c63c56181eb3856824b063325b2e6c8ee64431e679d56e9238a6872228f648755: f2f7717586444815727d63f86cc5877958512d732169cabce0cefd8ec595f85d6: a14c441df27a3a317d0289503a03490705cc204897178ef38c051eec450bf5357: f4a858c5afd6d2bbfe79825cc00005d2e5bc4cb6a3723b70509ff06cb4f713008: 49fbc719d10777c21e02e255a1174dbc47e89c67c7b327c5f50e8ea1ffbb5bad9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 9203a1600de814d3afb819f841569332c7e3b58c4d0e0ea56c377729f25dca49- root_
hash 03dd6fb33b4bd65222257eec0069956926795f14f7354795bcb42af5fe51ba08
The earliest published head that covers this entry
- tree_
size - 1585
- signed at
- 8 Sept 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash a224a45fec4b50dd9d3a17f401a022e1320b8849bcdcf3109bc5ef8fc4c335cb- signature
xJYNwZXpQpbXcZskXqf+SutDkfY7nOE9BO058X7fOfif0VtoI/OM8Nfg0bN8D3iUjEtOt+FT3k9g7zbVw7vLCg==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12