delphi.consensus.snapshot
Appended 30 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 - 2257
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id 4bfc7aa0-f12f-479c-ba06-d8e4cebfe625- logged_
at 2026-09-30T05:31:20.399914+00:00- previous_
hash d8fee0900482960efad415e67e3f9407aba15bff5ad2ff04870309f6a3d2ffcf- payload_
hash 197223cc6d8b68794501d92e33d6cb8404948d27ac845649cfd4b8f94d708bb7- entry_
hash 54e4dbc116d6245585cbd68eebc34f83a8e1b204b534b774a6828d867c95c03b
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-30T05:31:20.397213Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "4bfc7aa0-f12f-479c-ba06-d8e4cebfe625",
"series_commitment": "d5350150681a8de9939b5333687b57e86a10b8da7e56b9ea5cda437b16f3f382",
"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
dfc38fb7445df9296c9338a9b910aa850d425734a39171e906977abf96d15457- 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 - 2257
- tree_
size - 2479
- leaf_
hash 0a0beae020fde22afe3947b7c4c81fe2b28ead3cf8ec06519e48a5eb1941e7e8- audit_
path (10) 0: 8904fb50371b7c1f6a90ef748e623c9d2fec48ae5db7d47ef0facf2c53f98ea11: a009ed6ce3b6acaa315054a024cc773913501c5961f90488951cea6cad0195b82: 2dae9cd05ecc56ead30e19376b7237edae04e154cea8841fc94b8bb4e3c948083: fd501c9075ea979d95d6a0ed3c2a43b7b481b3b759145ee46c9a50ff8191d4174: f445ce666b96800069af43d82ea4095b7f74ddf7c35e9f59f46e87945742ac805: dcb1e788d76f2f9a839c0389799b0d205491dea92f2f56774d104d9ff08eea1a6: cbc4db984571c13242d6f4b551c8d58b2ac60b14ae1df2945b6a2428d447c0bb7: 126596474757e47b31a2f4c9d89412108fada5bcdc7a19a9a1de3d4012be0b578: fc41f233aac25cd7d868667ffe62e2d6bc79ebfa41e20ba3937ba4144f68af369: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash 2135d33fc3b42de9408df8505e145fcd175142e943af391ea41c56bc99a1e5e2
The earliest published head that covers this entry
- tree_
size - 2265
- signed at
- 30 Sept 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 0feab2262fa1e39174e25fc17ea9383a6fe15fa5d22c96afd722849e59baa3f5- signature
sBjF7+G1kwx7TvtzLvw4PVBUGRz/EBjcsSFszE4oR8Sldm2d36cygyHFWsQscgAwwkpOvuaKoBjxVsrH/E1HCw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10