Optimism’s repository published kona-host v1.9.0 on 23 October, recommending it for op-challenger operators on 1.8.1 and strongly recommending it for earlier versions.

Configuration errors now stop startup

An explicitly configured dependency-set file must be readable and valid; previously an unusable file could yield an empty set. Expiry overrides exceeding seven days are rejected. Operators using network presets without a configured file are unaffected.

Beacon compatibility and TLS security

The host accepts beacon slot duration through SLOT_DURATION_MS, with SECONDS_PER_SLOT as fallback. It errors if neither exists. A rustls update addresses a low-severity key-exchange downgrade; the release also carries forward 1.8.1’s eMudhra certificate fixes.

The separately released kona-client 1.9.0 is optional: its notes describe a certificate-store update and unchanged proof execution for existing chains.

NetNapz assessment

The immediate operational issue is upgrade preparation. A deployment that explicitly supplies a dependency-set file needs a configuration check before restarting. Treating stricter validation as a routine binary replacement could turn a previously tolerated configuration problem into an outage.

Release availability alone does not establish operator adoption, a chain upgrade or an economic benefit for OP holders. Those require separate evidence. The useful follow-up is whether operators complete upgrades and maintain reliable challenger service, rather than inferring a token-price outcome from a software tag.

Sources and scope

Reviewed the official kona-host release and kona-client release notes. This report covers published software changes; it does not independently measure deployment or network performance.