sequence 8

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.

← 7 9 →

The entry

entry_hash24ff6b1da5a1REAL_UTC

sequence_number: 8
entry_type: delphi.question.published
entity_type: forecast_question
entity_id: 54324c2e-b8fd-4bfd-afc4-1b6e799c095d
logged_at: 2026-08-15T15:53:35.282526+00:00
previous_hash: d8ffe3d33e7bcd9ab3dfa6dffa2216ff81feafbd9896ffe9d0c450c3b815360e
payload_hash: 3e719e432c09d0dc2422b0e21fb9217189868c116f3788d9c3a98c563c059f41
entry_hash: 24ff6b1da5a1dd07ab0e1a9e3a7fdc353d257742823941ee7c24037076655e05

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

Payload

{
  "slug": "will-the-afd-receive-the-highest-second-vote-share-in-saxony-anhalt-on-6-september-2026",
  "title": "Will the AfD receive the highest second-vote share in Saxony-Anhalt on 6 September 2026?",
  "origin": "EDITORIAL",
  "timebase": {
    "clock": "REAL_UTC"
  },
  "closes_at": "2026-09-06T16:00:00.000000Z",
  "opened_at": "2026-08-15T15:53:35.278633Z",
  "blind_mode": true,
  "provenance": "PUBLIC_RECORD",
  "description": "Saxony-Anhalt elects its state parliament on 6 September 2026. This asks only which party takes the largest share of second votes, not who forms a government.",
  "question_id": "54324c2e-b8fd-4bfd-afc4-1b6e799c095d",
  "resolution_criteria": "YES if the AfD holds the highest second-vote share of any party in the preliminary official result published by the Landeswahlleiter of Saxony-Anhalt.",
  "expected_resolution_at": "2026-09-07T12:00:00.000000Z",
  "canonical_source_policy": "Preliminary official result published by the Landeswahlleiter Sachsen-Anhalt on its official results page.",
  "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.

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: 8
tree_size: 179
leaf_hash: 7d5f54d357cfcc5ee71f29c8ef3513154e7a9b7ff810ac46ba05a08529b21fbd
audit_path (8): 0: aedc57254ec5a19a16edd4d8c549c05f15e8216901efc7d0373bd0021c58a0231: beaa5d72afc1a4ef2c9b347bdcae7ea49947b9314f9d24d611216f673a403df42: a77f24677127c7bb35e52e72ee1428c6a7bfe467916fe7deeba51f69a6c00b483: d7c05425bf6e3fadbed68d9552781d28647454d6dad43f268ec9145a2b4220fe4: b70d290aa081a17cfd1dd59b61f1a28551b4aa8df2915bb773f8eda8b60841055: 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