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 - 60
- entry_
type delphi.question.published- entity_
type forecast_question - entity_
id 08ea8d0c-fe07-4a30-a823-6e71109f1fb5- logged_
at 2026-08-15T15:53:37.575287+00:00- previous_
hash 0243b4bbd29a837f1b5e6e2db38e175fb493918976ec55619b28237750f9bbe7- payload_
hash 498bbc8ee1f6a605754f68741b9e54c154f8d237a62ec5d4d12e39b59792be51- entry_
hash 4d741c1b8a11befbfc0df892e9cc6f23ed9a3b7c8f02c959cd5ef8162c8ed769
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"slug": "will-the-who-report-more-than-20-human-h5n1-cases-with-onset-in-the-second-half-of-2026",
"title": "Will the WHO report more than 20 human H5N1 cases with onset in the second half of 2026?",
"origin": "EDITORIAL",
"timebase": {
"clock": "REAL_UTC"
},
"closes_at": "2026-09-01T12:00:00.000000Z",
"opened_at": "2026-08-15T15:53:37.572403Z",
"blind_mode": true,
"provenance": "PUBLIC_RECORD",
"description": "Between August 2025 and June 2026 the WHO recorded twelve human H5N1 cases outside the United States across three countries, with three deaths. This asks whether the second half of 2026 runs above that pace.",
"question_id": "08ea8d0c-fe07-4a30-a823-6e71109f1fb5",
"resolution_criteria": "YES if the WHO cumulative table, in an update published after 31 December 2026, lists more than 20 laboratory-confirmed human H5N1 cases with onset between 1 July and 31 December 2026.",
"expected_resolution_at": "2027-02-15T12:00:00.000000Z",
"canonical_source_policy": "WHO cumulative table of confirmed human cases of avian influenza A(H5N1) at https://www.who.int/publications/m/item/cumulative-number-of-confirmed-human-cases-for-avian-influenza-a(h5n1)-reported-to-who.",
"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 - 60
- tree_
size - 181
- leaf_
hash 95ee932becc0f178023311b5ac24195771b460c45f7941a303185a4bd1493d19- audit_
path (8) 0: 35707c9741801d4801274136258f062f8a18ee5888ba0cf42a317de082de36521: 5280fcc28f0d9e516225eb339b796806791a694d92ddce9d93a45f9b9555bce22: a716f063852c3292bf19ec7de1198746dbf82b64a40fb0d1d5bc087981ea89673: 4a9e6d722dfb6e0747ca36be6009f85c6e94a6e038404e24e59f837c397ac49f4: 2470c45a41e5b2338cd0a79e1b28f402a0e7e23251bee7ed256b2f8f028ccbe75: 0dec549ee6527dafc0e801068f2df8c4eef8fcb9972397c6eb58217673bbfe9c6: 432b3bec17cc8d9bd118f5d2d11fc56d0578ec1940af60be2192f2f1b8d43dc67: 9635acfeb8c2590a96fbee35cfdc30839f075e00ba35b025d06547731fc18743- root_
hash 4c26c3ce818fe1e45410fef48bf0969b94f9e5bc0389388f5310d968c2e42fdc
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