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 - 620
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id f69e4ff3-bcaa-42f5-a8f1-8044a9975b0f- logged_
at 2026-08-22T05:30:43.421288+00:00- previous_
hash a860edd0261a996fb7a2f90cf79a39fc832826d005d07c0d71ad42d1505256b2- payload_
hash 206c7ec65dfb7a5b11c2180a5c367fa18f11be645fc23c7923d38786e8fca76d- entry_
hash 9efcfcc45a7411993605ec99eb88b84561116eb80db4efd60b3aab13fd013351
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.417533Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "f69e4ff3-bcaa-42f5-a8f1-8044a9975b0f",
"series_commitment": "7cca593188ee2b091161bf07402cbb54ed566e108dcfb0d19dcae28165f49446",
"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
32b9a79c90f8d11d50d8cf778bc537bd892255dd6c1f8ee12d00442cc9bb08c0- 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 - 620
- tree_
size - 2479
- leaf_
hash 4eae53a3b1f9def803c6d6e9d21c818bc1fb5015185602e18ad0e94f8a9beb07- audit_
path (12) 0: 75c03d7fcddc020c8d1fd43cb4ae758992115247f11a730bd08f170f8a3522741: c69a42266c1508a1ce24095a4c71d510913d437fd5b3fdb23b46b2237bd0d36e2: dd8d096cb4d4d256d78a8c25e46b714638c0d2706b0b949dedcdbc9790b6f5ed3: 11ec8a168146223f72f7730997aecac14fea9824bd7fa862b1dcc70af4d897014: e2debe6d7d7fd096a8bf17987c2a8dc42b7d75f28f604d60ceaa72f01206288e5: 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