delphi.consensus.snapshot
Appended 9 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 - 2412
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id a8c36f16-c0df-49f5-92d5-29bb1d0e58a9- logged_
at 2026-10-09T05:31:42.017190+00:00- previous_
hash 451de467f0cad5b2c563b91aff35bac38015e2e7f6d203d7393a3650e3ed9df0- payload_
hash a89d321a26c515ef99b036446b9b1db4a91039ea4d563d072699a7d3ff9e5f03- entry_
hash 532eb18b5ed36bd6adfcbe09da6ae336efa9d0f7abdf22ff0a51482b302649bc
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-10-09T05:31:42.008635Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
"series_commitment": "fd5974a5036184df0446008989b6c684f9442ae2224361e52016f94c5777b870",
"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
d3855b726b218905f30d858a6a1a2ffaa698e84f72f024433c293a775c42748b- 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 - 2412
- tree_
size - 2479
- leaf_
hash 44fe1a522d9d0ae9d807d22488ba76ac7335f887bc418d9f61ead9c90c6af97f- audit_
path (10) 0: 045ccc86a8ccb86ee13aa5ac434e34d574f4757eb24812cd1cdf8e71000f7fa71: 8b4cd1cad6a61843cc6c66e7ab06cba66364b97ba57328d0c659651bdada26232: ee5997b7f60291f66a5adbb25d2ed8c7677b18ff3cb9896620758184752a46613: 164e8c911f6d97e3e8ac86735d036e21d558dc66a27d9093870fa15919d537534: db274f2c2d258d8ad51d20c9f769f86b1f49716e419ca700f25edc4da1c8d5875: 2ed9cc8d273cab38fad19f47bbc010224a19439490ee53913441e305b38d15b36: 834c6985c52ea8f25de55920638ea90cbddfd15c7f0b1819c969144787359e5b7: 99ee92a7962953bad0227dbe9ab05c66de08e3b0b7eb51768dee6e3fc62b3b558: 765303d6f29939e50694ecde6538ee53e894bb299166d5a65c9a000adbb546d99: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 2135d33fc3b42de9408df8505e145fcd175142e943af391ea41c56bc99a1e5e2
The earliest published head that covers this entry
- tree_
size - 2419
- signed at
- 9 Oct 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 792ab27f6aac6b3114b00e2bfd761c3c231f1eebb3e41b8d60921762149749ed- signature
P8JWfRWThdlhpGIU+LW8ooR/v/GHZYyB/est+Aigxj+KOIE0Kk1uvkXB2Qs98jbrN6ziBcpn+VJ7dCZTSbIEAA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10