delphi.consensus.snapshot
Appended 4 Oct 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 - 2334
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id a8c36f16-c0df-49f5-92d5-29bb1d0e58a9- logged_
at 2026-10-04T05:30:21.200389+00:00- previous_
hash 7f976c3fe1ae0f0cc3aaa11cfcbcfbd6eba8f16850f4866d9442149b0a2b81bd- payload_
hash dc02915ed0a704e2ec468cfd0e1b2781d32fbdc45e9686fec54cc4e6c531bf7a- entry_
hash 07871dd93ef52f3872793f8dd5363ca36096dd89b5419b521cd49a6f168d6ab8
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-10-04T05:30:21.194469Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
"series_commitment": "47aa277ae78074e391b26cb0a7938d58906c9687041d050bd348194231108aa6",
"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
ae9eb312ccb3124b4283fd205ec6b33de13ea747feb384e6c3c04dfc9127f9f0- 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 - 2334
- tree_
size - 2479
- leaf_
hash d64efeea7c01e45af8270c14f7ee49fcc214b2055de1e36e5ac37740b8b2a411- audit_
path (10) 0: c59237adcabeedd823155e4ac9d46a1477f78c7098322d9d84934aa9e8f3e1de1: 59bdee84ebab9720ffd06d7f54450a3eac15348e7e9aff1fec946b8d807df6412: 36435e33d92c7db35301b061e47f8b11a17a90bf3d67d6652a8c8ab1daa853713: e4b8a71b844ed5f12e965aee16ea73f6f5bc8a82b5e1c9f8bde5458e3d7fbc604: 5c26e136e60e36307df95582430f3ae73b38a515c084d9e67286aac314bad5075: 8055e8d16004c9bd3edc12cb580b60b66991d223747a8a1be5c476f954671c5c6: f60923cdfcb3584afeffa8530ee1cafb60e6a0aff868cd02794b4b9e5ed208eb7: 99ee92a7962953bad0227dbe9ab05c66de08e3b0b7eb51768dee6e3fc62b3b558: 765303d6f29939e50694ecde6538ee53e894bb299166d5a65c9a000adbb546d99: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 2135d33fc3b42de9408df8505e145fcd175142e943af391ea41c56bc99a1e5e2
The earliest published head that covers this entry
- tree_
size - 2341
- signed at
- 4 Oct 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 9f32e37b52a81f4fc0f11a1b956464ef6acde09c58b0ce26dc44277199cb7df0- signature
aIyBq7WrK8z+2h6auUYK0NfeCTmCYzALpNq2nd+/ftrgcBTOpYxoi/MI/0VyV7rvp4VcCF127Asgtj/m4wmxBg==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10