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.
The entry
- sequence_
number - 24
- entry_
type delphi.question.published- entity_
type forecast_question - entity_
id 7fc5454c-0827-492e-a574-d01f70586fc4- logged_
at 2026-08-15T15:53:36.027254+00:00- previous_
hash 318d368a51ecf9b10b33a903236d61a95a71cc56188db1396323c7fb3c6b6fb7- payload_
hash bdabffb95bf4af9d17042c9d7ed27d0f6575541c275836828c2abcebffc145ed- entry_
hash bd4921e10ae2436898078181f43cf55a0eaaa08f56996f9d0441a2c2d9b8d31e
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"slug": "will-the-eu-council-adopt-a-new-russia-sanctions-package-before-the-end-of-2026",
"title": "Will the EU Council adopt a new Russia sanctions package before the end of 2026?",
"origin": "EDITORIAL",
"timebase": {
"clock": "REAL_UTC"
},
"closes_at": "2026-09-01T12:00:00.000000Z",
"opened_at": "2026-08-15T15:53:36.024088Z",
"blind_mode": true,
"provenance": "PUBLIC_RECORD",
"description": "The Council has adopted successive sanctions packages against Russia since 2022. This asks whether another one lands in the final four months of 2026.",
"question_id": "7fc5454c-0827-492e-a574-d01f70586fc4",
"resolution_criteria": "YES if a legal act described as a new sanctions package against Russia, or extending restrictive measures with new listings, is published in the Official Journal of the EU with a date between 1 September and 31 December 2026.",
"expected_resolution_at": "2027-01-05T12:00:00.000000Z",
"canonical_source_policy": "Council of the EU sanctions pages at https://www.consilium.europa.eu/en/policies/sanctions/ and the Official Journal on EUR-Lex.",
"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
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 - 24
- tree_
size - 179
- leaf_
hash 2e6f0ec75e58532f4aa20068c0c1760fbb6bcd974a9f12079242bdfb0db9f17e- audit_
path (8) 0: be8b521a51d7955356ca8152729ba5c5827596c644b2c867e03f54039c0b16ef1: 333f9068158c4bda2f641d8ba1d6c16194b533514d3249c8c7242a06baddf39a2: 9388af5d6c467dfae025223077240609a9f56df811b859f128b52d504c7444693: 1cf5d64fb4965f4940c526fa698108d7c4578146408b3cd51dabd149d5674bd74: 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