MIGRATE TO N3


BLOG March 18, 2026

Neo X TestNet v0.5.2 Upgrade Announcement

We are releasing Neo X TestNet v0.5.2, a patch version introducing several improvements and scheduled upgrades for the network. The new version will be deployed to MainNet shortly. 

This patch release introduces several improvements to align Neo X with the v1.15 Geth implementation. Without creating a new consensus client program or performing a “Merge”-like consensus algorithm change, our nodes now switch to the CL-EL model and support post-merge behaviors. A configurable blob file system for EIP-4844 data persistence is also added, along with JSON APIs for related queries.

This version does not introduce any hard fork in the genesis file or database changes that would require reinitialization or resynchronization. However, there is a protocol migration of the P2P network. As a result, nodes running versions before v0.5.2 will no longer receive EL block broadcasts for synchronization. Please perform this upgrade as soon as possible.

The new blob storage may require up to approximately 288GB of disk space. Please ensure your running machine meets this requirement.

Upgrade Instructions

Follow the instructions below to upgrade your node from v0.5.1 to v0.5.2:

  1. Download the new binary from the release page.

  2. Gracefully stop the node.

  3. Replace the old binary with the new binary.

  4. If you are running a validator node, rename the --miner.etherbase flag in your start script or command to --miner.pending.feeRecipient.

  5. Start the node.

New Features

  • Support EL-level blob data storage and JSON APIs for EIP-4844

Behavior Changes

  • Add a minimal CL implementation and switch to post-merge mining

  • Introduce a beacon protocol and move the block broadcast message to the CL

  • Remove EL reorg judgment and other deprecated pre-merge behaviors

Improvements

  • Improve snap synchronization for short chains

Bug Fixes

  • Fix possible panics in gas price queries caused by uninitialized variables

  • Fix DKG synchronization failure caused by old blocks

  • Fix DKG synchronization failure caused by missing group initialization


​​If you have further questions regarding the upgrade, please ask in our Discord community. Follow our official account for future updates.

Written by:
NGD
Tags: