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 - 1567
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id e732630b-b551-4965-92e6-7168c5a86d89- logged_
at 2026-09-08T05:31:41.864606+00:00- previous_
hash 99f9e4e868d17c901eb749ed5eeea79661b56df270c0d3f1bba738ae417b4bcf- payload_
hash 7411a7889766226a75042886d2fa7ec79c957541c7da85a50e3bdee6897d67d7- entry_
hash c14ad7e76f17779bede7dcb32c819a9e8e69f283da64261c7fd54c75b565f4b8
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.857628Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "e732630b-b551-4965-92e6-7168c5a86d89",
"series_commitment": "46df347ac91e762f6a0bd2a44323615a601de00b915e2b023f39448911baf711",
"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
85795932a44f0759f6e119545ff512b309f04e9edf615c86637d894642323187- 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 - 1567
- tree_
size - 2479
- leaf_
hash 11786d9d0bff7eeec54c1e05bcc33ff52580fe39b62af2687eca30322e62be02- audit_
path (12) 0: 0cf846a6f5aaa6b1607806705dde4e8484b3fc296ea8b7f13da3c4e73c0bea191: 6f4fad64d6ac15692e44ee2e68456a9583994a83dd4a310c9aad9f2f49f11a272: 82ae525b8850446a9092cc7af4aff6abe0ae575b8eea763b59084618041a0c653: aada6ebd03991fa1d61f61964da5ddf98cb3d8156ef9befae4c29aee12f5668d4: c63c56181eb3856824b063325b2e6c8ee64431e679d56e9238a6872228f648755: f2f7717586444815727d63f86cc5877958512d732169cabce0cefd8ec595f85d6: a14c441df27a3a317d0289503a03490705cc204897178ef38c051eec450bf5357: f4a858c5afd6d2bbfe79825cc00005d2e5bc4cb6a3723b70509ff06cb4f713008: 49fbc719d10777c21e02e255a1174dbc47e89c67c7b327c5f50e8ea1ffbb5bad9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 8d949d6aef53b2e3322ef5e232755263eaea63b886b405d936c87ac0c842b6a1- root_
hash 2135d33fc3b42de9408df8505e145fcd175142e943af391ea41c56bc99a1e5e2
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