← the log
sequence 46

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_hashf81f5c555c5c. The chained hash of entry 46, which is what every proof on this page is about.REAL_UTC
sequence_number
46
entry_type
delphi.question.published
entity_type
forecast_question
entity_id
a8c36f16-c0df-49f5-92d5-29bb1d0e58a9
logged_at
2026-08-15T15:53:37.023479+00:00
previous_hash
b582ed4ee81ce7ad99003f54700081b0775cdff214e6f731c5c89c944683b57b
payload_hash
d8b383d671376ba7679df1f52200eb7222ea9dbac10c863debcf8d6df5ffca13
entry_hash
f81f5c555c5c1a06fc942be0b4f6347dbd49325da46f6338e6046084f53401f1

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-peace-prize-go-to-an-organisation-rather-than-to-individuals",
  "title": "Will the 2026 Nobel Peace Prize go to an organisation rather than to individuals?",
  "origin": "EDITORIAL",
  "timebase": {
    "clock": "REAL_UTC"
  },
  "closes_at": "2026-10-09T08:00:00.000000Z",
  "opened_at": "2026-08-15T15:53:37.019587Z",
  "blind_mode": true,
  "provenance": "PUBLIC_RECORD",
  "description": "The Norwegian Nobel Committee announces the peace laureate on 9 October 2026. Organisations have taken the prize in roughly a quarter of the years since it was first awarded.",
  "question_id": "a8c36f16-c0df-49f5-92d5-29bb1d0e58a9",
  "resolution_criteria": "YES if the prize is awarded solely to an organisation according to nobelprize.org. A shared award to an organisation and one or more individuals resolves NO.",
  "expected_resolution_at": "2026-10-09T14:00:00.000000Z",
  "canonical_source_policy": "Official announcement at https://www.nobelprize.org/prizes/peace/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
46
tree_size
181
leaf_hash
f4d6394ff87c416b01970c1a4fb0a7646c4527f260d3cbfc5045e2d84c780eba
audit_path (8)
0: 2a81135f24889ea50990fe30983faf02476a15bd9425c50b1a28b44fc63391be1: 79cc50f07d1a18c388c7d3ab2fdcebb5c72b5e89c329eee1a058c6fd931b287e2: 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