delphi.consensus.snapshot
Appended 5 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 - 1427
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id e732630b-b551-4965-92e6-7168c5a86d89- logged_
at 2026-09-05T05:30:42.068789+00:00- previous_
hash c87ca167548f0a468979a2b02315670044a63b67bb32bb59b7a752f29d8a62f5- payload_
hash 97067e4eb8404719136bd0066dfec6c619cf4baceb996c1bea0d939db1244a71- entry_
hash 4f42a149407c1e30ad3711028c8aea75e8071ca12046caf09c7b73d45229ca7f
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-05T05:30:42.065771Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "e732630b-b551-4965-92e6-7168c5a86d89",
"series_commitment": "c242a5b7d4b10b3d681c8b040ebe6517c37328a1d8259e7217ea05b07dd12294",
"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
71684ae9f28aec610af261e10416aba35cdffee2b48f39130ae87c050a85a042- 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 - 1427
- tree_
size - 2265
- leaf_
hash ed89fd3d67cba622e22a8a4ac2b2bd9b708f4030c28aae79e2c15a724fa9ea8f- audit_
path (12) 0: 18ab34283c19e0ae28590a3cca8ee41ad5a161ab8fada1ea55c8eff3e70337ba1: 2195bf81583678a9098bdbeb7e3c10c87c8d20393619f437884ffde9268096fe2: a3ee7e6a425c4045bf92153f0be72606988050e2d8ad9184097e9c4937d018723: 25c67c207bd62c55832fef4c6767c92a1edd644a28b4bc86a509e4abf41031004: eb2ad53469a5278129837bf3faf26af1991b9ed24b7535827c85adb2a6fdf4295: 2d7f0151c1724ba0ea8bf06d726643f0f6893ec7bb868e6681848be8fd368c056: ef252f031089471cd75411471a0532012f4deaced96acde8a10c0024e7faaa357: 59548e903d1441fb0d6e6d441d39382bb2fbf2f915e94e4c49c6bda187d8c1278: 73b80563a47162cfa99809097caf5d77512af3a28ebfbf76c6bcfd5f572cc1d29: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 15428b80842f9a0801cf7667918b216c9ce4186d9825e806ba86972b039c03f9- root_
hash 0feab2262fa1e39174e25fc17ea9383a6fe15fa5d22c96afd722849e59baa3f5
The earliest published head that covers this entry
- tree_
size - 1445
- signed at
- 5 Sept 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 14935c0bde678e80dc3a37641650904de8988691c769149c38b10d54518ed6da- signature
oBabtEvQC4ypaFdP+K4eO6SkxwE6AoHWZOprH3l6t63fcsSRixVw214MPbkS6PXBnFsTXA0rFPKABtwhipFLCA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12