delphi.consensus.snapshot
Appended 12 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 - 1729
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 05901165-61de-4a02-b759-02a9bf89ef70- logged_
at 2026-09-12T05:32:20.817139+00:00- previous_
hash 50595a9d847bb5d7df384c5b1c891659f123f964c0b3b77d2ce2ba6e34015ddb- payload_
hash 615533337f20583e3108bc606037263d3a2aed10fab6634f2205172f6d8b58a0- entry_
hash 769227562ab76ed4cfa264ee513a6c484ef9dd6ad07548b8bdcbbf038a4ffcd1
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-12T05:32:20.810862Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "05901165-61de-4a02-b759-02a9bf89ef70",
"series_commitment": "03da2500a639a0d721b0b30d27e61f60cc201937bbddde01119fede0f3e72852",
"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
1375c253a47befb259aae7124c71c9a165d7638fd8e3a847df324b5eceb71b66- 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 - 1729
- tree_
size - 2285
- leaf_
hash f669ddc14418a5491a2131737c76a05d01994524a41f6e119c26f38dffc99907- audit_
path (12) 0: f9938a5c1fe418ee482d752be5cff8909bf32f174df7f670e893dbedebd1c2c71: af27240a2bad1838b0b8650b054ac20596b9185d85ca8b241a464b6270d18a1e2: b651ac760b4d5d95d944329e1424113c5d387509165312fdf4ed012ed56a9fe43: b814d945d5d232ab17cc126ec80a893077ef532c42c65e282285844adedf13a44: 0c9bd5c162fc6aaf5d9bf93b62d6c7267bc3226cfca9518555e4803f850180b65: fd82ea2957dec252aaf0f497194cc97cb06fa6fdc01911c77e1a2e46ff4eaa336: ac160a0852932e7e1298c12b7bbeac8a979011b4c86d850294a53e9c58329b547: 89bbeb672caa03ccca78c3e7d709e14d72ed0f279c7cfcd435bb71dc863239c68: 49fbc719d10777c21e02e255a1174dbc47e89c67c7b327c5f50e8ea1ffbb5bad9: 5fb1ed5f5a35e845232517268bf48c5384c29f290dd198d1d6f802756a73a76d10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: a95d574e00e9fefbc454b084e8cb19edc83831071366b2d8dc1af2f7114b646f- root_
hash 17330c6327e6363b8237bd4a68d5ee420a6d0f745c8d8bab0a90305d6bccba50
The earliest published head that covers this entry
- tree_
size - 1749
- signed at
- 12 Sept 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash e8cba9a99f4a57e7aaabf2bd0c850bb0715afb51953cf8fcda65ca036a6c608e- signature
cNlPz9oqpkHabbJeJhuOvJLMF32ooelAhyWb8yHCQmsqZM9LEZ0petdc0dMGAZbz5avsJ6pUSC4TluX7fEBpAw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12