delphi.consensus.snapshot
Appended 25 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 - 818
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id cd22f6a9-1eb7-4927-a2e9-6736a77b75cc- logged_
at 2026-08-25T05:30:32.549086+00:00- previous_
hash d772dd60fee5de67fcde1912e00bdd1c2a811bf7c641912801de4c158ab22851- payload_
hash c4edcb625326cf03f410a62b14a72c5baead387a58d2196c93a4554b951c4007- entry_
hash e95c469afdb59ff6e96b3bb9c74ad3121b5713125b33961c32ef0d1386a5ecde
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-25T05:30:32.547101Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "cd22f6a9-1eb7-4927-a2e9-6736a77b75cc",
"series_commitment": "30e0d323e8925852ba33bcfae56ad49b24652dc53fd85fbdd6a16be545ced94b",
"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
c0d309bc95910b93c11a55f463d00b869de811e85b459174fa420eba20390d3b- 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 - 818
- tree_
size - 2323
- leaf_
hash 3d73c03d5aa9116acf7c83cff2e6702684ac8215330772249d5116843d48af5f- audit_
path (12) 0: dd9908bea39d7c34c6b5fc99a43d6149c65accae6fa8017d2bdf3ef2b47eb8ee1: d8f54cb36521ccbb3a4434d769f1c50ada3e3848817e66d66e293e8e921fd2ed2: a98b519ec1044fd2ac87726f0b19bfeb0cee6b100f31a1ac9678db74af5d98073: 2002545a54ab72e11254137f185da2b5a8150064e4520062045c6dde8638a8be4: 01808a46935cf5fb2d75e8b97e4131e93b5842a68e3ab0aae3998345ed0abe685: 8b9f3a56401822e1e4af04086c31b37e1a9eecead0bcd104e08f30953092e6426: c715192dae6aca65ceed9c8b6f8df435b8f926e7881a91f9813cc86bda106cd87: bc6ace31149b3e9c1ba9d5f2b34ffb85a63422d9dcf2ebf241b2cac10329bca88: 184a24c3b623669a5fc418f1a01a448ab12c5b650e771370beaf16f761dd2e6c9: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: c3259a319fb9b811eedac153ce91727bb54f7b550d8cceab957b75c3a0564058- root_
hash d5cdf3ada5e9d6ff6f86cc94c6a7cd9965df1cd86b6e68dd8030daf1fd3631be
The earliest published head that covers this entry
- tree_
size - 829
- signed at
- 25 Aug 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 54d12dac3124cabdb4202235d36c70565cfe886be49d70b227ac5a5505091895- signature
mdeQG8QhQ6dRyM1bYFxhqIK4IU3G7uoqpGdqrdWIkJxP5SKMG/wuhFxNgJXg0tqbSG6msFkc8y3L0Pyf/W6XDQ==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12