delphi.consensus.snapshot
Appended 13 Sept 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 - 1774
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id d1b83331-68f7-4be7-a625-f7824bccab5b- logged_
at 2026-09-13T05:30:21.199514+00:00- previous_
hash 93bee52495b43fe5e552a8f61ebeeafb6ccf0d55a01011017729e49fd320061e- payload_
hash 8386bf4de1d619ec299dcfd4e599f074f6b5cf20453d7ba10e25325ee1673854- entry_
hash 6f1b5f2da1af6a0cb3f98307a27c64abe500fe2543bfb0755afa8f486e8fc008
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-13T05:30:21.195925Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "d1b83331-68f7-4be7-a625-f7824bccab5b",
"series_commitment": "77b6e13fd01898b6717a8dc05e1ad8afe31e42e74666ce0db666deaeb497573e",
"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
142c8d1473714c774e08269623c17427d76b0f1af87f7ba5e61e0282067e7e9b- 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 - 1774
- tree_
size - 2239
- leaf_
hash 96fefceb5ad829f04e13267f8aa3e18ae8c41e8e60be455c856fd0de33f60493- audit_
path (12) 0: 510ef3115744bae985d2cc5ffcf99de91623b73237ae1503888e372c5afb0fd71: c52fa7f9abd8cac1b98c913c4710c72d2340eb0dbc8723385ffcd7757fab5b372: f327b53fbd7913c1c72fbe964a49c7076b4ea38a3cc32346015941a11105e6fb3: 909264ce169f7a31297b0098d13ff7dc8209ecaf7322213333808c597bea1e454: 8dccf6452412545d0382c1657c04f550b9bdf1f17c23d727a4d4e20563f4ee885: 7c39a4f934fb08cf020dfdb7c75e05a6c26a5cf87ca7a597c9e13a2bf1ac01d06: ac160a0852932e7e1298c12b7bbeac8a979011b4c86d850294a53e9c58329b547: 89bbeb672caa03ccca78c3e7d709e14d72ed0f279c7cfcd435bb71dc863239c68: 49fbc719d10777c21e02e255a1174dbc47e89c67c7b327c5f50e8ea1ffbb5bad9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 9203a1600de814d3afb819f841569332c7e3b58c4d0e0ea56c377729f25dca49- root_
hash 03dd6fb33b4bd65222257eec0069956926795f14f7354795bcb42af5fe51ba08
The earliest published head that covers this entry
- tree_
size - 1789
- signed at
- 13 Sept 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 388bd49a3665992db6aa3f5411da8d94094d9533bfcf03670f67990f1da0e869- signature
8BPUlbqNylu7KfsdIH4L+HYq1scSh5gT52wCY1X+qoObVNaDebiStxXGB+z/dDutmyNLBN4KR4ifXuZtakrSBA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12