← the log
sequence 4

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.

← 35 →
01. Link to this band.

The entry

entry_hash60f01537124c. The chained hash of entry 4, which is what every proof on this page is about.REAL_UTC
sequence_number
4
entry_type
delphi.question.published
entity_type
forecast_question
entity_id
1b1a20a9-2af9-4c58-972e-a6628e241b09
logged_at
2026-08-15T15:53:35.024151+00:00
previous_hash
16e8d51eb964859b302e2ad0483a320c110b0bcbde4adefe0c12542204aeb84a
payload_hash
982d16d8b2b41229d9c198b8e057feb98eab5b06e2ddbafb26d16b51e47b281b
entry_hash
60f01537124c36a895e63a3f4e67406e3afab5544b85ef668ef45a0c1bbae08b

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

02. Link to this band.

Payload

{
  "slug": "will-the-ecb-leave-the-deposit-facility-rate-unchanged-at-its-10-september-2026-meeting",
  "title": "Will the ECB leave the deposit facility rate unchanged at its 10 September 2026 meeting?",
  "origin": "EDITORIAL",
  "timebase": {
    "clock": "REAL_UTC"
  },
  "closes_at": "2026-09-10T11:00:00.000000Z",
  "opened_at": "2026-08-15T15:53:35.020746Z",
  "blind_mode": true,
  "provenance": "PUBLIC_RECORD",
  "description": "The deposit facility rate has stood at 2.25 % since 17 June 2026. The Governing Council meets on 10 September. This asks only whether the rate moves at all, in either direction.",
  "question_id": "1b1a20a9-2af9-4c58-972e-a6628e241b09",
  "resolution_criteria": "YES if the monetary policy decision published on 10 September 2026 leaves the deposit facility rate at 2.25 %. NO if it is set to any other value.",
  "expected_resolution_at": "2026-09-10T14:00:00.000000Z",
  "canonical_source_policy": "ECB monetary policy decisions at https://www.ecb.europa.eu/press/govcdec/mopo/html/index.en.html, entry for 10 September 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.

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
4
tree_size
179
leaf_hash
a49846980e15f536f81c22a6874e945d8d3a0f92b4a7a87a743fd90b78b35f42
audit_path (8)
0: 5176210a015d8f492eda75861a516e13c6f16510c32ad81600c61451f28486821: 2a11c2d916cb6f37e57105d282aac63ab273306f1623b527b3d0b5ffbb907d8e2: c46f68fc5f6d0676e6a592aca2eb0ccd91364c312bbd202fdc2603dc938c6a353: 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