delphi.consensus.snapshot
Appended 11 Sept 2026, 05:32 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 - 1702
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id a8c36f16-c0df-49f5-92d5-29bb1d0e58a9- logged_
at 2026-09-11T05:32:21.397869+00:00- previous_
hash e73b1358c379ea61df1ec45195318fcebc601348302f1eb876332eeacb328318- payload_
hash a67c3e3b087b40cbe12827f2a6705c4a1edd65787decb85fee3032213ad895a6- entry_
hash b3e25b64af943045960c96e0042750012aec003d3128cd70ac137240feb7e0b0
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-11T05:32:21.395103Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
"series_commitment": "8a6b6608adff0107ca0d938cd441399c467e55c8e025dd68f606bb9a91ab1c20",
"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
12b5590277daff8fe5f0af222e44c95b9a5cc5510beac73c65e3ab230b720c71- 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 - 1702
- tree_
size - 2515
- leaf_
hash 7a1a268369bf6540afa3c6369483d2e392b820053632cafef75c5a7d13bc3b1a- audit_
path (12) 0: c450d67f3189bc297b16e2f763a0ab72ecf8224d72a8ccf8fb98aa78e67cf3f71: 4b9290eaf653ccef45bf3839b4d243f5212e466698e0f47029c13812d85c68252: 846a3af061c7adc47d758538e5a5950d7c356cd8ca32b50cd7e24a2ce9a786563: aa8ec3c3ded0b9593c78e2c80c56f7746b547496f4af7b145b72d7c5431780944: 7150a8a2fe4eec9d4ceee6bd07ba0db3dc162e8f34c7fe3a067e2fe5913ae9ec5: b819eb725b33287e475b3b957c5805ae185bf7fbbfbf66638ca28dc7f0256cf56: 67d3a5f070d2cf8390b34d7293fad5757f74160be9bb198580c670e63fbcd4217: 89bbeb672caa03ccca78c3e7d709e14d72ed0f279c7cfcd435bb71dc863239c68: 49fbc719d10777c21e02e255a1174dbc47e89c67c7b327c5f50e8ea1ffbb5bad9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 07e77d0b86e68e9f9b9a10013a0034c87fc2ef91312163906ab27730e4a116c8- root_
hash 94ed3e67e0f3ca6ab90e872a7f03020d191548311e8610028e47ddc18fbfbf90
The earliest published head that covers this entry
- tree_
size - 1709
- signed at
- 11 Sept 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash e91d99cb0270fb7ceae4d325a6b43249f697d71664628e72786a644f95d469d9- signature
4AJfAwvJaixLHP+4bphw9Qkl4ZaR6Cir4TrRrdxqNt4vK+qmVVd8CVQh/FIRVoQ98A3JuRAAUq4ybP3nTHqwDQ==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12