delphi.consensus.snapshot
Appended 30 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 - 2252
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id cd22f6a9-1eb7-4927-a2e9-6736a77b75cc- logged_
at 2026-09-30T05:31:20.340136+00:00- previous_
hash f60c848d91956804e370ba589f3aee8f72bfaea2736a0c9bb874655c32449852- payload_
hash e13af0424c06558bfd704f2b7ad52721a40cdedd80db0ccb5c7f2b0dce009eb6- entry_
hash db18a4a1eac8ba8002d8a5025d2a07e2d32083278e5134f5a72b91db60b8e0c7
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-30T05:31:20.322025Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "cd22f6a9-1eb7-4927-a2e9-6736a77b75cc",
"series_commitment": "94fccec5a7eda1135392790f027f66b8cd12c860f86a25319bbb5b7af766be15",
"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
653fb17c1791a5b0a0987d82dc28394c5622bdedeab6c07a8e809ac3d3510e89- 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 - 2252
- tree_
size - 2389
- leaf_
hash 098bcad7311c97618ea0dde370c0cfc34933ac97567b9967af40a11cf8d29a63- audit_
path (10) 0: 20310af3ec840a71bc16201fd82559ae636fb9b965ba7ec83c31b5691423d0d41: 196cd64a90929c1714fb95e861917d19398c3cf6b6e1db1870262b5ad6f80d932: 90b974b0e4590b4981b5a36c163e525a998e5187759683a0722edf66b7dccab33: 3c4fc56980af2aa0f69b5f9d58fa505229ccc5321b0a2659bd6ffbf9489254dd4: c068edafbe1d556931252450f48dd023302a27a3e529738c33e3d621eba495945: dcb1e788d76f2f9a839c0389799b0d205491dea92f2f56774d104d9ff08eea1a6: cbc4db984571c13242d6f4b551c8d58b2ac60b14ae1df2945b6a2428d447c0bb7: 126596474757e47b31a2f4c9d89412108fada5bcdc7a19a9a1de3d4012be0b578: 03c349147789bfb063beb6c472906eef54792e9077566daa1ada925b4ce9b91b9: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 4f7f1a3085d540e3b69ac022c801823029c04ad350f74966858670c2038ea3cd
The earliest published head that covers this entry
- tree_
size - 2265
- signed at
- 30 Sept 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 0feab2262fa1e39174e25fc17ea9383a6fe15fa5d22c96afd722849e59baa3f5- signature
sBjF7+G1kwx7TvtzLvw4PVBUGRz/EBjcsSFszE4oR8Sldm2d36cygyHFWsQscgAwwkpOvuaKoBjxVsrH/E1HCw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10