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 - 2278
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id a8c36f16-c0df-49f5-92d5-29bb1d0e58a9- logged_
at 2026-10-01T05:32:02.956392+00:00- previous_
hash d77896b7cfeae3795e56005b3edabda0c2407372762c1d22182224ba22743a40- payload_
hash ab9770a7276502934d82653d8c4f99b89d1f3d47e7c27b78a43db80dd92e59c2- entry_
hash f33727f0d0c285e195ff0480b20c6761e0be4dd54a6a67f9396a05587d12e8b0
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.909268Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
"series_commitment": "885b6f453e34fb683ef099b05f338fabdcdb504d4b83fa9bdeaa67700b1bcc83",
"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
951a01de5aa15b47209231d1af95ef4ac25459d979f7dd36a397744f82c8d840- 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 - 2278
- tree_
size - 2479
- leaf_
hash 774a82d5327997233151836c1ec9245ae3da42395d0748f7c990e59f205bdb4f- audit_
path (10) 0: 47ef40eef6738ca8dbd06fb40d9dacf129aaf813083c311f1c02d59872420f0c1: 1505853e8c78a4670dc0bf0cf74d663a265e1e2e1d33f943e436cb5faadf03b92: 9f47046bbc5697bc4d2b2d956eac2bb5b9e206111548a99c17545ccfef241a453: e8a87685ffc0c045844f48048e15e73d87bc3b0e8f22683bd6dc45e7883291754: 17915314b26d6769039107000ee4044a98d3c61a06eb7fa7121566ca8a4107f35: 453a26486f28dbe1e75e2f01f0d5e9fd3fe713113fe66b00eb5763b442ca537c6: cbc4db984571c13242d6f4b551c8d58b2ac60b14ae1df2945b6a2428d447c0bb7: 126596474757e47b31a2f4c9d89412108fada5bcdc7a19a9a1de3d4012be0b578: fc41f233aac25cd7d868667ffe62e2d6bc79ebfa41e20ba3937ba4144f68af369: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 2135d33fc3b42de9408df8505e145fcd175142e943af391ea41c56bc99a1e5e2
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