← the log
sequence 48

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_hash52cd1c8a9cb0. The chained hash of entry 48, which is what every proof on this page is about.REAL_UTC
sequence_number
48
entry_type
delphi.question.published
entity_type
forecast_question
entity_id
0485b0c1-a674-414e-9778-a898c974bd9d
logged_at
2026-08-15T15:53:37.128408+00:00
previous_hash
ba56bbe3823b0b5d38bbfd8f8813411cd7da59c04f080a107a498dc287920f63
payload_hash
7e71fcf31a1bfdf5021f37b8085cc5f6ef4e7a22e2581880e29d9d3ce97b091b
entry_hash
52cd1c8a9cb09ff218501a3fd4e5369d4f061218fc3089d9f4ec1028f225cbe0

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

02. Link to this band.

Payload

{
  "slug": "will-the-2026-arctic-sea-ice-minimum-fall-below-4-50-million-square-kilometres",
  "title": "Will the 2026 Arctic sea ice minimum fall below 4.50 million square kilometres?",
  "origin": "EDITORIAL",
  "timebase": {
    "clock": "REAL_UTC"
  },
  "closes_at": "2026-09-01T12:00:00.000000Z",
  "opened_at": "2026-08-15T15:53:37.125537Z",
  "blind_mode": true,
  "provenance": "PUBLIC_RECORD",
  "description": "Extent stood at 7.02 million square kilometres on 2 August 2026, the ninth lowest for that date in the satellite record. Seasonal outlooks put the September minimum somewhere between 3.99 and 5.68 million square kilometres.",
  "question_id": "0485b0c1-a674-414e-9778-a898c974bd9d",
  "resolution_criteria": "YES if NSIDC reports the 2026 annual minimum extent as strictly below 4.50 million square kilometres. The confirmed minimum governs, not daily values during the season.",
  "expected_resolution_at": "2026-10-05T12:00:00.000000Z",
  "canonical_source_policy": "NSIDC Sea Ice Today analyses at https://nsidc.org/sea-ice-today/analyses.",
  "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
48
tree_size
181
leaf_hash
b2877129ae69cc147865cdeccdd51cc80076f85e7e89b814c8410c245298c18e
audit_path (8)
0: 7fea16177ef493ab3ccd0b14d8533b98bfcea7d34f37c542dc82d2040132dc251: d68db828e59419a762bf836df25d0387f1cf937c9e958fb685938a519bc346db2: 575d95304450173ca4c6ce66d688d95c5abb0e6b923bcbf1c78a25de9ec4c02a3: 59b626cca7986be0b6ec44fe0d4d89e3fdbd22110dbe11bf0c1a9d22fcaf178b4: 2470c45a41e5b2338cd0a79e1b28f402a0e7e23251bee7ed256b2f8f028ccbe75: 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