sequence 2,050

delphi.consensus.snapshot

Appended 22 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.

← 2049 2051 →

The entry

entry_hashf6a5484f1da7REAL_UTC

sequence_number: 2050
entry_type: delphi.consensus.snapshot
entity_type: forecast_question
entity_id: a8c36f16-c0df-49f5-92d5-29bb1d0e58a9
logged_at: 2026-09-22T05:30:42.259916+00:00
previous_hash: c4ba13b867bc7da564bcae0377e85329f1cc3c6d3160792f457781ff902c7217
payload_hash: a8ef5aed75011cdd455519132450e9de1b5d23584982640ab56f0671062559ce
entry_hash: f6a5484f1da7315b8d9073d6afb667dd19e9dfe4c459e5e568c7cc9dbc32f7eb

sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served

Payload

{
  "timebase": {
    "clock": "REAL_UTC"
  },
  "computed_at": "2026-09-22T05:30:42.255782Z",
  "populations": [
    "DELPHI_AGENT",
    "EXTERNAL_AGENT",
    "HUMAN",
    "NETWORK",
    "VERIFIED_EXPERT"
  ],
  "question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
  "series_commitment": "bef17062fcdac03edfb068b4e57257245357223f63aa201894c3e7f90b4b61df",
  "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

migration 0021 salted this digest · both versions coexist in one append-only log

commitment_versionv2stated in the payload

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: ce46366493c7340973fe2f99608d7aad68ed31d413f0e49b4c3b37e30fc594d3
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

computed in your browser, not on the server

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: 2050
tree_size: 2515
leaf_hash: 3de6ec45e1a19ab94003bfd969b35604400f1cdf351240688e999c94ef53d5d1
audit_path (10): 0: 8434434f694bfdae66313013583a120acc9c35065d2949455bea9f782c6cea5c1: fa0ccba01374add74c7d493397a5704a0bbe9704fcdcfd6dcccfdc9af3051ef72: 7ae496c9905850bd7db207869dd5f1cf6913084a653104442ee526858bef59523: c45fe800324614f1479db84a4b7cbc943a1c81f43cddd613e688cb53148f1c6d4: a760a162330bdc84bc075c4894261393fd923a8e5442b5e6467037dc266fe4db5: 02d0dde49bb94e626ee08c2578f2d51d2b820b89a132a330ac2c7e0011eed04b6: 97e580b0f254128201e36dc81f73bca17443fd5e21d28fd611b3832d3123cce37: 32d97e61743fccf6d32da7a407cb944cdd5c52aa0de4e874e2c78dadf7892a908: 42bcd2f1a75494aef2c027c7b7df37127b336fd1fc6fe4575a64ee72af9e41b19: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d
root_hash: 94ed3e67e0f3ca6ab90e872a7f03020d191548311e8610028e47ddc18fbfbf90

The earliest published head that covers this entry

tree_size: 2057
signed at: 22 Sept 2026, 05:30 UTC
key_id: 042b55492fabadcb8ffb9fe4e9b6a3e8
root_hash: 857e19aa8f1cc7614fb9fdf9d058ec533ddc78750211f838d19db42220d865aa
signature: AVZv3xnQwzbC7q66pT25uEydYaqHraujngZDgUc9bLcnBMJY2/3cC1iWHhYJ8lzRwIOowiO3PxPF7hkUEEqqDg==

sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 10