delphi.consensus.snapshot
Appended 30 Aug 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 - 1121
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3b1bf8d0-fa87-4392-b4cf-333e6cba3622- logged_
at 2026-08-30T05:30:41.157148+00:00- previous_
hash 94b07d372860c2f34f27530428c8e6d392bad2f19ad7fda20799442191c40424- payload_
hash 6b0e936ac05ffe8cf866ab001b261ae68740078c1685e435b22a45d0db599215- entry_
hash f134ce96630d8df00b31ca64fe745890bb14d4440c753eff92473df2c4fcf1fa
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-30T05:30:41.150732Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3b1bf8d0-fa87-4392-b4cf-333e6cba3622",
"series_commitment": "7176a26e2ec8b89df500fb8a01c14f7ce020cce5271cfd643d976eee838b823c",
"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
addba22586c92f8257d9764086dd9bbf165046f8e4519a765883dc1688e95924- 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 - 1121
- tree_
size - 2341
- leaf_
hash 80eddbe28d4ae6eadedb8844fc379525150a3270000b56c95c52853cce0edbbc- audit_
path (12) 0: 0ed3ab1d93da01b2e3f81b23dee3a77398c1d3265b9be8cff2e7da651da6c54b1: df8bef7a01a7108e652747b922e3fca71e1031119b566d3fe9eb06ae617045fd2: bb27e575a358a98541a1593c2b04f75443b773fc572e630c1d6f22a5411a37e73: a735ed70c9ee8bfac4793f187b84951baae8dcc85b6c12e8083efd1df93a10454: e4f0fb45f69e62faf8920f9f4026c1fea765f2a12d5baff8498c2bbb19a0f40b5: efa01dd0286ff83e9fd1c8442b397ce07b4cd15d103de784ae87eb507a2715bc6: 3330710dd5fef91aa0e763e3b3c0b21b7b27e549cf2bfbc05fee8e8bfb1f42b77: bbfee2f96690132143d2a2a16089df72535201b31174873b1f1a4d4c85a029a98: 6ce18fb0b650e54a2c9454c3e9abde48f8386826f5bd1752662ede2993ff557e9: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: bd18df2de60e205be411a53ea96887ec76f5a16c15250bf48e3f90dc788abbaf- root_
hash 9f32e37b52a81f4fc0f11a1b956464ef6acde09c58b0ce26dc44277199cb7df0
The earliest published head that covers this entry
- tree_
size - 1133
- signed at
- 30 Aug 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash f93488269a5aeaf9d50291920769e871ba9d361f0fb72089c9ba41c88a2727b6- signature
nnzoG8Yk362jKSvRmRO456zSfVqvhFq0AoyJZsV0jjpigKArT+n7iaJbA8sAIeqGXEUgCqPLF9MrRlQug43xAA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12