delphi.consensus.snapshot
Appended 4 Sept 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 - 1382
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id d1b83331-68f7-4be7-a625-f7824bccab5b- logged_
at 2026-09-04T05:30:40.464351+00:00- previous_
hash 5219e02eb3f6f5f5c13f0b9059a5bb38c18377755a32ca0104de3c845d0ce8b2- payload_
hash e1f005e76f9ba15de7c507924ed33ebf1ca77e76d04431c759bfb13c921f3e5d- entry_
hash 02f9b2b3780be8e6df37a83ce0d765e5a2dc7f6ff768918804901077b978fce6
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-04T05:30:40.461768Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "d1b83331-68f7-4be7-a625-f7824bccab5b",
"series_commitment": "9830b06afd03b47a286bac8f4beb75d859bc047a871e85c0518143ebfdf40a45",
"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
bfcb496e413e5cd78cae9c9b3213a50e76a1167d3f8bba8e1b596db7ef740aea- 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 - 1382
- tree_
size - 2357
- leaf_
hash 154d8b69d0cbe928d3c49b541a4808a6b1c6ea24221a70591261de73156328db- audit_
path (12) 0: 62f786517b964263f284ce7c4f46702c5b999ad84824fa37469208d322b1a35a1: ac177421f2d0bb72bf86e82f6a1068190080d3f659b8304ed22b7a4c80333e0e2: cfd42c55fc828e574791e6f579cacd4a2460b67e81135b11ef1ee105021c71983: 7eccfa57eee54b1cf2725639ee65ffb07ed7aa08e48a35b4c568ea0080f4ab514: 13f28f3407a29ccc4c44d00c691dfee5d2a85ff0d643ac7fa01890f2db8136605: 3d3a958791e28b79f550cca07dae62a1e556e0e03bb681620fd44cb3c0b449456: 3347dae74325660c6b1e768277c0a7f2169b7554b58c0815e1d6311ce75bfca77: 00aa16d00eabe2b61089fea4a6c3044cf3b1ced9f2af168276f93e239a98dae48: 73b80563a47162cfa99809097caf5d77512af3a28ebfbf76c6bcfd5f572cc1d29: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 2f361a0c4a49843181536f3a7baa572ba4bc0573be4bb8272112c3d056aa1031- root_
hash 58c8c5ab99dba36e8c6b398578e37592253a716c9cf756f72e78b6606a198d59
The earliest published head that covers this entry
- tree_
size - 1397
- signed at
- 4 Sept 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash dcdf356cdf9dc7ebf6b15487b75fbf56f1dd13b64c18428b5b1c3def4a10dd7a- signature
3byga8XRhlKNr2NA4ABo68hmWG9n+zteILiR72i24nQlgkl2AHzxfRM3GAGCw7aUDx0eN916Oq0zGWs0D7mPDA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12