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 - 1122
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id cd22f6a9-1eb7-4927-a2e9-6736a77b75cc- logged_
at 2026-08-30T05:30:41.165611+00:00- previous_
hash f134ce96630d8df00b31ca64fe745890bb14d4440c753eff92473df2c4fcf1fa- payload_
hash 26cfd0f865f7599bd655d372e2d332f86162e078f14aa71ae098914487897d90- entry_
hash e0819afb3cc4d6ea17e5fdb5efee46b90bbea8c5434f4490c13758c2fb57733c
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.162903Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "cd22f6a9-1eb7-4927-a2e9-6736a77b75cc",
"series_commitment": "03ee15ac3c509a2eeab61e41c862205ba6adda2c2744a0a4a522f04dfa648349",
"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
34c72c68dec4e37c7a4074feb8c9fff232e30fe2111eb8d668af8446f50f003b- 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 - 1122
- tree_
size - 2341
- leaf_
hash 2be76b9ceaebc30fcfde32265bb5267f36cda952f0b4e1b7509213707660cfc0- audit_
path (12) 0: 3e367d7a97d8dc8cab5f855049edbc3bf9be4abe4a63b91d74d34afb3c95d02d1: c12ffdb03ccb3f68da14a1d147e73a5e5f1c07278fa4f7f7a8d272153408f3a22: 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