delphi.consensus.snapshot
Appended 30 Aug 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 - 1104
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id fc61e6d4-5001-4db0-95d4-be60a131bd47- logged_
at 2026-08-30T05:30:40.998239+00:00- previous_
hash 6cb63d9c96ccc3685201ef11efdfa522791b0f8f6ce0966ccc684760ac71df5e- payload_
hash 3a88df8df0d06766fedcc0b86abe74696621978ce604666002ba2b1a571de38e- entry_
hash c66855cbe81bc509dde045d9f35281b4dff28bf9fb597f5d19e62761f6229a2b
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-08-30T05:30:40.994757Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "fc61e6d4-5001-4db0-95d4-be60a131bd47",
"series_commitment": "c7195fa5abde49533add865a1c859894e8c88a843b8831673465834b83cd059d",
"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
ea8972e6a9691453d5f7b686cdb81961fc45ea502156c21574ba9b0f7da6da35- 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 - 1104
- tree_
size - 2357
- leaf_
hash 5e89bb475eadcefcfac240fc899eca480b7b4cb7f81d0c06586ecf989306b9e4- audit_
path (12) 0: 7784a6e87422df0fd4811b82e37e4ace5ec29392f199788a66d1f1285afdc8f61: 56e906a7ac12e22efb55128d556547b50806b4db9abaccc7ccd15ae7beebc5e42: fd8ec32b13db99052cdd607269250b883def71713b9a259810beca7357bd93e23: 9e64e9935c6d2296157cfea59d898a4bd91cb5c1b4af8af1c4fcad08cf04d66c4: 082abd3851e6828c8ff227c8cb876ad3b2f35792788c1ec7782d22c728720ade5: 8947d8a1e70be2b634115b93456cd4640838c379021b8f3207e435521e78989e6: 3330710dd5fef91aa0e763e3b3c0b21b7b27e549cf2bfbc05fee8e8bfb1f42b77: bbfee2f96690132143d2a2a16089df72535201b31174873b1f1a4d4c85a029a98: 6ce18fb0b650e54a2c9454c3e9abde48f8386826f5bd1752662ede2993ff557e9: e4979eb1a845b9e87ed1dae5e71668989143fa3d9cf0261e0f77022718d3602e10: 9cc5fac487aa9ec1c73baef673025a398e2ca2721a82dbc4c270eb2473aaf7be11: 2f361a0c4a49843181536f3a7baa572ba4bc0573be4bb8272112c3d056aa1031- root_
hash 58c8c5ab99dba36e8c6b398578e37592253a716c9cf756f72e78b6606a198d59
The earliest published head that covers this entry
- tree_
size - 1133
- signed at
- 30 Aug 2026, 05:30 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash f93488269a5aeaf9d50291920769e871ba9d361f0fb72089c9ba41c88a2727b6- signature
nnzoG8Yk362jKSvRmRO456zSfVqvhFq0AoyJZsV0jjpigKArT+n7iaJbA8sAIeqGXEUgCqPLF9MrRlQug43xAA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 12