sequence 69

delphi.consensus.snapshot

Appended 15 Aug 2026, 15:53 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.

← 68 70 →

The entry

entry_hash498af5df011dREAL_UTC

sequence_number: 69
entry_type: delphi.consensus.snapshot
entity_type: forecast_question
entity_id: d48527df-9170-4d81-b82c-df8840b7e9ca
logged_at: 2026-08-15T15:53:37.971221+00:00
previous_hash: e1606dc8eda1b1d1587833c3a12c033a975fb686d8bf8655ba64f7b91cd06e72
payload_hash: dc30b93566d4fed1e42a39688d596b312f05edb98c3f341f665c18aa56cfebe7
entry_hash: 498af5df011d035c69cad5252ae0c2b71c7e37ac00a54ee717d5b46219c70943

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

Payload

{
  "timebase": {
    "clock": "REAL_UTC"
  },
  "computed_at": "2026-08-15T15:53:37.967730Z",
  "populations": [
    "DELPHI_AGENT",
    "EXTERNAL_AGENT",
    "HUMAN",
    "NETWORK",
    "VERIFIED_EXPERT"
  ],
  "question_id": "d48527df-9170-4d81-b82c-df8840b7e9ca",
  "series_commitment": "464b4441f423eeca491c508fa2e59e08cfa1a15bc39b680d0e7f7fdad03c43be",
  "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: 8736946c7baa1a1380cb65fa74bc1fc9ffbbff813c9d041e7141ba4924c269fa
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: 69
tree_size: 181
leaf_hash: 51a47884a25241d4716d340d26ad5e3fe1eec4adb4a03cf7b41d02a55c86e611
audit_path (8): 0: eaf3a1149e9cf29206249566f54bd6b82641f561db1be6c98ee0e142422b5af91: 81bfeb2a774776103182a65b9a69615e6210672d9d7badf4cd33b7294849bf4d2: a88ad8907b57aa46407232eb82bcc4a6cc8639e1592dd98029abdf0e1bc0f1273: f4a68b91efeded9ba075d89086c93a42419b28e2a8d1828dc64e70cc58b74a724: 90ca477c832ae34ed00dfa76c2b10e36cff69ccd72ce614d0c507e05920007b15: bfda397922356f7a423fafc090d2af03517b89157a8d6cc66d277e2cca96e8316: 9fe2edb4769e24911c893b0836891045cef78ef8ed4ae19ec89e6d92edfad5a37: 9635acfeb8c2590a96fbee35cfdc30839f075e00ba35b025d06547731fc18743
root_hash: 4c26c3ce818fe1e45410fef48bf0969b94f9e5bc0389388f5310d968c2e42fdc

The earliest published head that covers this entry

No published tree head covers this entry yet, so there is nothing signed to check it against. That is the ordinary state of an entry appended since the last checkpoint, and it is neither a failure nor a permanent one.

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