← the log
sequence 34

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_hash096d9bb3aeff. The chained hash of entry 34, which is what every proof on this page is about.REAL_UTC
sequence_number
34
entry_type
delphi.question.published
entity_type
forecast_question
entity_id
e732630b-b551-4965-92e6-7168c5a86d89
logged_at
2026-08-15T15:53:36.496156+00:00
previous_hash
f9424d4774c10347afdd1c98d28f1ef3c6afd82ddd912e1ec0c2efab05518c70
payload_hash
d45a3e5ed499905bbe4227a903c8a4e9e0cd33111fc7fd9c56e349bfc8ebb0b8
entry_hash
096d9bb3aeff05194f85f542b9abe4fa8182761fda6dc89366efd4fe16adeb0b

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

02. Link to this band.

Payload

{
  "slug": "will-databricks-publicly-file-a-form-s-1-with-the-sec-before-2027",
  "title": "Will Databricks publicly file a Form S-1 with the SEC before 2027?",
  "origin": "EDITORIAL",
  "timebase": {
    "clock": "REAL_UTC"
  },
  "closes_at": "2026-09-15T22:00:00.000000Z",
  "opened_at": "2026-08-15T15:53:36.493438Z",
  "blind_mode": true,
  "provenance": "PUBLIC_RECORD",
  "description": "Databricks closed a five billion dollar private round at a 190 billion valuation on 13 August 2026, and its chief executive has publicly ruled out a 2026 listing. Stated intentions and filings do occasionally diverge.",
  "question_id": "e732630b-b551-4965-92e6-7168c5a86d89",
  "resolution_criteria": "YES if a publicly viewable Form S-1 for Databricks is retrievable on sec.gov with a filing date on or before 31 December 2026.",
  "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
34
tree_size
181
leaf_hash
5cd0ca259de00fa967a57b75cb0120bf61ff138e8adf5ea4870b7da749ff818d
audit_path (8)
0: a13b4d2f403744b3441b8d3353c50855d77f7ff28fa5a8175be821f3894f4fe71: 78ea0e84b81409b5996f39f9c1f4b15f390ab1a130a0af2b8a28b421b7abfe102: a8f494186f033c69dd6178c0d51ad1f52e2f7902e8f7078f60a4b76eaf5a65e03: 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