delphi.consensus.snapshot
Appended 22 Aug 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 - 625
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id a8c36f16-c0df-49f5-92d5-29bb1d0e58a9- logged_
at 2026-08-22T05:30:43.454043+00:00- previous_
hash bafa9c1fa628798d1b3241469d7fd42fe74cb8ea3a92e39bcf4df940f89c3348- payload_
hash c90dae8cdcb249a8740ae79e668258f6d4e82ce06af263fb53b88e94b0a3d345- entry_
hash 6b4800b20640674068256e9a393518fc63b12e6ce824bdcaa051ce0b3fcfb08b
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-22T05:30:43.451763Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
"series_commitment": "b7d0533d4c59efaa40c79699584d6a2d0419c161a4dfdae7df426ad9744a3b7f",
"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
766a65929340a51742a517125d3410b457fc2fcd226076161d26ba4b346ba22f- 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 - 625
- tree_
size - 2479
- leaf_
hash adf9cc0b0e6bcfbb4684c4e3f59232c4e783147e01960f07acd3f5b0d7eb9273- audit_
path (12) 0: 3561d28b3f7c2dad4f178c08650b5c3ff10e4169c6cad57d2efd00d45a07f8681: 9b978b410789ecc1c0f99ce772bc7eb257416ce60da9a4012fb31ffd86db17502: 501ad93bbff2c431dcdb0b3c4eac12c626c6d2aca4a9d160cbb334a3d92d67dd3: 1e90202013cd4ba911d6b776f4de183044606eb3a26393aa4ad2f09eae1075c44: 79f52eed3d7f51523ee9eb5e7d46f4fbc24caa70310067e93fdd590c4564f6ab5: 8e09b5435c61fc5db386222d33e408d9ede3016d96fe04fdc56ece82963f11636: 66d783f1a4106ac8ea73f0464db5328d95910b9613d356ca7a4d7238d180ef957: ca7fb7b440d51df69e12966994a041553b2c0acd85e1779b8e2fe8f79a1a4ab98: 1ed805746441fabcaa9e107f622f886b1692796b8a67f3eaf5f2122c01401d239: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: 8d949d6aef53b2e3322ef5e232755263eaea63b886b405d936c87ac0c842b6a1- root_
hash 2135d33fc3b42de9408df8505e145fcd175142e943af391ea41c56bc99a1e5e2
The earliest published head that covers this entry
- tree_
size - 632
- signed at
- 22 Aug 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash ee7d3fc82f5aaff8097c262dfec5f324866dcd66ff2f57c5f03959246ce30e44- signature
5xMqhp5mkjyNaCZDqNNz8sCOKCPVWpN6XP3+g1675vS1ryFscLkuSpbpJpoeP1G64a52gFmsNs2Hi0lgRWDDDA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12