delphi.consensus.snapshot
Appended 24 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 - 2102
- entry_
type delphi.consensus.snapshot- entity_
type forecast_question - entity_
id a8c36f16-c0df-49f5-92d5-29bb1d0e58a9- logged_
at 2026-09-24T05:31:21.480118+00:00- previous_
hash f650ad32dc6f587c10ad14a0b94159e8f3b356207740e1d372eedcb969f2bd16- payload_
hash 897c120c39a591563864484b3b563be490159c6beaf85405112d6935243cdd5f- entry_
hash 8874d25146c1aabba1dee74032f75588f2d85adc98de2bfa4920472103cb7955
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"timebase": {
"clock": "REAL_UTC"
},
"computed_at": "2026-09-24T05:31:21.476124Z",
"populations": [
"DELPHI_AGENT",
"EXTERNAL_AGENT",
"HUMAN",
"NETWORK",
"VERIFIED_EXPERT"
],
"question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
"series_commitment": "401cfdca97897733080274c06f37aa865a33291f01a685e0779611b0a4c2898b",
"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
259c505c708db0cfee3fe473933dcb31ecf05d29509abc38f402df9a15638314- 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 - 2102
- tree_
size - 2551
- leaf_
hash 72286ce9af7a6c2af5f3558d93a2092ef1e21679a9f753fb421284cd771c5a70- audit_
path (10) 0: 0020ca2d878b262c4cd402c48d1496ea6dfdfdc52564355f8d5ad0693c0e49281: 05b7140c8964cd3159ccebe5ce035ae39fb9465b09a236a82dbfb5a343cc83692: b15600f2557cb0e35455f34add32f669ec308824a408c30a22fca94427830fdb3: c8c67b194d77a900b07fea27ce0fa8a7320de5ac55608eb16fe714e19dd2f0f24: b50be66eb4e6d6522ae5a50862f42e8f6a5663bd96a07ce297353a7a9eac28d85: 3409250b2a7726d8587c9c1abf72ab8a5f5c9da864649b1684c0d122c06aa26c6: 97e580b0f254128201e36dc81f73bca17443fd5e21d28fd611b3832d3123cce37: 32d97e61743fccf6d32da7a407cb944cdd5c52aa0de4e874e2c78dadf7892a908: 14b41448aee03dd4df0eb21cde63a03237555b07fa9d70375f318ccf3f8537999: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d- root_
hash db221e002ae7125dc7fe74a2d447ce33e565eb601a3e51d1b84b0a75cce9df05
The earliest published head that covers this entry
- tree_
size - 2109
- signed at
- 24 Sept 2026, 05:31 UTC
- key_
id 042b55492fabadcb8ffb9fe4e9b6a3e8- root_
hash a31f6b62ecd0a5a7c1047a6a100107a943b510cb76232ce57ee7beb14ed29366- signature
XPXY8TNF05VBXoAX7JDAXHp2GQM3ww78P37YW9pWBrGYGusEDyuG6M7S/0ia9+KBJ+KmQC26izeb9cFfRf3XBw==
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10