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 - 2275
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 29f1e88a-b6de-480c-bc2f-f234c647455d- logged_
at 2026-10-01T05:32:02.580948+00:00- previous_
hash b92bb3ee7b7de34df3e462d2effa4afa3a52f646a2f87687830bba3b9cce8c7a- payload_
hash c149ae314b9dc1adced73001b13ce6dd22de0ba00fcee15f45e59697f5b16c3d- entry_
hash 1835102cccaa5dc09e0b69d4f24c9fabf7a88e0952386d2f1fb31cfa47ce6d8c
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.544420Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "29f1e88a-b6de-480c-bc2f-f234c647455d",
"series_commitment": "d4bf728c4403ba011f04814a049ebbf4d71a2afce6da28aa91c02b57f887b9f4",
"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
beff84da0696f709a085725bdd16546d6ed8e3add80c07170efc2768f359364f- 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 - 2275
- tree_
size - 2389
- leaf_
hash 2d35c0d1768298455478c260daffa661a56c78206340af7278401ad571a0f700- audit_
path (10) 0: 0a9514f267b5fee7588f229da3f6e709a5c3e6180a1de805ef06b6144313f87f1: 2af5ce7353107a3e88e49a7b847c808ecbee5d2afbcf65b7cdc95ae6f33a56932: 95e45a36fe6f5903206b65e17fd0d114a8ddba08bdc1d36d52e535b1628c7e513: 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