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 - 1340
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3b91df80-00fc-4a4b-b86e-3310edcb9332- logged_
at 2026-09-03T05:31:20.955945+00:00- previous_
hash b8ef88c92d44e20743217354998753f5cde78b593c06a477d33a6fc1d51339a4- payload_
hash 9ebf5a30fd20e6af54fbe427e3f21ef0066d6cfc9f12236131a88a3ad25c4b19- entry_
hash 2a2ad59811b12965f2ba16bceb104f9f688e0f18e02564a0f02cd8d4a3806270
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.952870Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3b91df80-00fc-4a4b-b86e-3310edcb9332",
"series_commitment": "f89face9c9925faa66fdad2edfc2a4aec1c4511faee8c88261c99b7242a695f9",
"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
e115cfe37fe29989a2a8a4fd6135b179bde4e98b702cdf9ded2c147ed1189430- 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 - 1340
- tree_
size - 2357
- leaf_
hash ded7c24113a4babbd2f2718b424db4637faa0c764f68f2d8fde6cb10318be98f- audit_
path (12) 0: d1aca2c98fd4f39c4e25b529103a3d482cc7cb7b2b055383044980954aa985331: 3b12468c687c3797139b5526972db9d92e28febf499bf0c931184756141f40272: 368b76e05e3f8451990710dbf96f9f0c741fa929cde25a895d7c79ef874713a13: b37f63b20e8eb322307cfa432b489c4f83165faf9a7864d61a79b8e8016c3eda4: 2918c2aeb1134879bae40b295e56941c654043e35aeceab2d852a6af12421b575: b36c7c4e17776a5c001456b78736a38b0060838a2c1cca456f37637a9e1267416: 1856e988c0ca2de1232e3499545b496b7d991e639165b9289a3c3dc3f273d8d47: 00aa16d00eabe2b61089fea4a6c3044cf3b1ced9f2af168276f93e239a98dae48: 73b80563a47162cfa99809097caf5d77512af3a28ebfbf76c6bcfd5f572cc1d29: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 2f361a0c4a49843181536f3a7baa572ba4bc0573be4bb8272112c3d056aa1031- root_
hash 58c8c5ab99dba36e8c6b398578e37592253a716c9cf756f72e78b6606a198d59
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