delphi.consensus.snapshot
Appended 28 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 - 2203
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 29f1e88a-b6de-480c-bc2f-f234c647455d- logged_
at 2026-09-28T05:31:39.546070+00:00- previous_
hash acdca031533ceba34a969b378a28477e07d23fb676398a831c453c1cf6b09e39- payload_
hash bd2bbdacb154999be1158b27fe5e1b96afa9105f12cd0cf0da74ea1d6b6c1f66- entry_
hash 105344bc001d340261b7852356616d2610709c6f05252007ac8cad2474ecec16
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-28T05:31:39.541525Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "29f1e88a-b6de-480c-bc2f-f234c647455d",
"series_commitment": "cb44122fc943b5b1409558b82446d97fd33c97884cc2e6c499e81d792e03dfd7",
"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
d07aaabd9c1cdf4db1bd9d9d1bde9122622ec5d5ebfb66d558742541784b7417- 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 - 2203
- tree_
size - 2389
- leaf_
hash 8ce7b192b09cffbba50beeb6a99b48da7949882a2ed02fc78c0cea44174bc938- audit_
path (10) 0: 1b45f917fc34fe73bf8e76a36004fc545acfc900ce2288ebe504944b6a2080e61: 69090db414372ae7599c05b1342c99e6e919a552fa5415d2ac81d38c36af4b5a2: f123a9fda4fc7e90d1402c6e5ab25f274e5f1ac1933666406a0a8168625c5d4d3: 8285573693690377c5f56c09150338e11062ff5ffc6f2343af99fd370976ce9d4: 49bba1cab8bbdd43d7b9bf51acae2e4ee13dffaca0854642ee664c756f28e05a5: 0349dea9398b8aa40633af547e822a1da687592d53272f4e6aa136e48023a75b6: f30320e32b01d85ee25d3699765f61034c40add7177cc53ee3e39fdfed97b4367: 126596474757e47b31a2f4c9d89412108fada5bcdc7a19a9a1de3d4012be0b578: 03c349147789bfb063beb6c472906eef54792e9077566daa1ada925b4ce9b91b9: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 4f7f1a3085d540e3b69ac022c801823029c04ad350f74966858670c2038ea3cd
The earliest published head that covers this entry
- tree_
size - 2213
- signed at
- 28 Sept 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash e6ef985c2d8c02c6ad806a1fed9e7dbd1908860b7059dafd6031fd735675222a- signature
lZwXVggSbp4U9M4HPhBdliPV1fW7ltXRhHCMzOGIxk4uVObAicLqZ+silW7WvZAEBoECv+It+4rRV6HqbOHWCA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10