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 - 1782
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id a8c36f16-c0df-49f5-92d5-29bb1d0e58a9- logged_
at 2026-09-13T05:30:21.279486+00:00- previous_
hash 202a5c34158a498eab05cb5a5972588616f18504beedc4c379ecf1a54fccadf2- payload_
hash b0190eb6998417e6a78043878b669e22cd8772f1460dc66896489e4ca86ec4f2- entry_
hash 1340df29ce4fb4674e6f8b2f2884e461a7a712bfdd206f2aa6fed342cc7281fa
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.275681Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
"series_commitment": "81676b83b3a4cd3c05173f8d376c1f8c40f21537cf236672826d07367340d8e5",
"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
a04a18fdd0ac99097d9d63ddef5c975ea88e9adae9e4b3968c7d9b2d8dc3a1aa- 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 - 1782
- tree_
size - 2479
- leaf_
hash fbfef12b350cdbb3062de436a8041e0ed2f9e36bc22bcea54f45ceb261f54e52- audit_
path (12) 0: 658a076a05e5ba59ecd2c9df0f0926df5d4a99da83c20f2f88a7fc3f96de736c1: 0b93f8de9f4689b92c37328d51667e84f1aa4297a11b0312aa2704563c4357d22: f58a72c500d15cd4c8e68167594c7e120beb03d40feaa1a764497c83b40c791f3: cfab60c51d6edf6987a1f03315964f6fc6b5846075bd0d5396fb1002c6fba2884: fe124cdd35b82fe60b1e2f908bbced3897a465f5c7a90e177b12019fd4547f815: 7c39a4f934fb08cf020dfdb7c75e05a6c26a5cf87ca7a597c9e13a2bf1ac01d06: ac160a0852932e7e1298c12b7bbeac8a979011b4c86d850294a53e9c58329b547: 89bbeb672caa03ccca78c3e7d709e14d72ed0f279c7cfcd435bb71dc863239c68: 49fbc719d10777c21e02e255a1174dbc47e89c67c7b327c5f50e8ea1ffbb5bad9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 8d949d6aef53b2e3322ef5e232755263eaea63b886b405d936c87ac0c842b6a1- root_
hash 2135d33fc3b42de9408df8505e145fcd175142e943af391ea41c56bc99a1e5e2
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