← the log
sequence 18

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_hashf85b266cb8f2. The chained hash of entry 18, which is what every proof on this page is about.REAL_UTC
sequence_number
18
entry_type
delphi.question.published
entity_type
forecast_question
entity_id
1d7c973e-1d2e-40a2-8242-236a5a5201b9
logged_at
2026-08-15T15:53:35.735746+00:00
previous_hash
b8c7782c81acbe5d0217ae2d33ca3c4849f19186024ca95b74bffe0a16e934f3
payload_hash
0e1baa43862b6a4ed47076f860213c1e4e29c992369bc10ee50166ab0e5af380
entry_hash
f85b266cb8f27f6eeed49fc5e54113f8736d91920c4a1f8cbb0a22a888ffb6f2

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

02. Link to this band.

Payload

{
  "slug": "will-republicans-hold-at-least-51-us-senate-seats-after-the-3-november-2026-midterms",
  "title": "Will Republicans hold at least 51 US Senate seats 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.732775Z",
  "blind_mode": true,
  "provenance": "PUBLIC_RECORD",
  "description": "Thirty-five Senate seats are contested on 3 November 2026, including two special elections. Fifty-one is asked rather than fifty because the vice-presidential tie-break is not a seat.",
  "question_id": "1d7c973e-1d2e-40a2-8242-236a5a5201b9",
  "resolution_criteria": "YES if Republicans hold at least 51 seats measured against results certified by state election authorities as of 15 December 2026. The vice president's tie-breaking vote does not count as a seat.",
  "expected_resolution_at": "2026-12-15T12:00:00.000000Z",
  "canonical_source_policy": "Certified state results and the official Senate membership listing at https://www.senate.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
18
tree_size
179
leaf_hash
2ec5cfe219f42dbbf28ea2693ddb8bf7759397a50607255085c84848432584ff
audit_path (8)
0: ac209c84a3f2c18cb3cbba7d0afad1b25bd994bc8742ac26e7b4bb6231a470231: beee25a79b059f21e0135b701aa59489569fa761e653b7e1bb4a76419ad88eb62: 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