delphi.consensus.snapshot
Appended 7 Sept 2026, 05:32 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 - 1532
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id a8c36f16-c0df-49f5-92d5-29bb1d0e58a9- logged_
at 2026-09-07T05:32:20.570729+00:00- previous_
hash 89becfeb69fa7b1308d7b28ac5ece198d379344051a34e523152b843bec53fbd- payload_
hash d42c3260e0e84524a03d1f25902cd7d90974c809a6034870de803380b61e81da- entry_
hash cf2eef4b074e1de94f41c1ec561a6e28c29c6b5499e15616a6648ddc590f0b6e
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-07T05:32:20.568149Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
"series_commitment": "917270d4c544066b6d838776b5892beea11f0c328f571e81876c130d29745c06",
"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
28cce0bd0eabe2dcd58441af811e5775a4c9ee4e7d1897be0d307b2837655e42- 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 - 1532
- tree_
size - 2491
- leaf_
hash 11890327d81b89c1a336bb37f4c97d5c19ecb571cc0e2f409af5d7a158192277- audit_
path (12) 0: b5ee754ba7695910ff40a77b6ef384fb1fa73866de58c65ab57b0877340b46ef1: ea6b8a0f48cae9dff67af5568b12695092289ed0b746df73938c0f4cefd244d82: cb3a8fcae51ba35746fef7a270ee5fdc881813517f142f80bbf61b4a81c3ea113: 47596b27cfaf1cc2f281f8a836e91b1b7cf9b9aa9fb1243ce9fe1d65663915db4: 186fd3378c18fea8fb6da7f0fdb301f4b90c8983dfa5aa0bb5375f2b2699bda15: 116fe9e1fce946c94a088265bf94d7539ae1b7eb30ec656da7e96abcaee8da4a6: 35aca0f2b9f8c478040e38216ad4f2e9efa65fae1c6fc41a8df2a826f260686c7: 59548e903d1441fb0d6e6d441d39382bb2fbf2f915e94e4c49c6bda187d8c1278: 73b80563a47162cfa99809097caf5d77512af3a28ebfbf76c6bcfd5f572cc1d29: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 083d0806ed3c3d656f2d8c4762013d3fb4c0ed984cb03e95e8ae46936f2431df- root_
hash a9a1dac66ff7c8ec3d4b27b434ff70fbde5df3ef3dcd4b4fe4b41bb80f78a7c7
The earliest published head that covers this entry
- tree_
size - 1539
- signed at
- 7 Sept 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 5f62430a970697dbff207fbbc55e8c2e5cef33d00f3440f0eb91ce69905c40a4- signature
Cp1jg9rr3x9GvHY4Gcbb4Ye3N4dXZIRAhxuuWkgecXc4Q/yKfKaNU1B/1nlLfseihdJ4SzKVkZGsC9+w/DufDw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12