Neo X TestNet has been upgraded to v0.6.0 “Rarefaction,” introducing help for Ethereum’s Osaka fork, a rebased Geth v1.16.9 basis, and the brand new BEACON/2 P2P protocol for improved community synchronization. The discharge is totally suitable with Neo X v0.5.3. The discharge, announced by Neo World Improvement on June 11, continues the chain’s sample of monitoring upstream Ethereum execution layer adjustments.
Neo X is constructed as a fork of Geth, Ethereum’s Go-based shopper implementation, maintained by Bane Labs. As such, it inherits execution layer upgrades from Ethereum’s roadmap. The v0.6.0 replace is the newest in a collection of TestNet releases which have progressively modernized Neo X’s structure, following the post-merge model introduced in v0.5.2 earlier this 12 months.
Osaka fork activation
Osaka is the execution layer part of Ethereum’s Fusaka improve, which mixed the Fulu consensus layer with Osaka and went reside on Ethereum MainNet in December 2025. Neo X TestNet will activate Osaka at Unix timestamp 1781500000, roughly June 15 at 5:06 a.m. (UTC).
BEACON/2 protocol and EIP-4844 enhancements
The discharge introduces BEACON/2, an up to date model of the beacon P2P protocol first deployed in v0.5.2. The brand new protocol model improves transaction synchronization by way of a proposal-aware search cache, block synchronization by way of handshake-triggered fetcher notifications, and blob synchronization with an improved sidecar fetcher. Older beacon protocol variations will probably be eliminated in future releases, making the improve important for continued community participation.
EIP-4844 blob transaction help, initially launched in v0.5.0 and expanded with devoted storage and question APIs in v0.5.2, has additionally been additional improved. The release notes don’t specify the precise adjustments, although associated bug fixes deal with blob synchronization configuration and sidecar fetcher habits.
Geth v1.16.9 safety fixes
The underlying Geth codebase has been updated to v1.16.9, a safety hotfix that addresses P2P-layer vulnerabilities CVE-2026-26314 and CVE-2026-26315. The Ethereum Basis advisable that operators recreate P2P node keys following the replace. Node operators working Neo X TestNet infrastructure ought to concentrate on this steering.
Further enhancements embrace upgraded execution-layer downloader support for post-merge backfilling, light verification for consensus-layer beacon belief extension, and refactored synchronization status checks. Bug fixes deal with points with dBFT seal hash computation, transaction replacement behavior, and RPC error responses for under-priced transactions.
Improve path
The replace is a suitable rolling improve that requires no chain reset. Operators upgrading from v0.5.3 ought to obtain the brand new binary and genesis file, cease the node, change the binary, initialize the database with the brand new genesis file utilizing geth init, and restart. Nonetheless, as with the v0.5.2 launch, the P2P protocol migration means nodes working variations older than v0.5.2 can now not obtain execution-layer block broadcasts. Operators are urged to improve promptly to take care of synchronization.
No MainNet deployment timeline has been introduced for v0.6.0. The total launch notes might be discovered on the hyperlink beneath:
https://github.com/bane-labs/go-ethereum/releases/tag/v0.6.0
