delphi.consensus.snapshot
Appended 23 Sept 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 - 2076
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id a8c36f16-c0df-49f5-92d5-29bb1d0e58a9- logged_
at 2026-09-23T05:31:22.118529+00:00- previous_
hash 87f735cc8b393ecd526649442354dd1f22cded5cfdce7b6ef77bd88e7746e969- payload_
hash 7fd024eea8f60475d7c22de3b3dfa011d31dc3ae890728ff5f29c7f1392b18a3- entry_
hash 2558cdb28554523c9215de454f0aae8cefbbc79b28f111f889594889f4415456
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-23T05:31:22.113845Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
"series_commitment": "46794fadad40108f25293023818bb9eae5a3bbeee49ddf9c5afe2b734aeb77b5",
"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
6b7111ea3375bf5765bd84656127047afc588a8f463703ffe757de67a4edd83e- 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 - 2076
- tree_
size - 2527
- leaf_
hash 7309186d282810f7f913cc58a5376de05a8d3955e2dd7cdefbf4574bbb43c4e2- audit_
path (10) 0: 631d88acd9d8f3bf7309f62cce0bb98e73277678605798b412ab85ae481d997d1: a7446ed6ce29844b812fa87c76e2f167df889845e2b8d4c5539df8490f6814562: fbf8ebac3ab0fd26d2dcb698afb14415cf697751343e59b7c211d6b61b2b1bfd3: 47f6fa8eb19b5b350ec3054214a6c4629129dff19ced8a87a6f0c54fa268741f4: bf44c0f23985ec73ba70f8bc29b0f6ad4f1e936885cc5a45e5476c3db4d6f6c85: 02d0dde49bb94e626ee08c2578f2d51d2b820b89a132a330ac2c7e0011eed04b6: 97e580b0f254128201e36dc81f73bca17443fd5e21d28fd611b3832d3123cce37: 32d97e61743fccf6d32da7a407cb944cdd5c52aa0de4e874e2c78dadf7892a908: 50c7fde465f6973c57ec2d3b5a940d7616fbbd0425b42d7aa13514aa4b0a1cb29: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash ec978d5c7cdf86c1addae478d489dfb54061a2da37f75e4557895152c63d6c38
The earliest published head that covers this entry
- tree_
size - 2083
- signed at
- 23 Sept 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash d6c88688a6cd2ce0afacd2220cfe05c6666fc242ec7f9ac09129b8d0bc00fb0f- signature
bLHEfkVSe/EJZc/PD8usy+UPLY2Y2/f+Mxks+W/Ea8Ln6XdDXICDe9lU9Oos68dZVS29/4k0IitE7SmvpTB5AA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10