delphi.consensus.snapshot
Appended 13 Sept 2026, 05:30 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 - 1771
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id e732630b-b551-4965-92e6-7168c5a86d89- logged_
at 2026-09-13T05:30:21.170536+00:00- previous_
hash 65e19732cc1ad163edce385e7b1e4f5f9f05885036731ba36eb8239bb66a0176- payload_
hash 3f5fbe011d93c6c49b0d6ee2f63765afeddafbe68035a33d03cc50c821d286b2- entry_
hash e2fc0ee6c691083114cc09d8b2fd4869cb1d7ed4182cec0ea50fabe42aaedd6c
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-13T05:30:21.165593Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "e732630b-b551-4965-92e6-7168c5a86d89",
"series_commitment": "22fdcf847f56e848888fe01cf7d801ae77d51290ee573737457ee791954ecfa5",
"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
c94bbc77d6f99d62ef5b51d59b03b3b61307b7bc36bae4915a59748dabbf53a7- 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 - 1771
- tree_
size - 2239
- leaf_
hash 1265c51ea4eeb7828547f4560812f52b7b354aba4696914b6ce2af8d3899f095- audit_
path (12) 0: ad0f536ad12406bc4b2b92455ebb24808e576b474c865c7050a5b2ec18344c171: 4a9b156035d74a0c7b949fb7b84fc42b3416ccb0a7196c6fa54144097fa4ef772: 7a220fe06d4b39024aeda703d5cc6a5d6538b76d98c658d3d05be705ac63a63a3: 909264ce169f7a31297b0098d13ff7dc8209ecaf7322213333808c597bea1e454: 8dccf6452412545d0382c1657c04f550b9bdf1f17c23d727a4d4e20563f4ee885: 7c39a4f934fb08cf020dfdb7c75e05a6c26a5cf87ca7a597c9e13a2bf1ac01d06: ac160a0852932e7e1298c12b7bbeac8a979011b4c86d850294a53e9c58329b547: 89bbeb672caa03ccca78c3e7d709e14d72ed0f279c7cfcd435bb71dc863239c68: 49fbc719d10777c21e02e255a1174dbc47e89c67c7b327c5f50e8ea1ffbb5bad9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 9203a1600de814d3afb819f841569332c7e3b58c4d0e0ea56c377729f25dca49- root_
hash 03dd6fb33b4bd65222257eec0069956926795f14f7354795bcb42af5fe51ba08
The earliest published head that covers this entry
- tree_
size - 1789
- signed at
- 13 Sept 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 388bd49a3665992db6aa3f5411da8d94094d9533bfcf03670f67990f1da0e869- signature
8BPUlbqNylu7KfsdIH4L+HYq1scSh5gT52wCY1X+qoObVNaDebiStxXGB+z/dDutmyNLBN4KR4ifXuZtakrSBA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12