← the log
sequence 22

delphi.question.published

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.

01. Link to this band.

The entry

entry_hash0ab2c44ea976. The chained hash of entry 22, which is what every proof on this page is about.REAL_UTC
sequence_number
22
entry_type
delphi.question.published
entity_type
forecast_question
entity_id
f9f31c96-d8da-4945-9cc5-157c16ffb7a9
logged_at
2026-08-15T15:53:35.899765+00:00
previous_hash
e227fc9279a7c4af43461d3d69860d0ca75abab22268d967866c4e2a04d25f66
payload_hash
2dae569818403cf468fe8d022fe57041add03392f3ca7ab3f83d7eca68226c94
entry_hash
0ab2c44ea97681d7c17c7500b84e2a043748abb0a8728de6b69f173d8cc71ee2

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

02. Link to this band.

Payload

{
  "slug": "will-cop31-in-antalya-adopt-its-final-decision-text-on-or-before-20-november-2026",
  "title": "Will COP31 in Antalya adopt its final decision text on or before 20 November 2026?",
  "origin": "EDITORIAL",
  "timebase": {
    "clock": "REAL_UTC"
  },
  "closes_at": "2026-11-09T12:00:00.000000Z",
  "opened_at": "2026-08-15T15:53:35.896682Z",
  "blind_mode": true,
  "provenance": "PUBLIC_RECORD",
  "description": "COP31 runs from 9 to 20 November 2026 in Antalya. Climate conferences routinely overrun their scheduled close by a day or more, which is exactly what makes the scheduled date a question rather than a formality.",
  "question_id": "f9f31c96-d8da-4945-9cc5-157c16ffb7a9",
  "resolution_criteria": "YES if the UNFCCC secretariat publishes an adopted final decision text dated 20 November 2026 or earlier. Adoption spilling into 21 November or later resolves NO.",
  "expected_resolution_at": "2026-11-23T12:00:00.000000Z",
  "canonical_source_policy": "UNFCCC COP31 official decisions page at https://unfccc.int/cop31.",
  "resolution_rule_revision": 1
}

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.

03. Link to this band.

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
22
tree_size
179
leaf_hash
766ffe3db07aea31fc11f4c23122053a1cea10d266ecea981f4fcd9d703ca458
audit_path (8)
0: 2e6c86f2ec5e86318081f6f6e3bfd8357228794a5c6d089d3e1e9106de0367ca1: 8a2454cf872abe3c3c4a946762cbf0a02c2f53c6df59ee03383aa7dd07e582ae2: fff3ff54516ca778b8e41f50d52d7589f9d0bba05294a5394fc970f39a5e3fd13: e4b9ee89b03a1049049e4b184c49c6dae3ebfbec9a890141323ea71fdb33b0ed4: 7d6682fa6e600d077f7841e30621efe19877a3f61ce600d24a3eb3948d17dd255: b74c92a6356a40d4a8987db99772ead75d18bf349905054ba53bbc3401d9b2b96: 432b3bec17cc8d9bd118f5d2d11fc56d0578ec1940af60be2192f2f1b8d43dc67: 3f76b135a3f3ce5dc862e0e2e004c9eff2bbf99040ca47c64d64cec42062fd34
root_hash
b6268ac6224d3cfeaf4fdd2e07881a4bb21cf8ed320580fb2a683f4427a55006

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