delphi.consensus.snapshot
Appended 2 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 - 1283
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id e732630b-b551-4965-92e6-7168c5a86d89- logged_
at 2026-09-02T05:32:20.798707+00:00- previous_
hash 30f773978f96bccd728de6d14e3cd71885bff49b658f00a03d6bb205ebd04832- payload_
hash 147ccd1fd04637593bb5115b942ce0d9de6b0d25a519be098ffab923ff77cbdf- entry_
hash ad6396336fa71620b68e55c463d515a27fc269e176c5162d470423308159e2a4
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-02T05:32:20.794906Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "e732630b-b551-4965-92e6-7168c5a86d89",
"series_commitment": "f69e0c5a76768c3d2e8184d4dc6b8edcba06b27c09d67406c8c71b5e910ddf3b",
"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
af70259b169174a2742aa20138c77e955e43593aace7d77287694654b6e9c752- 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 - 1283
- tree_
size - 2265
- leaf_
hash 00c189f291248f5bd6c914857f2b3a9d9aa9614f7a8c65a36d99b90982da4527- audit_
path (12) 0: 44756213244be81b693844d3003ed767d379e0f45055c42f7591fed56912f2301: 78bbfc8d5b5b7df8e1766e044331da563129dcbd6a0f185260e167ac6390cfd22: f346be8902fc52b8bd3e523088574f4fc1df67e6d5a1165f7d0fd00c1385d31b3: ae4b9b092482ed9232c486acb17a965d99b37a1615b436d45be7c16ff749dc9a4: 3bab3dfacdb4663eededa2dd912fa671e084bbce8b9478f98ff785f76bc67f205: 338aa13e9ab3bf9fc959251d8ac5778963ee124660725c2266d53394765b5c306: 1856e988c0ca2de1232e3499545b496b7d991e639165b9289a3c3dc3f273d8d47: 00aa16d00eabe2b61089fea4a6c3044cf3b1ced9f2af168276f93e239a98dae48: 73b80563a47162cfa99809097caf5d77512af3a28ebfbf76c6bcfd5f572cc1d29: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 15428b80842f9a0801cf7667918b216c9ce4186d9825e806ba86972b039c03f9- root_
hash 0feab2262fa1e39174e25fc17ea9383a6fe15fa5d22c96afd722849e59baa3f5
The earliest published head that covers this entry
- tree_
size - 1301
- signed at
- 2 Sept 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 7412c3bb0fe0de978d577bfb7d7e6c78c4415aac29193a116b150bd1dc28f398- signature
NpyT4m8rheEfWbFdEQNnccQG0Zzl3KXO1wHnZx7zD3lNnn81UHz/zavu3VUhzj72XmrSmaJLQKo1iyyww27pAw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12