sequence 0

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.

1 →

The entry

entry_hashfc38e85ac3ddREAL_UTC

sequence_number: 0
entry_type: delphi.question.published
entity_type: forecast_question
entity_id: 48ef81cc-e8c7-4059-91e1-550a9ffc1391
logged_at: 2026-08-15T15:53:34.861876+00:00
previous_hash: 0000000000000000000000000000000000000000000000000000000000000000
payload_hash: 9ddc30b552df4fa480bbca50931cac2faa2bd72ee70bdc273585cffaf50d1b08
entry_hash: fc38e85ac3ddefc3e3f018aaf59a399ad9e167a370d9c62434b26b6a48cfc402

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

Payload

{
  "slug": "will-euro-area-annual-hicp-inflation-for-august-2026-come-in-at-3-0-or-higher",
  "title": "Will euro-area annual HICP inflation for August 2026 come in at 3.0 % or higher?",
  "origin": "EDITORIAL",
  "timebase": {
    "clock": "REAL_UTC"
  },
  "closes_at": "2026-09-01T07:00:00.000000Z",
  "opened_at": "2026-08-15T15:53:34.856523Z",
  "blind_mode": true,
  "provenance": "PUBLIC_RECORD",
  "description": "Eurostat publishes a flash estimate of euro-area annual inflation on the first working day after the reference month. July 2026 came in at 2.9 %, up from 2.8 % in June. This asks whether the August flash crosses the 3.0 % line.",
  "question_id": "48ef81cc-e8c7-4059-91e1-550a9ffc1391",
  "resolution_criteria": "YES if the headline annual rate in the Eurostat flash estimate for August 2026 is 3.0 % or higher, as first published. Later revisions do not change the resolution.",
  "expected_resolution_at": "2026-09-01T12:00:00.000000Z",
  "canonical_source_policy": "Eurostat euro indicators news release at https://ec.europa.eu/eurostat/news/euro-indicators — the flash estimate for August 2026.",
  "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: 0
tree_size: 179
leaf_hash: e6f9f9e33b9065874d934ce34dabf53925268e64079284b5a099f680365356d6
audit_path (8): 0: d9ca974c0cede57541dfcb283976c1340ad8f35bdc792d9a7e6c6470000dbe3f1: e18ecbcea86ce9cf0f0dbf66c3b29f8dae9b8f568206fc665cdfcb803cd7c5902: 0181e023c12bf413471cf696a1f35b944e2aa91d05e94025e4ca983e5220b8f53: 6accee06a91eebe583c1229064362cefcdec41ff4bb0d38479e32b13cdf4cc7a4: 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