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 - 820
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3b91df80-00fc-4a4b-b86e-3310edcb9332- logged_
at 2026-08-25T05:30:32.560900+00:00- previous_
hash dce22ec3a7c20478ffd451021d7f01c58b3b6b613900ff1e061f18e2489c0eb5- payload_
hash 93ba9eb2fc2246458245aca7cff996b162377cbea93e968c430bbed2adfeffc4- entry_
hash 91b77a23143cc207c0b23960b38ed5a88fae39e285bc6747ec3d106b2dbe9b0b
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.558909Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3b91df80-00fc-4a4b-b86e-3310edcb9332",
"series_commitment": "c7eabad886b94ac8a4fe50363eaf3c2b14414c7abd68d547066e8ee16367d241",
"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
c45d17520b5a96a615ff4088f69fc85234114ce323971e18dc0f9a781b1fb839- 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 - 820
- tree_
size - 2515
- leaf_
hash f361165dfb0438117f160e0636d4b2e3fb4fb288c8afed46e31ea1ce758ef907- audit_
path (12) 0: 797d493d6fb080d37d243076828ed5a353ee612db34257dc1ae7961d4829e46d1: 9f8cb66ab2f255a0a699dfa74f608516b7e5123df13d73f78db07006c53432792: b409f2a6567de8da0d7443fed6be4ea9665ef9677c231adb6a3d1ab8ddeaa5693: 2002545a54ab72e11254137f185da2b5a8150064e4520062045c6dde8638a8be4: 01808a46935cf5fb2d75e8b97e4131e93b5842a68e3ab0aae3998345ed0abe685: 8b9f3a56401822e1e4af04086c31b37e1a9eecead0bcd104e08f30953092e6426: c715192dae6aca65ceed9c8b6f8df435b8f926e7881a91f9813cc86bda106cd87: bc6ace31149b3e9c1ba9d5f2b34ffb85a63422d9dcf2ebf241b2cac10329bca88: 184a24c3b623669a5fc418f1a01a448ab12c5b650e771370beaf16f761dd2e6c9: e5a5c76fa4bfc3f31f74c026263990b303ea76d2ec828987b307239036c908ac10: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: 07e77d0b86e68e9f9b9a10013a0034c87fc2ef91312163906ab27730e4a116c8- root_
hash 94ed3e67e0f3ca6ab90e872a7f03020d191548311e8610028e47ddc18fbfbf90
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