Neo The release is fully compatible with Neo X v0.5.3. The release, announced by Neo Global Development on June 11, continues the chain’s pattern of tracking upstream changes in the Ethereum execution layer.
Neo X is built as a fork of Geth, the Go-based client implementation of Ethereum maintained by Bane Labs. As such, it adopts execution layer upgrades from Ethereum’s roadmap. The v0.6.0 update is the latest in a series of TestNet releases that have gradually modernized Neo X’s architecture, following the post-merge model introduced earlier this year in v0.5.2.
Activation of the Osaka fork
Osaka is the execution layer component of Ethereum’s Fusaka upgrade, which combined the Fulu consensus layer with Osaka and went live on Ethereum MainNet in December 2025. Neo
BEACON/2 protocol and EIP-4844 improvements
The release introduces BEACON/2, an updated version of the beacon P2P protocol first implemented in v0.5.2. The new protocol version improves transaction synchronization via a proposal-aware search cache, block synchronization via handshake-triggered fetch notifications, and blob synchronization with an improved sidecar fetch. Older beacon protocol versions will be removed in future releases, making the upgrade essential for continued network participation.
Support for EIP-4844 blob transactions, initially introduced in v0.5.0 and expanded with special storage and query APIs in v0.5.2, has also been further improved. The release notes do not specify the exact changes, although related bug fixes address blob sync configuration and sidecar fetch behavior.
Geth v1.16.9 security fixes
The underlying Geth codebase has been updated to v1.16.9, a security hotfix that addresses the CVE-2026-26314 and CVE-2026-26315 vulnerabilities in the P2P layer. The Ethereum Foundation has recommended that operators recreate P2P node keys after the update. Node operators using the Neo X TestNet infrastructure should be aware of these guidelines.
Additional improvements include upgraded download support for the execution layer for post-merge replenishment, lightweight verification for extending trust in the consensus layer, and revised sync status checks. Bug fixes address issues with dBFT seal hash calculation, transaction replacement behavior, and RPC error responses for underpriced transactions.
Upgrade path
The update is a compatible rolling upgrade that does not require a chain reset. Operators upgrading from v0.5.3 must download the new binary and genesis file, stop the node, replace the binary, initialize the database with the new genesis file using geth initand restart. However, as with the v0.5.2 release, the migration of the P2P protocol means that nodes with versions older than v0.5.2 can no longer receive block broadcasts at the execution layer. Operators are urged to upgrade immediately to maintain synchronization.
No MainNet implementation timeline has been announced for v0.6.0. The full release notes can be found via the link below:
https://github.com/bane-labs/go-ethereum/releases/tag/v0.6.0