delphi.consensus.snapshot
Appended 3 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 - 2314
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 3b91df80-00fc-4a4b-b86e-3310edcb9332- logged_
at 2026-10-03T05:31:12.378148+00:00- previous_
hash 5a37915bea9576b8f0aa92704f67222504dd2acdeb01091edfae5d1e68723861- payload_
hash 91810525eaf074ba66352c4977326a26a1a5d831c3c671aea4f97fe119a1ca2b- entry_
hash 679323822d6953f53f29b64b2ace8ebf8ec64b58877ff002e5aebd7d2e8ea4ca
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-10-03T05:31:12.366320Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "3b91df80-00fc-4a4b-b86e-3310edcb9332",
"series_commitment": "5ecc40045ea9ee0d93de683a3baf1a5b3652083a64c2b6dd8c91c4ffd0f021e8",
"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
fd0c6dd69c47041f29770d0c3989d54b9d351e89b58b7d2e6466e6bb2df3aa1a- 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 - 2314
- tree_
size - 2389
- leaf_
hash 86da81953997ec273b080bcb687446a4cf58dbfdc46edf932750580f71583b80- audit_
path (9) 0: 17fd48ddcd67dfcb0e93cf622ca66c582c391d6df004405ab5d197e8a3efbb071: 666b243b720c610f4e87a4f3c3c2c179d3d3f9db91bcc26cf09677b8f58e16412: be32868ff4017ca71406d15fae2443047bd3481afe2bb89f7e21ae99886cdee73: 37b07d7e5dd5947a3c43fcad9f35a0624ed0dc80c484579a0c9e5980add1b6644: 2a8d45d5c5dd1d335c8971c0f86db7634941560caa50de678092b2fcafebfbc85: 8055e8d16004c9bd3edc12cb580b60b66991d223747a8a1be5c476f954671c5c6: a996b154fe63ce51a611e48e1d6360e7e9e40f1d5821b39e97eab310e640deab7: 765303d6f29939e50694ecde6538ee53e894bb299166d5a65c9a000adbb546d98: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 4f7f1a3085d540e3b69ac022c801823029c04ad350f74966858670c2038ea3cd
The earliest published head that covers this entry
- tree_
size - 2323
- signed at
- 3 Oct 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash d5cdf3ada5e9d6ff6f86cc94c6a7cd9965df1cd86b6e68dd8030daf1fd3631be- signature
1BQCMtKOV4dlhWYjBYTSEwsJ7gT5IVLMC39AMQobNHEVmLfgNgJd2teZf8zEq6geGuh0vLM1HXVqdZvXtRtjBQ==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 9