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 - 813
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 24c5a768-70af-4997-afe5-05e9edc2e4a7- logged_
at 2026-08-25T05:30:32.521365+00:00- previous_
hash 06d0a2c75ae4deb89fa0ea482ba4b9f95227357c5c64314aa5af6d6a58ae3236- payload_
hash ce0da814ff38b91ee55661c41a7ab5bd679d62f537fb7426f4a2da38be629baf- entry_
hash 7b28799ac5b5a6ae36acb71a5d3fd401a9dcaeda1c1ec1fcccd0681a43d718cb
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.519142Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "24c5a768-70af-4997-afe5-05e9edc2e4a7",
"series_commitment": "26422a2d142853c1deba409a16ba67811a588dccf89ac3270ab7684bcfa37806",
"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
b98334a7a7eacc5ffef882b1b1680841c816c34edfe54b0ef612fdb0fa250188- 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 - 813
- tree_
size - 2341
- leaf_
hash 24def4d10e8863986157961b87efaa4edb5e12872852a5d456a4daa2772ae356- audit_
path (12) 0: 7b7ebccb2d3e799a90d1b4bf0da861fe6ec5332f0669c6511613380c698870dc1: 780dbec0e00f6af72fb2ab69bb6e89a39624cdcffa891f8f81eb37ef19603de42: 271b3c72006724224f4d547dfb8bd9d3a43f89d418ec737d8ef10737f7540bbd3: 440da531d4ed7a82b9f3a7e9abe5ee00d256a395fd1de98fb8e493436c2cef564: e6504495f678413fa3a87a90cefb204f1530ef75a986eb88378995f192b6ccb15: 8b9f3a56401822e1e4af04086c31b37e1a9eecead0bcd104e08f30953092e6426: c715192dae6aca65ceed9c8b6f8df435b8f926e7881a91f9813cc86bda106cd87: bc6ace31149b3e9c1ba9d5f2b34ffb85a63422d9dcf2ebf241b2cac10329bca88: 184a24c3b623669a5fc418f1a01a448ab12c5b650e771370beaf16f761dd2e6c9: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: bd18df2de60e205be411a53ea96887ec76f5a16c15250bf48e3f90dc788abbaf- root_
hash 9f32e37b52a81f4fc0f11a1b956464ef6acde09c58b0ce26dc44277199cb7df0
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