delphi.consensus.snapshot
Appended 16 Aug 2026, 18:37 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 - 232
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id d8d7d8bd-61ec-4918-b395-799de97e359f- logged_
at 2026-08-16T18:37:39.170606+00:00- previous_
hash af966de523942e70212822a3dbe25c32f155edb772795dfd6e200bb679a4b4e5- payload_
hash f180737bdaad0639dceb35d874e358406a75a51926abca92c07d74b077d6083d- entry_
hash 709b1b3b3c41a3781517f6594f6baa5d63a876dcb7541ca15ab96d04773371eb
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-16T18:37:39.158847Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "d8d7d8bd-61ec-4918-b395-799de97e359f",
"series_commitment": "e818647cd3a28b54fb4c298906c0ad617a7cdf89dd29a580080ad188045252dd",
"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
8ad78302069495194b2d6b3200ee30843e3b50f536e22b9eeaa4790e20b2ce93- 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 - 232
- tree_
size - 2341
- leaf_
hash 5f80bb012b514fe52a629cd4c63625bb318cbc1db7ff959f7279215cd9a47b67- audit_
path (12) 0: 55e7bb9a110b2d5c72b093aec9fdacdc471d0dde0db88fbadba2341c6af0bc1e1: 4864ed5c60ad184d9442adcc901ebe733b446298d97de70a4d7d65f75e7fe9f22: 73ae418dc9956a6dd16ee956bac0dca188b566b726dfd54776ee8429cbc73afd3: 3dc4ee7e9f21068bb1d06ea724721b93410874c1de1c8664874be45406c6143c4: 88a5c76fce868181e508348b8e4cde17b4954a2eef6ccd1f41e617e4522600dd5: 38f22b4f6954e82fcbee4467f4a42ba1f2942ed25bc15b0809079511da578adb6: d84113033297e6a1a6778c4a1e0094059ebbb1414eced4e82d59b1e29bed26c17: 8e3ada3865734ef89cf9ebd82b633327831f303fabc83306d43c8e1c4685702d8: 6e5b02022079dc614c5f74ca1c784cf9700d832e05c2eec11f0ad0a37376b46d9: 2fb679aab258481705c982e553094522ea7bb93361711a8387ebf359e8c3e43110: 86666e2cb262024eb1c2584c671184dc2fb8b8d41a345bde94ca518e487ac23911: bd18df2de60e205be411a53ea96887ec76f5a16c15250bf48e3f90dc788abbaf- root_
hash 9f32e37b52a81f4fc0f11a1b956464ef6acde09c58b0ce26dc44277199cb7df0
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