← the log
sequence 16

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_hash5f1a3823ea39. The chained hash of entry 16, which is what every proof on this page is about.REAL_UTC
sequence_number
16
entry_type
delphi.question.published
entity_type
forecast_question
entity_id
a1fe265a-83a7-4cf7-a06c-81aea258e90c
logged_at
2026-08-15T15:53:35.658024+00:00
previous_hash
8f34c6524cdde495d3424a5d4adbbc8d2adae24e39103726737cf22e04931469
payload_hash
7ec0ffb6f9a3e280b9fee89ab6af0d4dfd1221e43107cf71e897375013dcd7b2
entry_hash
5f1a3823ea39281555a5107e6562439afbac773145bfadc40b9b27401eb182a1

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

02. Link to this band.

Payload

{
  "slug": "will-the-democratic-party-hold-a-house-majority-after-the-3-november-2026-midterms",
  "title": "Will the Democratic Party hold a House majority after the 3 November 2026 midterms?",
  "origin": "EDITORIAL",
  "timebase": {
    "clock": "REAL_UTC"
  },
  "closes_at": "2026-11-03T11:00:00.000000Z",
  "opened_at": "2026-08-15T15:53:35.655107Z",
  "blind_mode": true,
  "provenance": "PUBLIC_RECORD",
  "description": "All 435 seats in the US House are contested on 3 November 2026. This asks about the certified outcome rather than about election-night calls, which is why it resolves in mid-December.",
  "question_id": "a1fe265a-83a7-4cf7-a06c-81aea258e90c",
  "resolution_criteria": "YES if Democrats hold at least 218 of 435 seats measured against results certified by state election authorities as of 15 December 2026. Later special elections and party switches do not count.",
  "expected_resolution_at": "2026-12-15T12:00:00.000000Z",
  "canonical_source_policy": "Certified state results and the official tally published by the Clerk of the US House at https://clerk.house.gov/.",
  "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
16
tree_size
179
leaf_hash
93d0628a6d0e10cde352e2aa491889809ea21a955a0d1b15739983b96343bac7
audit_path (8)
0: df75633ea197e83c146930f9ad6265246baa0a5ad2b8e2a3c6394e9156d5cd021: 6c66d1127780410166b27cc3e9b2fee0ca1db0112ccfa151ee10ed7c9b6db1ae2: adcdadb2d60b76a9e240f202345392ca06f68766269a64f4cf21691f112d152f3: e4b9ee89b03a1049049e4b184c49c6dae3ebfbec9a890141323ea71fdb33b0ed4: 7d6682fa6e600d077f7841e30621efe19877a3f61ce600d24a3eb3948d17dd255: b74c92a6356a40d4a8987db99772ead75d18bf349905054ba53bbc3401d9b2b96: 432b3bec17cc8d9bd118f5d2d11fc56d0578ec1940af60be2192f2f1b8d43dc67: 3f76b135a3f3ce5dc862e0e2e004c9eff2bbf99040ca47c64d64cec42062fd34
root_hash
b6268ac6224d3cfeaf4fdd2e07881a4bb21cf8ed320580fb2a683f4427a55006

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