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 - 56
- entry_
type delphi.question.published- entity_
type forecast_question - entity_
id d8d7d8bd-61ec-4918-b395-799de97e359f- logged_
at 2026-08-15T15:53:37.429435+00:00- previous_
hash 3f333ce6b26689d3be3fbbb42b7adefe72f129b75f3133768f75c11412ce654a- payload_
hash ce635f3da1bf3cc9a4200f36253cac4b854f0fece726463b5fc07f09eac184a4- entry_
hash 575c48168f460280f605fac83c79bfd411171358192ec397890bac1f5bc41cdd
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"slug": "will-at-least-three-more-atlantic-storms-be-named-between-24-august-and-30-september-2026",
"title": "Will at least three more Atlantic storms be named between 24 August and 30 September 2026?",
"origin": "EDITORIAL",
"timebase": {
"clock": "REAL_UTC"
},
"closes_at": "2026-08-23T22:00:00.000000Z",
"opened_at": "2026-08-15T15:53:37.426294Z",
"blind_mode": true,
"provenance": "PUBLIC_RECORD",
"description": "Two storms had been named against a full-season forecast of seven to thirteen. September is normally the busiest month. Three more inside five weeks would put the season on track for the middle of the range.",
"question_id": "d8d7d8bd-61ec-4918-b395-799de97e359f",
"resolution_criteria": "YES if three or more Atlantic basin systems receive a name from the National Hurricane Center with the naming advisory timestamped between 24 August 2026 00:00 UTC and 30 September 2026 23:59 UTC. Storms named before the window do not count, whatever they do inside it.",
"expected_resolution_at": "2026-10-01T12:00:00.000000Z",
"canonical_source_policy": "National Hurricane Center advisory archive for the 2026 Atlantic season at https://www.nhc.noaa.gov/.",
"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 - 56
- tree_
size - 181
- leaf_
hash 6e93b5ee3a35b93736969719882e042dec8a05b4513ac640284a12293ec38242- audit_
path (8) 0: 4174597983f69336fa222917188aff6ffaad909255561382c6b16032568111b61: 52bc49fc18553cfd3aa001ea92a88b326825fdd56fd06909846c06145f496e262: 2aa9d10e11bad4b2419579996ad9e22ad7c5bd8f526eba31cb6bed527184022d3: 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