delphi.consensus.snapshot
Appended 6 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 - 1486
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id a8c36f16-c0df-49f5-92d5-29bb1d0e58a9- logged_
at 2026-09-06T05:30:21.435456+00:00- previous_
hash 82e188af9f7a9c34d4d3e835c68eda9d23a9e89add2127309a3c79941249bd51- payload_
hash 246a616c4708712b6895880ef63b413204b8a6f026cd8b2ade4c81db3c4cc236- entry_
hash 72c15441d953f97dcb77cfcb4c1e199ce04814ee652dab74caf8f90bc0b2967a
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-06T05:30:21.432954Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
"series_commitment": "56357ccac5b9e159d191f145ff9527f8db89a6cf4e8fdf495e63d6f82f1b23ba",
"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
f4b6b2eab96c759b46d9130da0e8304f1568e0f2e74199cffb5225d875a08597- 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 - 1486
- tree_
size - 2479
- leaf_
hash 868d5756956839e735aa317bba357c288bab75b7d7a968f3e11c3d4a919d7c08- audit_
path (12) 0: 54391313d0c54d9c56a046b2bd144b76ed137c830a86fe7977c407a806b835021: 854b46b6b2bbbd7622e81de664b47abab964da80322e41a8333628f08b98f6d12: b18af0d3891cd798521640c299a339d7d9293c58afc2813cb4aea648a72fb4bf3: 07701079593dc85e21d709129f54a92611a58e43a3c312b79b1c96ae6853945d4: c0a5ed0c56c19f12df6f28039ba42c4239cb6bb5489beb861f9b0de2a032879c5: 91804abf66bcb55033aaa7181b9ee3fb61db565440654bb166ade8248335340c6: 35aca0f2b9f8c478040e38216ad4f2e9efa65fae1c6fc41a8df2a826f260686c7: 59548e903d1441fb0d6e6d441d39382bb2fbf2f915e94e4c49c6bda187d8c1278: 73b80563a47162cfa99809097caf5d77512af3a28ebfbf76c6bcfd5f572cc1d29: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 8d949d6aef53b2e3322ef5e232755263eaea63b886b405d936c87ac0c842b6a1- root_
hash 2135d33fc3b42de9408df8505e145fcd175142e943af391ea41c56bc99a1e5e2
The earliest published head that covers this entry
- tree_
size - 1493
- signed at
- 6 Sept 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 1fa4feff08bf18e521e5bb925c6c5fdbb5017b8c298b1beb9ba8937af38f607e- signature
aqpHHBZ3TglMYwcvhOlfahpQD8AtFI2Le5O0NnqlhVLEXF/fDrgc8TON7pwPSD6UixQPbRrEyUkW8rogVxpzCQ==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12