delphi.consensus.snapshot
Appended 9 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 - 1606
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 1b1a20a9-2af9-4c58-972e-a6628e241b09- logged_
at 2026-09-09T05:31:39.896552+00:00- previous_
hash d8089c49274117afed1b84313f90899853811835628f5e0276db04e23247a708- payload_
hash 896d1da5781ecf959767d1d6e4a89e77f9e6b3092f49c1a858954007ab721750- entry_
hash 2c34648a6ea257e652508114caa37bbddedc9bf12ecc3eb40c0bbe468ad8fafa
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-09T05:31:39.889869Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "1b1a20a9-2af9-4c58-972e-a6628e241b09",
"series_commitment": "914b40b437ad361ea964d94b9be239874b3abcf761543d83eca9e616838e03d0",
"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
b8d8a0404874019e9d29cecfd3d6a9953c4af778c9986c623b3c5ca85b8a40b4- 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 - 1606
- tree_
size - 2265
- leaf_
hash 6745d904a1c9589af6ab90c36cbf201539f17ef32e66a948f8ff4c3b8e344ee5- audit_
path (12) 0: 2efc90c53c1fb51db6fd00ae202f147bf164ce915c690c9280011c6350e706471: 2172459862b5f7c17b6ef1ae03844854a78ace9ef630fb3974c4eab4564f02a62: 55f072ea7d07ead694311cfba0b616bac9895e5dc7be846ac4334fad944576ee3: a41ce8a5a24af0cf3be319d271361d492995dd020cfcaf174af009d34b3936914: ce8813d73788a5a7ccef44404a8ca9577f9ff9897e64be3657e55edeb54438365: b1b6fae7089c27926a3b967b88f7de369c00e69d47160c303e67fd8ad3c0702c6: 00d36260786b8ce290bee853db49e73fdd5d2800eb992fa1e6e2b98e2e9d62487: f4a858c5afd6d2bbfe79825cc00005d2e5bc4cb6a3723b70509ff06cb4f713008: 49fbc719d10777c21e02e255a1174dbc47e89c67c7b327c5f50e8ea1ffbb5bad9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 15428b80842f9a0801cf7667918b216c9ce4186d9825e806ba86972b039c03f9- root_
hash 0feab2262fa1e39174e25fc17ea9383a6fe15fa5d22c96afd722849e59baa3f5
The earliest published head that covers this entry
- tree_
size - 1627
- signed at
- 9 Sept 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash ece15eb8383aee9bbf3f3bec9ccc72d87819c3947b61ecb8093ec13082289977- signature
9dr5EA8ZzKRK0L5i3/Zn8Rt3+PevClFJSGpb1IzYaNtVr+QKTJT2R+Qd9oJ77HQMV4y5WBTzci9qRcxNN4MqAg==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12