← the log
sequence 30

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_hashd70c6c175968. The chained hash of entry 30, which is what every proof on this page is about.REAL_UTC
sequence_number
30
entry_type
delphi.question.published
entity_type
forecast_question
entity_id
d1b83331-68f7-4be7-a625-f7824bccab5b
logged_at
2026-08-15T15:53:36.280206+00:00
previous_hash
26c6bb7b492a0ecbbf52cc9af5b9faa201a647d3749c05190dbe9840b45654a7
payload_hash
9acdd1939813816c740d70a6b789348873e61b80d948cad362b6b9dd962c9904
entry_hash
d70c6c175968feab6d0b165cadeb1e8bb36beac9a07978b5d530364457a571d1

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

02. Link to this band.

Payload

{
  "slug": "will-openai-s-form-s-1-become-publicly-available-on-sec-edgar-before-2027",
  "title": "Will OpenAI's Form S-1 become publicly available on SEC EDGAR before 2027?",
  "origin": "EDITORIAL",
  "timebase": {
    "clock": "REAL_UTC"
  },
  "closes_at": "2026-09-15T22:00:00.000000Z",
  "opened_at": "2026-08-15T15:53:36.275915Z",
  "blind_mode": true,
  "provenance": "PUBLIC_RECORD",
  "description": "OpenAI filed confidentially on 8 June 2026. Confidential filings become public when the company chooses to flip them, typically weeks before a listing. Reports since have pointed both at a fourth-quarter listing and at a slip into 2027.",
  "question_id": "d1b83331-68f7-4be7-a625-f7824bccab5b",
  "resolution_criteria": "YES if a publicly viewable Form S-1 or S-1/A for OpenAI is retrievable on sec.gov with a filing date on or before 31 December 2026. A confidential submission that is not public does not count.",
  "expected_resolution_at": "2027-01-05T12:00:00.000000Z",
  "canonical_source_policy": "SEC EDGAR full-text search at https://www.sec.gov/edgar/search/.",
  "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
30
tree_size
181
leaf_hash
3366bb69eafd9e38b432391de4950487cb219b7c1ec263fcc03f973382c5195c
audit_path (8)
0: 36d01af729226ccf32bd19ad6e2fb3c8a73d8032ca9d5b561d027a3abe67a09e1: 5a2c1bfe26f42ba3d0f5896932755af01b75aa485207f715c1cb9c4dd044292b2: 1bab8e6b1385cbd43dadbbe19c62fa5e79c714dc2ed265dd3bc33b2b34b507c93: 1cf5d64fb4965f4940c526fa698108d7c4578146408b3cd51dabd149d5674bd74: 7d6682fa6e600d077f7841e30621efe19877a3f61ce600d24a3eb3948d17dd255: b74c92a6356a40d4a8987db99772ead75d18bf349905054ba53bbc3401d9b2b96: 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