delphi.consensus.snapshot
Appended 15 Aug 2026, 17:40 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 - 180
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id be56b97e-fbba-4073-8b29-04e6afa28138- logged_
at 2026-08-15T17:40:22.571506+00:00- previous_
hash 07f23e9f2de2eafedbb1fd593b21627734ff68e292f880d7306000e1e46cf913- payload_
hash 92400c35bf06fed1c51cccf8025dbcc55b523433e7609ea131e280b272d88b43- entry_
hash 12f64915676705d30b61e34baa6d6b62dd2bf1ea38bbc80b0ec8de410ebb1036
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-15T17:40:22.556338Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "be56b97e-fbba-4073-8b29-04e6afa28138",
"series_commitment": "1df8570040a415543bcbb4f366be75cdc8c00b0864d0cce1787e4015b8346671",
"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
a70f532d03bbeb538a57aad768b45d7ab28ad80cc96fb18da4f4dfbbd9bc24d3- 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 - 180
- tree_
size - 2323
- leaf_
hash 13b468c9082ddff23deee69d5c68e9422064281cf6175b010091bb481ccabf8c- audit_
path (12) 0: 4ab87c386288217d0876a2dbfb9fb31f25b6ab09a744216fac869769da3daf7a1: 91a26fe470e37e29f42ca813fab6643ccae153b9485a29b19bfe80abfac3cd702: a7fb9e117bbd933cf360bde5ff374dfc3f1fdbd44ae75b28e7196f469438a1dc3: 4fba174ebf3c4668231dd8b97401f68f84b51474b130e285700f618ebfdb95494: 4c662827fbc2b2e4df650edfb1debb0bf2901593e38d586ed8826b0586b79d185: dc65f705f8825b65cd837fbc21e908be23ce2e3613f86cab80adfa745e5e0d036: c3b4d3376719648a480b38b7b7d07463135f7839d88422b8699fac5ece48f2757: 8e3ada3865734ef89cf9ebd82b633327831f303fabc83306d43c8e1c4685702d8: 6e5b02022079dc614c5f74ca1c784cf9700d832e05c2eec11f0ad0a37376b46d9: 2fb679aab258481705c982e553094522ea7bb93361711a8387ebf359e8c3e43110: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: c3259a319fb9b811eedac153ce91727bb54f7b550d8cceab957b75c3a0564058- root_
hash d5cdf3ada5e9d6ff6f86cc94c6a7cd9965df1cd86b6e68dd8030daf1fd3631be
The earliest published head that covers this entry
- tree_
size - 374
- signed at
- 19 Aug 2026, 20:25 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash ecf4adc708ae542a0339e03fd4cc181cf49d0329768627c5345c915a58bd813a- signature
3yL+JZfMhiQ6rm5rCTTg7iT+or04nCGVcQ08ILMw/d7eqvR4Jid7cEg2rQU5fCX7llStjVkTC9jVZjfGQvtMAg==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12