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 - 1293
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 4bfc7aa0-f12f-479c-ba06-d8e4cebfe625- logged_
at 2026-09-02T05:32:20.881733+00:00- previous_
hash e706eba019d6fad89b52817a2030f3f75e82c038d41bba057cf8b55b7958bdcf- payload_
hash ebc28ab15e422e153a29e7b864b1d5e59e29e45eb6cde192f3c81a95df30cb40- entry_
hash f23ad0156f19d4209881295fdfdab9b4796b04b82742e45f39715e771491345d
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.879306Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "4bfc7aa0-f12f-479c-ba06-d8e4cebfe625",
"series_commitment": "be40280b700172d5701e81d15845704368e40edacc5cf07c45145453fbc6da27",
"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
ef74dc4c054a361b09b8278580df071a2eaf7e20c6f7b04848975e8afcbb1401- 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 - 1293
- tree_
size - 2527
- leaf_
hash ad9027676559a4ee208db8086e106686ac942a715a59f9f3335ff96e1386d477- audit_
path (12) 0: db6a05e5e537d180943980d4d4bb0df3dbfb03b4c2ec407476a7251cf644d1451: bb3491f708373cd9dc635c32171d5540f59659d103a450a6a6908c5f47c3df2f2: 294a805d6fa89c92c257e1b881918c4eb4473904d198e51ad35880e97176dae93: 595b2fc835f327f57ed8373d99169f59746d5a4224184477d33f3e0921e83d2a4: 3bab3dfacdb4663eededa2dd912fa671e084bbce8b9478f98ff785f76bc67f205: 338aa13e9ab3bf9fc959251d8ac5778963ee124660725c2266d53394765b5c306: 1856e988c0ca2de1232e3499545b496b7d991e639165b9289a3c3dc3f273d8d47: 00aa16d00eabe2b61089fea4a6c3044cf3b1ced9f2af168276f93e239a98dae48: 73b80563a47162cfa99809097caf5d77512af3a28ebfbf76c6bcfd5f572cc1d29: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 6a1689c7a18dd6e26bb5ba9aa9beb34e33c31941a6b6f9809c8c7ed6c8391a49- root_
hash ec978d5c7cdf86c1addae478d489dfb54061a2da37f75e4557895152c63d6c38
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