delphi.consensus.snapshot
Appended 6 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 - 2365
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 4bfc7aa0-f12f-479c-ba06-d8e4cebfe625- logged_
at 2026-10-06T05:32:20.949959+00:00- previous_
hash 83888bd67480c6aea4de944bbf87112d3fe7397f5fff6edf783568c64f47b7cc- payload_
hash 2d849a2803a844ea7dde64a16f908402a070b53bbb4c1123865543d6b5ef8954- entry_
hash 602ccc29bfd2ad0eefa17371d5c7b05b6c5beb310d4fe125392100112fea4588
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-10-06T05:32:20.939187Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "4bfc7aa0-f12f-479c-ba06-d8e4cebfe625",
"series_commitment": "9921da9152b118bd31da630416231e15e6f3d23369543fd6f608701202bfe247",
"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
01079e84e2fc3b5c3eaf9bc58d912a0c5751a4bb20ce12999ddc959a0e3a67b8- 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 - 2365
- tree_
size - 2491
- leaf_
hash c9fff60e0eab8c239cad7a83ae99555e4f672133c76f81f314eeeead9f93c4c7- audit_
path (10) 0: e3206da6ff152dd241e2677cdcd5a4912fc2193d0a557f0384dc48dc16d293671: 2176eda51b64504fe6a972f5ee9f0feba44ca61a9a6b301cf543ad1f6f6d977e2: 4204db5cde69200737da040121557e23256d46ac8c1c431c2e487f6bd604303e3: fc19df759478c8865bde788718abaa419a32c6dd11820cb9d319842244ad013e4: e3a5493808b2dc3f3403e8bfbfb7883f5058dc4d7825625826de5ec37e9b742c5: 92498c2b48d5d20744b9266e1c2f22eeee4d089e5a8ad2645ec11941889cc7156: f60923cdfcb3584afeffa8530ee1cafb60e6a0aff868cd02794b4b9e5ed208eb7: b23da60f2e510b29c72a07aff7b47743065a5b6d552266a144958cf77a987e958: 765303d6f29939e50694ecde6538ee53e894bb299166d5a65c9a000adbb546d99: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash a9a1dac66ff7c8ec3d4b27b434ff70fbde5df3ef3dcd4b4fe4b41bb80f78a7c7
The earliest published head that covers this entry
- tree_
size - 2373
- signed at
- 6 Oct 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 1e267d0ac014ebb6f08aba71abcf460d744c241ab259158739e916a593073e40- signature
w3U98KukWjpxj3sVqAEAhmq66KyXRLY40x5IbgesFoNTvH+cOn3pKu7jhBvkblFCGPKeSzJxomTsYKLM7k5kAQ==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10