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 - 1326
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 28453d7d-6676-414d-a36b-2fcf2cf13265- logged_
at 2026-09-03T05:31:20.855977+00:00- previous_
hash eef863f9735cc75d1c57837a0d0159683ef8ea4fa9d92f272c78ad8eea4c0f1c- payload_
hash d5497f672a58106fb11bef0fc09f4b7981b143df084cc557413794eddfdebe64- entry_
hash 98fa0a669714a5f12ae9e6c38974cb88eb09b69676de2fe4e2b98d3adb42f6d8
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.851525Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "28453d7d-6676-414d-a36b-2fcf2cf13265",
"series_commitment": "8acd4c6943321655b51672dc3e727b950528dcf7d66cbed39a261685ad8f77ab",
"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
db86274a5252e8d9bff80ae6231a0aa3aac8aeb1c1813c647483163241e621dd- 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 - 1326
- tree_
size - 2323
- leaf_
hash 49fae8f72b49a2713403630275d65da862d17bd1db85951aa9c81dc27a29d987- audit_
path (12) 0: b8bae3443d8cfff5c1b9b8d7669bb0f5ca9f7a1359a85fdec6c6d093f56dff211: 22c27e03eb490fcb283beb6b2ff97028df925b936dcdc6cbbb560d54d7e24b322: 79bb58846e9b33b58f856ebedc5d835066ef25c585343a104b19ad10b07026f63: 5fad69bc3401f92af6eb08690b4fb9ce7b9a5d51db37073f7e55ab48a94ea38e4: af948a3fbeeb54e6cbb4b8beb772b67b6a70af82164a0f96993aa165100a9a7d5: b36c7c4e17776a5c001456b78736a38b0060838a2c1cca456f37637a9e1267416: 1856e988c0ca2de1232e3499545b496b7d991e639165b9289a3c3dc3f273d8d47: 00aa16d00eabe2b61089fea4a6c3044cf3b1ced9f2af168276f93e239a98dae48: 73b80563a47162cfa99809097caf5d77512af3a28ebfbf76c6bcfd5f572cc1d29: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: c3259a319fb9b811eedac153ce91727bb54f7b550d8cceab957b75c3a0564058- root_
hash d5cdf3ada5e9d6ff6f86cc94c6a7cd9965df1cd86b6e68dd8030daf1fd3631be
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