delphi.consensus.snapshot
Appended 25 Sept 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 - 2128
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id a8c36f16-c0df-49f5-92d5-29bb1d0e58a9- logged_
at 2026-09-25T05:30:42.662181+00:00- previous_
hash db4f91d33dbd109b3d0b52a33078a0b252607539a9352f381d7465daaff89cd8- payload_
hash 54da2a9b68a88feb808af5f500e32fdc5046548453206a7409881e416beed85e- entry_
hash 80ef17ffd30608789d6cad069a5dd12fd35700a843115a637a6f56f9807b905f
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-25T05:30:42.659159Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
"series_commitment": "180d5f80e76df3a054bd1e8f22a2f4654b1319139ab2255da356ff6be91ed61a",
"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
e5078f512649221577022725e2283eecc2ad80d17608956ac5c8afbe58162478- 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 - 2128
- tree_
size - 2563
- leaf_
hash 18c89bc9f60cf957a7a6e32ea9493062a89c7dcfa5e432f96fee1c4c5ab548ef- audit_
path (11) 0: ebf4b9489efe88af0065cf81ad83ad8abc56094db142bced692e5d347e80dd321: aaa679815d30f5afda7c24b21dc91249cc29df370800c3161111b32c20abee3e2: 4c199c9ddfcf61dfc4c5222e5d63f0718579d1ba149d2e3273ebe33f30fae9063: 58599a8566d283033fc9240974799e6ba9de49b9f57b2907c3d6d597e179459f4: 94cf1066bdfde7962a00d5f80ce3f8520c0efa3cc3386dfa8ff7b5cf3002e6985: 559bc6d68b20ef3ce754297613d102bda419cb61cab1971c2f441622cd86f40c6: f4d02cca79f588f9c172b1dc53f54784db35848f8f8b4fa96ae1493d76b463787: 32d97e61743fccf6d32da7a407cb944cdd5c52aa0de4e874e2c78dadf7892a908: aafd507def44fb84fe7e3ad8d4e9b98fd55aca5f9a559834432ba7fa0fc8f5189: 26291f2018459f699fd091f9feee536ae8babd6de2316dd4855df868f4a2ed2610: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 5603f1f84862ea78f51857aab4dd05ce73ba33470baa2f6affe3d552f8604398
The earliest published head that covers this entry
- tree_
size - 2135
- signed at
- 25 Sept 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 45e4998f74d5c216e9d9da4088fefb456c0aa83e21edb4035f581e57b15431a0- signature
zdy+vfo0PbejA1KdjFDDhWpugBbEt8J/FMJk2Vz2wJbl7wwNofT7wjsVH+qSOXUuNAQhUmxVRVTnm/IWY5iEDA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 11