← the log
sequence 38

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_hash7b852bad26aa. The chained hash of entry 38, which is what every proof on this page is about.REAL_UTC
sequence_number
38
entry_type
delphi.question.published
entity_type
forecast_question
entity_id
4e06eb7d-ce53-4631-86d8-403a4f841a49
logged_at
2026-08-15T15:53:36.698311+00:00
previous_hash
a4eec9d5687066b4271702f1354c69513fb0acb0742c7655e94221198e3ab326
payload_hash
7f7219d08c5f7d4cf9aef5c380d2af15aa0499ea562ef88ae249a7e52966818d
entry_hash
7b852bad26aa0a6204910f3163b37018626f8dfc3cea4f47833cc835b9e13ea3

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

02. Link to this band.

Payload

{
  "slug": "will-spacex-conduct-starship-flight-14-on-or-before-30-september-2026",
  "title": "Will SpaceX conduct Starship Flight 14 on or before 30 September 2026?",
  "origin": "EDITORIAL",
  "timebase": {
    "clock": "REAL_UTC"
  },
  "closes_at": "2026-08-27T12:00:00.000000Z",
  "opened_at": "2026-08-15T15:53:36.695426Z",
  "blind_mode": true,
  "provenance": "PUBLIC_RECORD",
  "description": "Flight 13 flew on 24 July 2026 carrying a Starlink V3 payload. Regulatory filings point at 28 August as the earliest date for Flight 14. Starship dates have slipped more often than they have held.",
  "question_id": "4e06eb7d-ce53-4631-86d8-403a4f841a49",
  "resolution_criteria": "YES if a launch designated Flight 14 lifts off from the pad on or before 30 September 2026. An abort before liftoff does not count; a failure after liftoff counts as having taken place.",
  "expected_resolution_at": "2026-10-01T12:00:00.000000Z",
  "canonical_source_policy": "SpaceX Starship page at https://www.spacex.com/vehicles/starship/ and SpaceX mission announcements.",
  "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
38
tree_size
181
leaf_hash
947de5cbb6310237e248847ceb889b2f0eb7c43c62871848f95b7b8305ff9469
audit_path (8)
0: 7d3f5f5b8ac67482a23a730090c9743f7aabb4044f3eef028f21e0370014fae71: bd4fac68811616a21a10bbc7952cb9a77cafea3681363657553ccfb798b3c7282: 8bd080f4ed42c8a0c15fc00fd68b411b9fc620b2129bfdc09976569fb60fd1663: e0fd32a6c37370ab40664c7f00dd10aa97f83f28e9593d5626d8ca57a96fe3ca4: 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