delphi.consensus.snapshot
Appended 26 Sept 2026, 05:32 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 - 2154
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id a8c36f16-c0df-49f5-92d5-29bb1d0e58a9- logged_
at 2026-09-26T05:32:12.243363+00:00- previous_
hash e12b5d7e31b95a0877540904b9886570f547713e7424f6f4f13d3143470a6eb8- payload_
hash 8546093af4fb7a9e2ecd301da3448f7fc8dfa911b02ba05659e4d96266665878- entry_
hash c1c68c521bc80fe11eabe10450b90ab9e02286add3543251af8756ca91f5b110
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-26T05:32:12.238138Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
"series_commitment": "1524ecd0064c921ed5a45b60eebc1c04ecf9e2d8aca92216c525f6c408b92296",
"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
47e9fa08fb5e533b67fb6d0261fb718a3858b9e87f6e2829a578d8f547a88dfd- 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 - 2154
- tree_
size - 2539
- leaf_
hash e8f5f27fec7046edb9f2a9d874ffc3334329d71b7959c99596327bde49f99d18- audit_
path (10) 0: 08de9c994eb7b6b1c58f40c7d84bf4adea5418fbb09c730f696ac8e7c95227d21: 7901dd3da0950cfbe2406cffd1edd4efdc29f6717452fb1f2c303b62b2649eb32: 2421c09e88d6b0b229e398b64ea2a38025c439046aadb6cbcf5a83d85a247d163: ffa421c251f691dcbc1fdb8cb320944ce3a3a9ecf1738127949a1cdff9df7c5c4: ce84c24a1d3f5de3d333368de28d51a29649a866b4d9ce9379de23fb6e76ac895: 50cc49d79f0f3c552cc19006c4d6b819801e07bb4acb2a3fb50f66393c28555e6: f4d02cca79f588f9c172b1dc53f54784db35848f8f8b4fa96ae1493d76b463787: 32d97e61743fccf6d32da7a407cb944cdd5c52aa0de4e874e2c78dadf7892a908: 321ed8c579fb458cf9d641499610990c325930a6b642ae4ae2c09fdf055db9769: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash a725a4fc38f9ab511b484535b065f2f1d402485b98d909de2b2560ef782dde90
The earliest published head that covers this entry
- tree_
size - 2161
- signed at
- 26 Sept 2026, 05:32 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash 08d42dfc1a68825e48c5ebd6ef8deb02090b8acb5d1f2be9a9e2101b015a8fb2- signature
dB1NOOKbGZYlf8tpl8m7au97B5M49+4SOWOT1aR1A4WPqRzn123pmio+rP0C6SWMEK2kx1MBdDcTjVaJKZkTAA==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10