delphi.consensus.snapshot
Appended 14 Sept 2026, 05:32 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 - 1820
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id a8c36f16-c0df-49f5-92d5-29bb1d0e58a9- logged_
at 2026-09-14T05:32:20.154111+00:00- previous_
hash 7609bb98c2e7c14ce13f768d20fab723c678106d9a9e620103c60717f618eb53- payload_
hash 5a0f8607d83d2ec185ba625c45cdbbe42dd3265f43c3709d4bd763670490a19c- entry_
hash e77fc85759b5771e6c9685c1bbb39f88518d5d1fa9a9e19f79703e698e0d3644
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-14T05:32:20.150364Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
"series_commitment": "7d72bbca16b425b5e39f40227bc9de70132ba68eeedd4102f70962d5533bfc94",
"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
e65134d20521ecbb1d1810b2898be5aea3bfb3fc30048717dc445261f3ec6cf6- 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 - 1820
- tree_
size - 2491
- leaf_
hash 4019a22058495a9f6cd7bab9c9491004e39901a6d3da87bd2ae0244f97b9b4a2- audit_
path (12) 0: 3242a6b04b3f10dc58f8ed7d8a97d2bca9ab93fc3a3de201855146569b6915ba1: c9ad5528fc85feb2066ae1f4531126ff3b90f70943a2fa679342dfc663eb9b912: 549bae22075a1166ebc1455723fae82aafb2c87bd2ed32f8c609083a7a1a6a373: 6ce51839d4e7c758a257178f42e379fb962bfe38fa2fbc19439695a93a4e72934: 910ebb775e841c1de5206f3757643ca7d376ad37a8e3efed1b2f1d57a8b5e2085: 35e93264a628694567ffa81b9f6b6754295524d7648668627e7e79e320561d416: 66e877548a61fd36a62ff399c81b1533c5b6efa4d42185e861a4558efb824d297: 250a7c52b8fa3c4932ca872a3a7842e2fb00579ab86c9b5fb8782329fdedf9fc8: 5ab1df6751f0dac25a6ce29d97587d6e08dcdd2d94987223ead725483527e08e9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 083d0806ed3c3d656f2d8c4762013d3fb4c0ed984cb03e95e8ae46936f2431df- root_
hash a9a1dac66ff7c8ec3d4b27b434ff70fbde5df3ef3dcd4b4fe4b41bb80f78a7c7
The earliest published head that covers this entry
- tree_
size - 1827
- signed at
- 14 Sept 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 6e05cf324ce30b70ee7ce89eee15228fde23a83f821f9ba8523ebaf1d8fefc5d- signature
uMGbdZogepiib7kJvGrMkp166pSNlL4XyQglenQ+IL0wzHUIeA4uonjnlmZa4EixtTu6l4fAF5nBpky7UwM9BQ==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12