delphi.consensus.snapshot
Appended 3 Sept 2026, 05:31 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 - 1334
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id d1b83331-68f7-4be7-a625-f7824bccab5b- logged_
at 2026-09-03T05:31:20.917270+00:00- previous_
hash 7f15e621fcc799bb21a4ba3267f3069c7f2aa8ea65e04281f4449e53c3b0509c- payload_
hash 4b48cf5c5310212d90d8874867a77d1c84f7c1280812fb33e2c88038b0efc707- entry_
hash bf20785a61f3a145d6846a17e848bf4eac967171fffa2786f6085537283b54b7
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-03T05:31:20.914791Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "d1b83331-68f7-4be7-a625-f7824bccab5b",
"series_commitment": "c636dad2d1aa0cd4d56d9b4d2e92f7d4a484ac72a801f87f0247bb6384923535",
"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
5e881c62dde2ce1660e2c8d32b90f8acaa6645f6e7776efa263458105103d962- 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 - 1334
- tree_
size - 2357
- leaf_
hash 0655958be6bf8485a2fdd7bd6a4c505980feae9727c82cd1fc034070b108fddd- audit_
path (12) 0: 83b7751c18e1cb6314a2741d563ea3fa1069595a0b8c8b2a17509cdac6159e181: efe6d17880ca12c926b3975ce954a06bb27c882c998f83e467f97ab0fb782c202: 9a63670a285cab92b06c5aa6d5290cb20e42dda345403c951c91781c274f71433: dfbe1af2d4d370a02df80cf16ad32518b6b20d84466dc8b341d3fac9f970d08d4: 2918c2aeb1134879bae40b295e56941c654043e35aeceab2d852a6af12421b575: b36c7c4e17776a5c001456b78736a38b0060838a2c1cca456f37637a9e1267416: 1856e988c0ca2de1232e3499545b496b7d991e639165b9289a3c3dc3f273d8d47: 00aa16d00eabe2b61089fea4a6c3044cf3b1ced9f2af168276f93e239a98dae48: 73b80563a47162cfa99809097caf5d77512af3a28ebfbf76c6bcfd5f572cc1d29: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 2f361a0c4a49843181536f3a7baa572ba4bc0573be4bb8272112c3d056aa1031- root_
hash 58c8c5ab99dba36e8c6b398578e37592253a716c9cf756f72e78b6606a198d59
The earliest published head that covers this entry
- tree_
size - 1349
- signed at
- 3 Sept 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 7f923b9e276353e56131136c5f2d8734810b3ae593a7802c5ab7323e72ba7b33- signature
cFBBIpZO7O16ciWU8zV0mJX+pH5fdC2cAi7r1uTf6xLxXWweGyK8nkOKKpKkMiQp66DEILlOvMRMH3A5aU6FAw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12