delphi.consensus.snapshot
Appended 1 Oct 2026, 05:32 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 - 2276
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3b91df80-00fc-4a4b-b86e-3310edcb9332- logged_
at 2026-10-01T05:32:02.754542+00:00- previous_
hash 1835102cccaa5dc09e0b69d4f24c9fabf7a88e0952386d2f1fb31cfa47ce6d8c- payload_
hash 7546616fb86300f1343c51762babd36ce8329e920c0749c067dbe3215a26bfd0- entry_
hash d6e4bcfd3bce948299e079bfb62121c81a3d0b57fdaa49f9b81bfef590fe8a4b
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-10-01T05:32:02.696534Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3b91df80-00fc-4a4b-b86e-3310edcb9332",
"series_commitment": "a75b7a78fdf5456b9773a1f47a864802fb8bd322ade5db163aa8a821e53e71b2",
"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
9e7b6ce84a2e2c1511c4f3b6dc823bc55cc6c84e7e8da26c2ce0a4f211a9a57f- 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 - 2276
- tree_
size - 2389
- leaf_
hash 829ab05645f3f2f683c914465bc03b7a23083e01c705f7ce2c7ae4aaf5e695b8- audit_
path (10) 0: 2067d9e01ad84260e9ed8f98fe8989bedda91f12ea2c25caa7872252d34f6aec1: 390df4a0f6b44fef2ee46c23cb2a67ecc9536332273f6196b5cc5cb4da933b572: 9f47046bbc5697bc4d2b2d956eac2bb5b9e206111548a99c17545ccfef241a453: e8a87685ffc0c045844f48048e15e73d87bc3b0e8f22683bd6dc45e7883291754: 17915314b26d6769039107000ee4044a98d3c61a06eb7fa7121566ca8a4107f35: 453a26486f28dbe1e75e2f01f0d5e9fd3fe713113fe66b00eb5763b442ca537c6: cbc4db984571c13242d6f4b551c8d58b2ac60b14ae1df2945b6a2428d447c0bb7: 126596474757e47b31a2f4c9d89412108fada5bcdc7a19a9a1de3d4012be0b578: 03c349147789bfb063beb6c472906eef54792e9077566daa1ada925b4ce9b91b9: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 4f7f1a3085d540e3b69ac022c801823029c04ad350f74966858670c2038ea3cd
The earliest published head that covers this entry
- tree_
size - 2285
- signed at
- 1 Oct 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 17330c6327e6363b8237bd4a68d5ee420a6d0f745c8d8bab0a90305d6bccba50- signature
TlvQ+bw63yzvEDWcOD5MbBx7k0BSImf5PEym3jf4RkUEAcxz9SLwuoK5KlbtkboyqggWJf91cbdWSuZ+NP3aCQ==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10