delphi.consensus.snapshot
Appended 28 Sept 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 - 2206
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id a8c36f16-c0df-49f5-92d5-29bb1d0e58a9- logged_
at 2026-09-28T05:31:39.573430+00:00- previous_
hash 77356f1b23365f33622e6c18f6b1ae5c2a886f7192225b47521f747c7fb5fe0e- payload_
hash 607be8a18fb4d21aaffa4f0aaa917e0ccbc481dd48e4b4368ba8ae9e4c257654- entry_
hash 09ffdf286b80724f6dc26b0fb43720975c2164289be557d77e517056df64eb6d
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-28T05:31:39.570234Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
"series_commitment": "46030b8c343f06fe7234256cff75b6b329d33a83800533dd5067324d9ca2e230",
"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
47b7e5afd15c07108f717be87c30100ebbdf52810019dd5001fc01d2653feb8c- 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 - 2206
- tree_
size - 2503
- leaf_
hash 1b934e2010c6e5ed21ef661f8c40df3ced9a21d4d5fa2d836c17b91c0b7b4017- audit_
path (10) 0: a4262b07255f2a4c37f3c1dd684ef8d4bd26955ac85d673bc56ffeaec23069ae1: 9b3956381f1f39650b36d83bba8135287043f29f34d648c40b505f76738f06a42: 2fb9a70ce8645f06aa4c3fc18ef951069927cfa4df1c6784ab004089d095afe33: 8285573693690377c5f56c09150338e11062ff5ffc6f2343af99fd370976ce9d4: 49bba1cab8bbdd43d7b9bf51acae2e4ee13dffaca0854642ee664c756f28e05a5: 0349dea9398b8aa40633af547e822a1da687592d53272f4e6aa136e48023a75b6: f30320e32b01d85ee25d3699765f61034c40add7177cc53ee3e39fdfed97b4367: 126596474757e47b31a2f4c9d89412108fada5bcdc7a19a9a1de3d4012be0b578: 47a3489f8ed18aca1e6e6b6ae98a5d47ac64bb31c7314e873c7cbac9cda2eebe9: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash c97f540ea605dcd0a8a4165044c60093cb885a8303800b87d215a424a4d5258d
The earliest published head that covers this entry
- tree_
size - 2213
- signed at
- 28 Sept 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash e6ef985c2d8c02c6ad806a1fed9e7dbd1908860b7059dafd6031fd735675222a- signature
lZwXVggSbp4U9M4HPhBdliPV1fW7ltXRhHCMzOGIxk4uVObAicLqZ+silW7WvZAEBoECv+It+4rRV6HqbOHWCA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10