← the log
sequence 20

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_hashbcf0243eb3ed. The chained hash of entry 20, which is what every proof on this page is about.REAL_UTC
sequence_number
20
entry_type
delphi.question.published
entity_type
forecast_question
entity_id
28453d7d-6676-414d-a36b-2fcf2cf13265
logged_at
2026-08-15T15:53:35.814002+00:00
previous_hash
bc0822defd14f883ea2ff3303b71a1f654de4dbd8dc11701b44ec913fadb4aa7
payload_hash
e7c7f54a986eb17021e4459f21be11efad2118d6dfcf91757a61ca03a022657b
entry_hash
bcf0243eb3edd56523057d527e924b66ec4b4475fbb1859da47499b9e5aefd67

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

02. Link to this band.

Payload

{
  "slug": "will-the-un-general-assembly-adopt-a-resolution-on-ukraine-before-the-end-of-2026",
  "title": "Will the UN General Assembly adopt a resolution on Ukraine before the end of 2026?",
  "origin": "EDITORIAL",
  "timebase": {
    "clock": "REAL_UTC"
  },
  "closes_at": "2026-09-08T12:00:00.000000Z",
  "opened_at": "2026-08-15T15:53:35.810908Z",
  "blind_mode": true,
  "provenance": "PUBLIC_RECORD",
  "description": "The 81st session of the General Assembly opens on 8 September 2026. This asks whether the Assembly returns to Ukraine in a formal adopted resolution during the remainder of the calendar year.",
  "question_id": "28453d7d-6676-414d-a36b-2fcf2cf13265",
  "resolution_criteria": "YES if the official resolution index for the 81st session lists at least one adopted resolution whose title refers to Ukraine, adopted between 8 September and 31 December 2026.",
  "expected_resolution_at": "2027-01-05T12:00:00.000000Z",
  "canonical_source_policy": "Official resolution index of the 81st UN General Assembly session at https://www.un.org/en/ga/81/.",
  "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
20
tree_size
179
leaf_hash
085ffef0d20f3b42dc8c29dc574983e9828e3fb13c5fcb8163fc5c8b96af5180
audit_path (8)
0: 0011d6cd00b47ffe57ad6f7209e4857f07a79e56a2c35ef63146d35ed880e4901: 2f08fcac42823221564dd36e63a81a14a39ecb043fcb9addb4a658669178ee632: 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