delphi.consensus.snapshot
Appended 29 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 - 2232
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id a8c36f16-c0df-49f5-92d5-29bb1d0e58a9- logged_
at 2026-09-29T05:31:20.844234+00:00- previous_
hash f194ba7f0ca6a0416947c65a1a89091fe509ce5935ee242fc7c88ec66939285e- payload_
hash 8b30e38bd4fa95fa84499a17c57924654ee9ad47313697e8cc23bff88d09f4e4- entry_
hash db3cce5c28cc5106667d603d178df625a79d24dea76bc35a49b4fe9faa95c785
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-29T05:31:20.837865Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
"series_commitment": "1091152b21b1f032aa5eea3e7af1e99a5d80f38f4f7663124bc25f51970e6301",
"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
35f018c096749311f6caa4a3864d4580fe32b7f699ffe22c3fbfb9b3c4db12c7- 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 - 2232
- tree_
size - 2491
- leaf_
hash 01d763ec01a7818e9baa8b9920bcdef61fb9622a6898e37feba5f18e54cfd396- audit_
path (10) 0: af238efa0e6246d7fdd99ed0da2c005086c545a3a97246707f1ed1e833aebd8f1: 175ec4bd610d2c0def7a7a22bf343c32106b476e0c2fee92f9015079b74eed2e2: d2ae9bd3b5dac7636bd99d24dd27f764c89bdbb40927dcf05e121821708fc4033: 7f112a9a92cb543bd054802eb37a2dbd4be21544a78d72a646028a76d6d2afff4: d2c68d760af74d87740ca89ff1ff67d32bd189e548ad56ef83ea1334e37149175: ff576d5d5ebff608e9a429939d33e803b4f824aa935c65d508ae2b3f2eec66696: f30320e32b01d85ee25d3699765f61034c40add7177cc53ee3e39fdfed97b4367: 126596474757e47b31a2f4c9d89412108fada5bcdc7a19a9a1de3d4012be0b578: 669485cd765b7ea152259269d95a4789b962c3f1814e587b3e55ddaf172378ea9: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash a9a1dac66ff7c8ec3d4b27b434ff70fbde5df3ef3dcd4b4fe4b41bb80f78a7c7
The earliest published head that covers this entry
- tree_
size - 2239
- signed at
- 29 Sept 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 03dd6fb33b4bd65222257eec0069956926795f14f7354795bcb42af5fe51ba08- signature
u8ChL0jIyB0SQwYB26vHeURVL3Ia2DcWQObp46M30jJWJb4SKWQ36EVhUNp29FUDMGkSZ7aAlkHhiTbNS6OGAA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10