delphi.consensus.snapshot
Appended 22 Sept 2026, 05:30 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 - 2048
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3b91df80-00fc-4a4b-b86e-3310edcb9332- logged_
at 2026-09-22T05:30:42.241177+00:00- previous_
hash a497ed3d32d03cfb7d4e73555870f87f6bd31067065e28ed01bdcc051a6c0bd4- payload_
hash b6605e7923067255a6870f8574e4426264b550524fe2558ceb6be199dea0520e- entry_
hash 368414b74c776184fcb06b88c02e947965fdd447307ed07dcd8a6685c95f902a
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-22T05:30:42.237611Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3b91df80-00fc-4a4b-b86e-3310edcb9332",
"series_commitment": "bd8f73bc45e69fb9bac4c0c9c2c0181c07815db390498a8d3b9a10ed516c8b30",
"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
256b70e1174838ecad0ca1cd37c90e84bd80d2871f3ad9ce2c55669230792345- 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 - 2048
- tree_
size - 2515
- leaf_
hash 6c33f9d739bcd6e15b34a896e4649d8bb14268edaab0cf809df57eed477af59a- audit_
path (10) 0: a7da0b82cc056781088a9ea57417d24ad19e5af6d24d695c8c9fb7e01927f96d1: 369dd4a75c4deba626aa4b20affc9a9e33bd01360420d3f6418b37db351a68282: 7ae496c9905850bd7db207869dd5f1cf6913084a653104442ee526858bef59523: c45fe800324614f1479db84a4b7cbc943a1c81f43cddd613e688cb53148f1c6d4: a760a162330bdc84bc075c4894261393fd923a8e5442b5e6467037dc266fe4db5: 02d0dde49bb94e626ee08c2578f2d51d2b820b89a132a330ac2c7e0011eed04b6: 97e580b0f254128201e36dc81f73bca17443fd5e21d28fd611b3832d3123cce37: 32d97e61743fccf6d32da7a407cb944cdd5c52aa0de4e874e2c78dadf7892a908: 42bcd2f1a75494aef2c027c7b7df37127b336fd1fc6fe4575a64ee72af9e41b19: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 94ed3e67e0f3ca6ab90e872a7f03020d191548311e8610028e47ddc18fbfbf90
The earliest published head that covers this entry
- tree_
size - 2057
- signed at
- 22 Sept 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 857e19aa8f1cc7614fb9fdf9d058ec533ddc78750211f838d19db42220d865aa- signature
AVZv3xnQwzbC7q66pT25uEydYaqHraujngZDgUc9bLcnBMJY2/3cC1iWHhYJ8lzRwIOowiO3PxPF7hkUEEqqDg==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10