← the log
sequence 44

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_hash3635fcc77164. The chained hash of entry 44, which is what every proof on this page is about.REAL_UTC
sequence_number
44
entry_type
delphi.question.published
entity_type
forecast_question
entity_id
4bfc7aa0-f12f-479c-ba06-d8e4cebfe625
logged_at
2026-08-15T15:53:36.943773+00:00
previous_hash
2797ace22adea03f3444abc36db8a5543ab1ec7e7b5cd7220ada502a7e72993c
payload_hash
d4d70e9869e0f16a1904de3f9218cff6907b7a625c29ff791562f2ed4e806efd
entry_hash
3635fcc77164be69426318c43eff2ec4d37efc1210fb76289cb3fa4844c351c7

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

02. Link to this band.

Payload

{
  "slug": "will-the-2026-nobel-prize-in-literature-go-to-a-writer-publishing-mainly-outside-english",
  "title": "Will the 2026 Nobel Prize in Literature go to a writer publishing mainly outside English?",
  "origin": "EDITORIAL",
  "timebase": {
    "clock": "REAL_UTC"
  },
  "closes_at": "2026-10-08T09:00:00.000000Z",
  "opened_at": "2026-08-15T15:53:36.939311Z",
  "blind_mode": true,
  "provenance": "PUBLIC_RECORD",
  "description": "The Swedish Academy announces the literature laureate on 8 October 2026. The prize has alternated between English-language and other-language laureates without a stable pattern.",
  "question_id": "4bfc7aa0-f12f-479c-ba06-d8e4cebfe625",
  "resolution_criteria": "YES if the laureate announced on 8 October 2026 is a writer whose work is predominantly published in a language other than English, as described on nobelprize.org.",
  "expected_resolution_at": "2026-10-08T14:00:00.000000Z",
  "canonical_source_policy": "Official announcement at https://www.nobelprize.org/prizes/literature/2026/.",
  "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
44
tree_size
181
leaf_hash
6e18522043d747efe91b5321eae60d25a294596a0988dd8ac71c5459e606ce19
audit_path (8)
0: 7942e17264d0470982b4fcb515fa0a178f589a1b30ecd85a243c87b3acf28fbd1: ad36da04017902e966bff76992f4c65ee608b90600c74484f26cda173e4991f82: 79b53e1f98697a1bd4aad9267d101adf9029f4aa753b53e2269c35a284aa18a83: eaeacbd8d319b9d776cf6f767329e32539ccecb621836ffea46c36ad501849234: 44572e1f9d85cea0b2eeaa0aa227d6fb80c1e5448efb5228f587d667c12052dd5: 0dec549ee6527dafc0e801068f2df8c4eef8fcb9972397c6eb58217673bbfe9c6: 432b3bec17cc8d9bd118f5d2d11fc56d0578ec1940af60be2192f2f1b8d43dc67: 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