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 - 798
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 4e06eb7d-ce53-4631-86d8-403a4f841a49- logged_
at 2026-08-25T05:30:32.392032+00:00- previous_
hash 72c4f3a71c6cd0b09a3652481d28fb819f3fbfe4f54052ea241a64cc9c355c50- payload_
hash 6c54cd1163fe964dfebb341d87695bc5614489a2a689fea3bafddc10d9dfaf47- entry_
hash 6a268f83808e9aaf7a25d80abbafbaf130751d03f0d03e5036086c1ef38c8e86
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.382749Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "4e06eb7d-ce53-4631-86d8-403a4f841a49",
"series_commitment": "1ae0924d207d956ee090aba6bf6a8ce68064da32f94378facaa7b7e1f92a532f",
"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
c015bb1d1aade0b2b0f4509303d60685a522f5e70dd8c382bc4e51eca18d42ff- 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 - 798
- tree_
size - 2341
- leaf_
hash b5a2cff643f3ca3fa544489724cd5b5c91e21c9494cd0f559d397a25b5cfbfb2- audit_
path (12) 0: c9fef530e41126ba4636ada21a14797995933715065eb7ca66333de538092a051: e345ed9721bb4ba809874854590e82b770f7640e56ae6d10f30bc54ac31e8f272: 046833066b778868b814f271fb29e7db3b43cff8656e4454ea95852dee77d8c43: 5603c1e4d8035c8235f34b74336f3fca62ce26c0dd9dac6abc037cd772d242e04: d73e9883b332c7baf13de8ab066c4d19e0a9a2a0c4909a78109cea1451d6c7ee5: 532f612166859b9cf0a9f31f68894ded88b90871ba71442154cfd0185cd4a2fc6: 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