delphi.consensus.snapshot
Appended 27 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 - 2179
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 4bfc7aa0-f12f-479c-ba06-d8e4cebfe625- logged_
at 2026-09-27T05:30:21.947744+00:00- previous_
hash 051b8319ebd1c9ed0e4e1d0527824365aeb373e9ddceaec5dec3fc7549709800- payload_
hash fb7deb5eda010489088b078572f46a0e3d109b3f24b7e4914cbe499697392415- entry_
hash b38211b5cb5630ba5b25161a10d8dcd9ee2fdb86fe710bef88cd5febe252ad30
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-27T05:30:21.943845Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "4bfc7aa0-f12f-479c-ba06-d8e4cebfe625",
"series_commitment": "35cd01fa3fc8ca7550ac9efeafed93935fb43cb6209b39b515efdad18aea2ac1",
"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
6b55631ee0c51100a152d586d1b486f37e72bf11c16b35ef009e625e1f570ed1- 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 - 2179
- tree_
size - 2515
- leaf_
hash 5b49d05f70704b1acf657645fbc814332d9675a7a2cf402d119275acb5afc9f2- audit_
path (10) 0: 06d58d157ad826ea0d256a8a19d79f4a04a34e1217a428243096f48d84a334661: 55cac9a75cf508668c636970d4916d7bb9f8744bd10336706a9a364871c97cae2: dfaab98a4becfd042fb3b37de69ee41784c4630d9d68442d4ea3bb21a87ae8e93: ed3a76cf89ab882e3f8ce250f3dbb03f8c6da0f1d8761cbe57148314b5bd20a24: ca7191c480f6b18f2aa9dda035866fed87fbdd940ba16b9f842e3e09f1e1efd05: 0349dea9398b8aa40633af547e822a1da687592d53272f4e6aa136e48023a75b6: f30320e32b01d85ee25d3699765f61034c40add7177cc53ee3e39fdfed97b4367: 126596474757e47b31a2f4c9d89412108fada5bcdc7a19a9a1de3d4012be0b578: 42bcd2f1a75494aef2c027c7b7df37127b336fd1fc6fe4575a64ee72af9e41b19: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 94ed3e67e0f3ca6ab90e872a7f03020d191548311e8610028e47ddc18fbfbf90
The earliest published head that covers this entry
- tree_
size - 2187
- signed at
- 27 Sept 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash b1b50955e5089069aa81067ad2479df134298ae6bf7dee437daf781fa54ff0b6- signature
t0dWB84xoVBksXiO35mfeoTvij91UZx6rGZhLHqb2/zFwm5RcmHkzpdfzuu5kxVcT2cgqmmgQGI1XHIHmyc5BA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10