delphi.consensus.snapshot
Appended 5 Oct 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 - 2349
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 4bfc7aa0-f12f-479c-ba06-d8e4cebfe625- logged_
at 2026-10-05T05:30:21.062757+00:00- previous_
hash 86e67cb2a75b0be3223632842ad27ed31c96f31fea85626cc2217f5919fe9efb- payload_
hash 55491da57c0f92b6038978d700e54e3a5b7a1a2ac4ca461a895192120ca9f27f- entry_
hash a3f29f628a1ad4a48cb1129f82f33cef9fad859c34a1f78ee973dd1eb650d672
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-10-05T05:30:21.050280Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "4bfc7aa0-f12f-479c-ba06-d8e4cebfe625",
"series_commitment": "c90fc0f86f7e360bf4730a34befe2b5780c82fc54a4758c097806813bd67e432",
"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
f98c93d41bf88def06850149c4a41a58f79fb3d237b7a666baa9942cbc379bd6- 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 - 2349
- tree_
size - 2479
- leaf_
hash 255d92f2dcb96289c0a35619474f08bb40b4543705c914320ed25a2f2fc076cb- audit_
path (10) 0: de062d64eb976c93f0e2ded7ca441a1b151de1c1e7cf720efafbd615389352a11: 76567e27851103f26d6315afe673c921bb379db3096359f5ecb39cf7c06b125d2: d50490e6f9397a688172c1f71c0cf0cb3072af9faa332c2cdd6c896671f0607a3: 28aa0241b051bdc60ed1d5300cf455d21212b810db8d5c02f4c9add05b5f08d34: 7dcd25b3c98562e656f4d02e51c8fe4401ef9961c96942d96328da987977199f5: 92498c2b48d5d20744b9266e1c2f22eeee4d089e5a8ad2645ec11941889cc7156: f60923cdfcb3584afeffa8530ee1cafb60e6a0aff868cd02794b4b9e5ed208eb7: 99ee92a7962953bad0227dbe9ab05c66de08e3b0b7eb51768dee6e3fc62b3b558: 765303d6f29939e50694ecde6538ee53e894bb299166d5a65c9a000adbb546d99: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 2135d33fc3b42de9408df8505e145fcd175142e943af391ea41c56bc99a1e5e2
The earliest published head that covers this entry
- tree_
size - 2357
- signed at
- 5 Oct 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 58c8c5ab99dba36e8c6b398578e37592253a716c9cf756f72e78b6606a198d59- signature
xirAN+AGnV8OMbXLhyTyIr8tL2yeCmVCQzEWsX17jN3ibAv8OM5FjxuXn6qQUzvxDbqxwqbiRKdCifgC58vSCw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10