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 - 1519
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 05901165-61de-4a02-b759-02a9bf89ef70- logged_
at 2026-09-07T05:32:20.469565+00:00- previous_
hash 8f9ea4468e32533069900ead0adaf299fa2ceb6dffdb52f340f317a31e7074e2- payload_
hash 5b5a3eda4456f8ff460efa1b8310d2cf174e06c58dcde4d306563656880e0881- entry_
hash 8f340b657e63be7a2ef9ae6ea319f9ff89ce3a626ee3f6581b94079f4a773ea2
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.465708Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "05901165-61de-4a02-b759-02a9bf89ef70",
"series_commitment": "ce64ecf825674a2ae6ee0af18aff4a5d08e90e0820538b81d35c1a6772f99dbe",
"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
8480b7678b1602a19955a3146d63678b6da209def8c09e1dbc2fc059b6717e5e- 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 - 1519
- tree_
size - 2285
- leaf_
hash 1af9753bee05b72e5456dab9c70cacb74b878a6b32040f18b262e3e4cc919170- audit_
path (12) 0: 3acb19453feb6058596bea9fc289d9fa1f9b47958e79476611fac0fb5d923d801: 2055ca82b7278bca81543a7a7ec9eb480d61865d62b38e19ebfe38203a3be0ee2: 6a424c4d3bf25c045cabb4ec4faed92a7eb1f02a6330b470aef2869fb779b9db3: 1dbd675448dc84edc9ad7f1b007fbfe61898594ab192a12cb258835692bbc3e64: 2865852750e0901757d4fa42b4a15129fe3a234b931d0736a755862f8d7e79ce5: 116fe9e1fce946c94a088265bf94d7539ae1b7eb30ec656da7e96abcaee8da4a6: 35aca0f2b9f8c478040e38216ad4f2e9efa65fae1c6fc41a8df2a826f260686c7: 59548e903d1441fb0d6e6d441d39382bb2fbf2f915e94e4c49c6bda187d8c1278: 73b80563a47162cfa99809097caf5d77512af3a28ebfbf76c6bcfd5f572cc1d29: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: a95d574e00e9fefbc454b084e8cb19edc83831071366b2d8dc1af2f7114b646f- root_
hash 17330c6327e6363b8237bd4a68d5ee420a6d0f745c8d8bab0a90305d6bccba50
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