delphi.consensus.snapshot
Appended 16 Aug 2026, 05:31 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 - 196
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id d8d7d8bd-61ec-4918-b395-799de97e359f- logged_
at 2026-08-16T05:31:41.371225+00:00- previous_
hash f4513bab94383e77fa956498568fd8d5ff6d5fede22b92af7f32b897a1450ede- payload_
hash 1de4bb5dd5bd4b4b1578f840df7805f571ef87bc07e729ac3434ddf74282057d- entry_
hash 6aa2210793f221ccaa1b6654a7f7ec1f26d38331c47ea44f54fdd4ab2ad4c1d0
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-16T05:31:41.368239Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "d8d7d8bd-61ec-4918-b395-799de97e359f",
"series_commitment": "0399c1f7e9603edc63aa352539c070dcf9df6c05fabf6fa359f800ffba876c95",
"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
8eaee159f23d32ed7ed739154d825465076efb110d744b5c7a926979a924ec52- 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 - 196
- tree_
size - 2323
- leaf_
hash 19a823eed6a9d7a270fa3e00ad4640ed1dbb02848685b64fe0817c2194ee9b6f- audit_
path (12) 0: 2c782ecab591208175089c4c6be66453e4becf0e331a742ce9b4ae32a07fcaf91: 06d1806a1aae5d80e455e7af7c9169bc05e33260cecfdb605027d12e2e6d99b72: f3bfe848bcf3a79d7dea341e4cef17a041735fe57246feb14c7cfeb2d07c15783: a8a08bca9deec95709497518d54e110deffe1e7ea0246fa5383aa5639dd52a724: b6d017ce8c58d3ecec9ef7ee1363be3ac193173c87c4f036c07f007292f1f7e75: fc441ad496235ad68d0ad62d88ed053be8000557ddba9a742a39c6c06af3a15f6: d84113033297e6a1a6778c4a1e0094059ebbb1414eced4e82d59b1e29bed26c17: 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