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 - 615
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id eb8beb52-14b3-4956-b29e-909a936abbc4- logged_
at 2026-08-22T05:30:43.383674+00:00- previous_
hash 3a9795869dd196bb18e930bc22e3a737bbc14e01c2052088475e351eac2d93e2- payload_
hash 12c7490c0aa172dd604496c6d9822756ce872aad40513e7178ce294251d7b0ad- entry_
hash c8a724130e81968f313cc36bc7b34c7fb2a3cec19e04783ceb1ee2efae5c0b7d
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.380969Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "eb8beb52-14b3-4956-b29e-909a936abbc4",
"series_commitment": "fdc6d39df145f0499b5334bfff2ae2c42c764bae04072b7fff6bcefdee1548eb",
"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
f23756ebc2d3b56fbee66bb6fd54fdf079aeeffe3ba7d1e471eb03cda635f447- 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 - 615
- tree_
size - 2239
- leaf_
hash 6f3942212be7456de847d4260662761aefd168b8c635358c27287b141fc54e49- audit_
path (12) 0: dfd8517cac2217231b3121ac75dc3591f07232be5f7a4b64ab7befc589deb9811: c385fd52435d4fbed16fbcac543ab7f35c120061aab8fabb2dbc6e661e77fabd2: f6699fba4350a58da30ef77b5e3f0980b6dca0f7e168d2910ea3a590113321743: 9256a86a4861c9beeaab04571981d8c00243e36a2c4dd927d34323b890e600884: e2debe6d7d7fd096a8bf17987c2a8dc42b7d75f28f604d60ceaa72f01206288e5: 8e09b5435c61fc5db386222d33e408d9ede3016d96fe04fdc56ece82963f11636: 66d783f1a4106ac8ea73f0464db5328d95910b9613d356ca7a4d7238d180ef957: ca7fb7b440d51df69e12966994a041553b2c0acd85e1779b8e2fe8f79a1a4ab98: 1ed805746441fabcaa9e107f622f886b1692796b8a67f3eaf5f2122c01401d239: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: 9203a1600de814d3afb819f841569332c7e3b58c4d0e0ea56c377729f25dca49- root_
hash 03dd6fb33b4bd65222257eec0069956926795f14f7354795bcb42af5fe51ba08
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