Neo Global Development has released v0.6.1 “Sedimentation” for Neo X MainNet, which scheduled the Osaka fork activation at timestamp 1782700000 (June 29 at 02:26 UTC). The release also addresses two bug fixes and two infrastructure improvements targeting beacon synchronization and metrics reporting. Node operators, particularly consensus node runners and anyone using the built-in metrics service, are strongly urged to upgrade ahead of the fork activation.
Osaka fork activation on MainNet
The headline change in v0.6.1 is the scheduled activation of the Osaka fork on Neo X MainNet. 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. As a Geth fork, Neo X inherits execution layer upgrades from Ethereum’s roadmap.
Neo X TestNet activated Osaka on June 15 with the v0.6.0 release. The MainNet activation brings Neo X‘s execution layer to parity with Ethereum’s current standard. All MainNet node operators must upgrade before the activation timestamp to remain compatible with the network after the fork.
Bug fixes and improvements
The release carries two bug fixes and two infrastructure improvements on top of v0.6.0.
PR #629 addresses a potential status inconsistency during beacon synchronization and improves the synchronizers reliability. The fix resolves a bug that could cause inconsistent sync status reporting, while the accompanying improvement applies choice pruning to status checks, tightening the synchronization process.
The second bug fix (PR #632) removes an irregular dBFT metric counter that had been accumulating in the dBFT static pool and surfacing in metrics output. For node operators running monitoring or alerting dashboards against Neo X metrics endpoints, this counter would have produced misleading readings. Its removal cleans up the metrics surface and should prevent false alerts or skewed data in any tooling built on top of it.
Separately, continuous integration pipelines have been migrated and improved, including automated arm64 binary builds.
Who needs to act
NGD has specifically called out two groups as high-priority for this update:
- Consensus node operators:The beacon sync fix is directly relevant to consensus node operation, and the Osaka activation requires all nodes to be running v0.6.1 before the fork timestamp. NGD describes the upgrade as “highly recommended” for this group.
- Metrics service users:The removal of the irregular dBFT static pool counter affects anyone consuming Neo X metrics output. Dashboards or alerting rules built against the old metrics surface should be reviewed after upgrading.
MainNet node operators should note that the upgrade requires database reinitialization using the new binary and updated genesis configuration file.