← the log
sequence 64

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_hash5a21988be4c8. The chained hash of entry 64, which is what every proof on this page is about.REAL_UTC
sequence_number
64
entry_type
delphi.question.published
entity_type
forecast_question
entity_id
5b5159a4-bb59-4118-9569-40a0e89836ee
logged_at
2026-08-15T15:53:37.788929+00:00
previous_hash
16e01d65b0553a0bbc96a1e3cca22b72e97130d48dc1b5292fe3f3f509f89bd1
payload_hash
317f6e1ca42fe90059f7fc8dd8be1c4df64c50c918bb72a9c52d2710a6a367e2
entry_hash
5a21988be4c8eb19bf0c4d865de72f0675c4144a71457c90769e0b5ac3b60a13

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

02. Link to this band.

Payload

{
  "slug": "will-the-2026-ballon-d-or-go-to-a-player-of-the-spain-national-team",
  "title": "Will the 2026 Ballon d'Or go to a player of the Spain national team?",
  "origin": "EDITORIAL",
  "timebase": {
    "clock": "REAL_UTC"
  },
  "closes_at": "2026-10-26T16:00:00.000000Z",
  "opened_at": "2026-08-15T15:53:37.786315Z",
  "blind_mode": true,
  "provenance": "PUBLIC_RECORD",
  "description": "The ceremony takes place in London on 26 October 2026. Spain won the World Cup on 19 July 2026, beating Argentina one-nil after extra time, and World Cup years have often favoured players from the winning side.",
  "question_id": "5b5159a4-bb59-4118-9569-40a0e89836ee",
  "resolution_criteria": "YES if the winner named on the official Ballon d'Or page is a Spain international at the time of the ceremony on 26 October 2026.",
  "expected_resolution_at": "2026-10-27T12:00:00.000000Z",
  "canonical_source_policy": "Official Ballon d'Or announcement at https://www.uefa.com/ballondor/.",
  "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
64
tree_size
181
leaf_hash
f57639d8c361ba238a0f1ebd28df07e70417ff8aa2cce53b8403bde101e59b1a
audit_path (8)
0: 3ef4acae3ead7615100e09b9c1d022322bf705589e80ed308abf4b4acf95c89b1: 52fee1bedbeec0d4c06138feb32613676b1db03be56c6e112cff42d3b0cd4e982: 40ecbcca1de18289107f2ca219e58a6a6395d60f627d6771a43cf367290f31023: 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