delphi.consensus.snapshot
Appended 5 Sept 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 - 1438
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id a8c36f16-c0df-49f5-92d5-29bb1d0e58a9- logged_
at 2026-09-05T05:30:42.143148+00:00- previous_
hash e4237297ceaba2cbabcbb0a486d11b31ae718cc7b929c76dc9484e5786b68141- payload_
hash d651e72f38c4dd1ea18c087ceda21dc7516d7b626d315eb19a5adae5e4604953- entry_
hash d7353b1f2ec21f25eb4937c6b2b8aa9998b19b7ae9204592c7d3f68350ecb1ed
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-05T05:30:42.140634Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
"series_commitment": "494e3dd7556602481c6aab752c0fe5973308e62bf5cecdde6d3e99aa8f14dd8c",
"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
ca6f050ec9267531f829e972c1df2bf426f6e5c3edd7a529660b6be5e9771f00- 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 - 1438
- tree_
size - 2491
- leaf_
hash 7e5984085ba9b2a747dffafba6eb2f2b942474ce7371a8c74a61c9ee534a1cc4- audit_
path (12) 0: 08a212eeeacdf7668b8e4da8030ae6e3faeb78ca4bb0860e3a4c07481e72ec901: 2889f33b89860745d075da6b591d3b3f7e8d3172f776b03f89fa853722beb9682: 6bd7f54dc2ba61bc3cf250f40ea39e6cbc4d15b63e002621574abf25188745883: 564edf0d636b2ed19b71651eecb09aae7f9bedda413c151d2bf06ab39ce788c34: eb2ad53469a5278129837bf3faf26af1991b9ed24b7535827c85adb2a6fdf4295: 2d7f0151c1724ba0ea8bf06d726643f0f6893ec7bb868e6681848be8fd368c056: ef252f031089471cd75411471a0532012f4deaced96acde8a10c0024e7faaa357: 59548e903d1441fb0d6e6d441d39382bb2fbf2f915e94e4c49c6bda187d8c1278: 73b80563a47162cfa99809097caf5d77512af3a28ebfbf76c6bcfd5f572cc1d29: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 083d0806ed3c3d656f2d8c4762013d3fb4c0ed984cb03e95e8ae46936f2431df- root_
hash a9a1dac66ff7c8ec3d4b27b434ff70fbde5df3ef3dcd4b4fe4b41bb80f78a7c7
The earliest published head that covers this entry
- tree_
size - 1445
- signed at
- 5 Sept 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 14935c0bde678e80dc3a37641650904de8988691c769149c38b10d54518ed6da- signature
oBabtEvQC4ypaFdP+K4eO6SkxwE6AoHWZOprH3l6t63fcsSRixVw214MPbkS6PXBnFsTXA0rFPKABtwhipFLCA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12