Neo X TestNet v0.6.0 Adds Ethereum Osaka Fork Support
Neo X TestNet v0.6.0, named “Rarefaction,” adds support for Ethereum’s Osaka fork and rebases the chain on Geth v1.16.9, according to Neo Global Development. My take: this is the right kind of boring. Neo X is staying close to Ethereum’s execution layer, which matters for developers who want Ethereum-style behavior instead of another almost-EVM chain with odd edge cases.
Neo Global Development announced the upgrade on June 11. The release keeps Neo X aligned with upstream Ethereum execution layer changes, which fits the chain’s Geth base. That sounds automatic. It is not. Someone still has to test the changes, ship them, and keep the network from drifting into sync trouble. v0.6.0 follows earlier TestNet releases, including v0.5.2, which introduced the post-merge model earlier this year. For developers, the win is plain: fewer surprises when moving contracts or tooling across networks. Infrastructure too.
Osaka activation is the headline item in the release notes. Osaka is the execution layer part of Ethereum’s Fusaka upgrade, which paired the Fulu consensus layer with Osaka and went live on Ethereum MainNet in December 2025. Neo X TestNet is scheduled to activate Osaka at Unix timestamp 1781500000, around June 15 at 5:06 a.m. UTC. Why does this matter? Because chains that claim EVM compatibility eventually have to prove they can keep pace with Ethereum’s real upgrade cycle. Neo X is moving before the deadline is right on top of it. If testing holds, dApps that need newer EVM features may have another chain to consider. For traders, though, the real question is colder: does this create deployments and liquidity, or just a neat release note?
The release also adds BEACON/2, a newer version of the beacon P2P protocol first used in v0.5.2. It improves transaction sync with a proposal-aware search cache. It also improves block sync through fetcher notifications during handshakes, plus blob sync with a better sidecar fetcher. Dense stuff, yes. But the practical point is simple: nodes should find the right data and share it more reliably. Older beacon protocol versions will be removed later, so operators will need to upgrade to stay in sync. EIP-4844 blob transaction support, first added in v0.5.0 and expanded in v0.5.2 with storage and query APIs, gets more fixes too. The release notes do not spell out every blob change, but they mention fixes for blob sync configuration and sidecar fetcher behavior. Not glamorous. Still important.
The Geth base is now v1.16.9, a security hotfix for P2P-layer vulnerabilities CVE-2026-26314 and CVE-2026-26315, according to the release notes. The Ethereum Foundation advised operators to recreate P2P node keys after updating, and Neo X TestNet operators should probably do the same. I’ll be honest: this is the part I would not skip. Crypto has a long memory for security failures. The Ronin Bridge hack in March 2022, with more than $600 million stolen, hit confidence hard and hurt AXS and SLP prices. TestNet fixes do not move markets on their own. Ignoring P2P security would be worse.
Other changes include better execution layer downloader support for post-merge backfilling and light verification for consensus layer beacon trust extension. Sync status checks are cleaner. The bug fixes cover dBFT seal hash computation, transaction replacement behavior, and RPC error responses for underpriced transactions. Operators can do a rolling upgrade. No chain reset is required. Anyone running a version older than v0.5.2 should upgrade soon, since the P2P protocol migration can affect synchronization. Neo has not announced a MainNet deployment date for v0.6.0.
What this means
Most upgrade writeups treat Ethereum alignment like a checkbox. That is only half right. Neo X is trying to stay close to Ethereum’s execution layer instead of drifting into its own private flavor of EVM compatibility. I think that is the right call. Developers do not want romance here. They want working tools, predictable contract behavior, and infrastructure teams that are not forced to maintain weird one-chain exceptions. Is this overkill for a TestNet release? No, not if Neo X wants serious EVM projects to treat it as more than a side experiment.
MainNet timing is the thing to watch now. TestNet support helps, but the market will care more if dApps, bridges, liquidity providers, and infrastructure teams actually deploy around it. Counter to the usual advice, I would not read the Osaka support by itself as a price signal. The stronger signal would be Neo Global Development announcements tied to new projects on Neo X, especially if the wider EVM market is already moving higher. Traders watching NEO should watch for price movement around those updates. A strong MainNet release and real usage could put the $15 to $18 range back in view, a level NEO last saw in early 2023. Without usage, this stays a technical upgrade, not a thesis.