delphi.consensus.snapshot
Appended 7 Oct 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 - 2382
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id a8c36f16-c0df-49f5-92d5-29bb1d0e58a9- logged_
at 2026-10-07T05:31:41.109702+00:00- previous_
hash d5a97ee35a495441b0a2e8f479317c164cd840e959af916acc56bd8eb98c203d- payload_
hash 15dcf2438077d30aac8166fd93a2d7bacf17668a76fef45b2d94b827ffce1bfc- entry_
hash 98989587d601df153c60c53da924d9c1eb68c93e5a8146a6dbe96370f23fa707
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-10-07T05:31:41.104086Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
"series_commitment": "812ad7a7413a6ce9629dccf0ec784b094073427c9d3a60e61781268f4c3a251e",
"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
5d8256cfffc73749bbb9aa3c79ba77b2219d9ccb3c5b131c7d927a4da5c7bbfd- 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 - 2382
- tree_
size - 2479
- leaf_
hash 45523fd49a06f4aecb9c66b7a26e6588c2d337310b650f01726af012d2256242- audit_
path (10) 0: bc90d5a108abbeeecd769be572d3cd7e2425427d18c6e81b829d3d7703e6019e1: 86b042e46da75b0967587d53c6b35c2b3ef095362cc6bc862b7ce5f9577d51ac2: 42d317d009b9e1010b5818c7ea3887f7a64ef2b39d88819e1f18c857c426534c3: fc28f53df00f457fd3d4a8e811932af1b21bc3cf334215416193dcdc85459c254: f38b2eb220334d214d29a37edbab4195582a7000f288ed7ecc2ffb43ec2890bb5: 3e5c5766e4940cb7dda94351a5e27dfc8f706fef9342e7bf2324464ea61fae746: 834c6985c52ea8f25de55920638ea90cbddfd15c7f0b1819c969144787359e5b7: 99ee92a7962953bad0227dbe9ab05c66de08e3b0b7eb51768dee6e3fc62b3b558: 765303d6f29939e50694ecde6538ee53e894bb299166d5a65c9a000adbb546d99: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 2135d33fc3b42de9408df8505e145fcd175142e943af391ea41c56bc99a1e5e2
The earliest published head that covers this entry
- tree_
size - 2389
- signed at
- 7 Oct 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 4f7f1a3085d540e3b69ac022c801823029c04ad350f74966858670c2038ea3cd- signature
UvlhE38UEMJnByU4DF/P6uC9M52OV15VOwl/s2iGtS9adIxo97fOZi78iEbiFPZnaVezyW7TYC3vGMp7K4L4Aw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10