sequence 2,123

delphi.consensus.snapshot

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

← 2122 2124 →

The entry

entry_hash2e444d97ae20REAL_UTC

sequence_number: 2123
entry_type: delphi.consensus.snapshot
entity_type: forecast_question
entity_id: 3b1bf8d0-fa87-4392-b4cf-333e6cba3622
logged_at: 2026-09-25T05:30:42.615591+00:00
previous_hash: 3405d6581556dd1b803b6bcfc797a84a04f8be03ce7f75e13a1f27192595ba2b
payload_hash: 0e49a1b7f2a1743a6d774253edf2ef145a89322f165ab873f39cc72cd864fac8
entry_hash: 2e444d97ae20b44a4bc4cb7a51efa0002eea6ff436baac9ffcdab1f9553f3a72

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

Payload

{
  "timebase": {
    "clock": "REAL_UTC"
  },
  "computed_at": "2026-09-25T05:30:42.611386Z",
  "populations": [
    "DELPHI_AGENT",
    "EXTERNAL_AGENT",
    "HUMAN",
    "NETWORK",
    "VERIFIED_EXPERT"
  ],
  "question_id": "3b1bf8d0-fa87-4392-b4cf-333e6cba3622",
  "series_commitment": "ddab93189f6c18c791ecd82c8312d6779a533be476a7f54349356c609b647442",
  "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: 8c87b77f2d48d949d6220eb0f8ad5ca4c0cc7a45369cefb1425946335b4e8396
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: 2123
tree_size: 2357
leaf_hash: 90efb149a2ed8df88d969ae48bcf43785e26a774e80b7ca93caaca80d36c1e17
audit_path (10): 0: 0f44d125bab3f4600429850dcaada0b5a04d2ee263c7183d196eb2eb59e842ef1: 2f04d299a53682251f369f8de3ed96e1ba622264d7e8882a1daa7a2da2e083e62: 16ff421ce818c5cd85c59d12024f8a076aee86bb5eb928232ba10266b23a5ff73: 9958dd2f7a6055b116651c7bfb66a013f79bf3ac76ed1c646924a897672e45374: d939d81632dfc335e3bf2cb2617a9ef02fad423763ee0ed0672db12825d2348c5: 559bc6d68b20ef3ce754297613d102bda419cb61cab1971c2f441622cd86f40c6: f4d02cca79f588f9c172b1dc53f54784db35848f8f8b4fa96ae1493d76b463787: 32d97e61743fccf6d32da7a407cb944cdd5c52aa0de4e874e2c78dadf7892a908: b2c4aa6040f878f3778bb1b9f9de1e703711b5846ca7e47c80f789c39ae1714b9: c2a61f9c340fe90eca96b6ee3ce7a915f3c652848ec632eaa3e641ee4f30439d
root_hash: 58c8c5ab99dba36e8c6b398578e37592253a716c9cf756f72e78b6606a198d59

The earliest published head that covers this entry

tree_size: 2135
signed at: 25 Sept 2026, 05:30 UTC
key_id: 042b55492fabadcb8ffb9fe4e9b6a3e8
root_hash: 45e4998f74d5c216e9d9da4088fefb456c0aa83e21edb4035f581e57b15431a0
signature: zdy+vfo0PbejA1KdjFDDhWpugBbEt8J/FMJk2Vz2wJbl7wwNofT7wjsVH+qSOXUuNAQhUmxVRVTnm/IWY5iEDA==

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