delphi.consensus.snapshot
Appended 5 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 - 2350
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id a8c36f16-c0df-49f5-92d5-29bb1d0e58a9- logged_
at 2026-10-05T05:30:21.100797+00:00- previous_
hash a3f29f628a1ad4a48cb1129f82f33cef9fad859c34a1f78ee973dd1eb650d672- payload_
hash a38f7072583cc29e3830fb3c31705cbdde79243a33b0dd4d2d21734b075c4e6c- entry_
hash 1d8410ff4d16bb1e7b3fc1e156f5f00a21085ec070be5aa8a4e3247712631503
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-10-05T05:30:21.079648Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
"series_commitment": "cb795ea9acf3fce13696643d31dce0e2c81eb53bbd2dde0d2c0df3f80bf76db9",
"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
af2b6cb1160daf742abe7b09d375da6b5a4084c552a613fdfb0c8407d1283c0c- 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 - 2350
- tree_
size - 2491
- leaf_
hash 016f0bddae5c16f82b62c97a780f5124e313cc9395028cf215bfddeb76331225- audit_
path (10) 0: d17a40d9048cac66161f5dbfd92fa5495783e783e53d7ac2a0bb6d3dd7b85d111: 36a4f185649138f6357ea769635f9b66a0b816382d70f4cd372c9b03ba14a5142: d50490e6f9397a688172c1f71c0cf0cb3072af9faa332c2cdd6c896671f0607a3: 28aa0241b051bdc60ed1d5300cf455d21212b810db8d5c02f4c9add05b5f08d34: 7dcd25b3c98562e656f4d02e51c8fe4401ef9961c96942d96328da987977199f5: 92498c2b48d5d20744b9266e1c2f22eeee4d089e5a8ad2645ec11941889cc7156: f60923cdfcb3584afeffa8530ee1cafb60e6a0aff868cd02794b4b9e5ed208eb7: b23da60f2e510b29c72a07aff7b47743065a5b6d552266a144958cf77a987e958: 765303d6f29939e50694ecde6538ee53e894bb299166d5a65c9a000adbb546d99: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash a9a1dac66ff7c8ec3d4b27b434ff70fbde5df3ef3dcd4b4fe4b41bb80f78a7c7
The earliest published head that covers this entry
- tree_
size - 2357
- signed at
- 5 Oct 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 58c8c5ab99dba36e8c6b398578e37592253a716c9cf756f72e78b6606a198d59- signature
xirAN+AGnV8OMbXLhyTyIr8tL2yeCmVCQzEWsX17jN3ibAv8OM5FjxuXn6qQUzvxDbqxwqbiRKdCifgC58vSCw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10