delphi.consensus.snapshot
Appended 22 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 - 2044
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id cd22f6a9-1eb7-4927-a2e9-6736a77b75cc- logged_
at 2026-09-22T05:30:42.194951+00:00- previous_
hash ea9b0015e2c91b7a6ed0a7cc704c993cb928765168575dce0b1d01978ef0d197- payload_
hash 5e1f794ffea1aa108f45f4d2bdac5cf6fdf4259d83b1ec387f30839000a84005- entry_
hash 6f7c38095a1a6351a5f1bd59dd054e2b69a78881109da612d59b7aa7c1b552d0
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-22T05:30:42.185410Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "cd22f6a9-1eb7-4927-a2e9-6736a77b75cc",
"series_commitment": "5f02c6e15367735c3a8c2ca71a25189c321f43c6f1f37a4cf7f545cc76089d2e",
"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
725696fb38d9f5520b487a8dcd21dd693430e41160082f2c4b5e3a05e9cfbab1- 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 - 2044
- tree_
size - 2503
- leaf_
hash 65af00fb4ede392ffce43ab13b97f3903e0fcc9ba708e4bb91bd49570b2ecc3f- audit_
path (12) 0: abb405f789db2bd5e65d1687a149a8eb33a4408170aaba18f038c32496604f221: ec3d0f9002dee063079e99b37edf9eacfa4c278274f8b41b8a7542bcff99907d2: 1f75769f193eb8c6060c7e9fc382a8eecf15027553e868d3c97e7447b83a7d3e3: 241b7d382e5c30d703aa2057b6dd9f605ff2051ef4278ff22260ae1190a2a9a94: 34754a6b18db45df483970ae551edb298a26e629b24951179b3e71083a8977395: 67597ad3c6d4b363732dc65bb4d4bcf26e23a5338a996842c3364d3486e683a96: c321285e45ea8a57cf869ad4aefceaa5840e364ae5f182e7b0c7b58aab9054be7: 8018b7deda34c522f2ac360ffdd9cc85624549e7457ea594e86a7f04e9a264aa8: 5ab1df6751f0dac25a6ce29d97587d6e08dcdd2d94987223ead725483527e08e9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: aa4b429c2497df4f846fe6b3e60223989226aaf0ba6013dc6f90c17afe986d9d- root_
hash c97f540ea605dcd0a8a4165044c60093cb885a8303800b87d215a424a4d5258d
The earliest published head that covers this entry
- tree_
size - 2057
- signed at
- 22 Sept 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 857e19aa8f1cc7614fb9fdf9d058ec533ddc78750211f838d19db42220d865aa- signature
AVZv3xnQwzbC7q66pT25uEydYaqHraujngZDgUc9bLcnBMJY2/3cC1iWHhYJ8lzRwIOowiO3PxPF7hkUEEqqDg==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12