Neo-CLI v3.10.0 is now available, introducing groundwork for the upcoming Gorgon hard fork alongside new developer tools, wallet enhancements, and an official Docker image for simplified node deployment. The release was published on June 11, deployed to the T5 TestNet on June 12, and is planned for MainNet on June 26.
The update does not activate the Gorgon hard fork itself, which remains without a scheduled date. However, it marks a significant step toward readiness for the C# reference node, which must complete its dynamic opcode pricing implementation before the fork can proceed. The Neo Council voted in April to defer a 100x execution fee reduction until Gorgon’s dynamic pricing model is in place, citing security concerns with reducing fees under the current fixed-rate system.
Gorgon preparation
Several changes in v3.10.0 target the virtual machine and consensus layer ahead of Gorgon. The VM JumpTable has been refactored to optimize opcode execution dispatch, and fixes to SHL (shift left) and SHR (shift right) bitwise operations address discrepancies identified during cross-client compatibility work. Opcode price charging has also been optimized, and cryptographic verification logic has been updated.
These changes align the C# node more closely with NeoGo, which has already completed its Gorgon preparation. Once both client implementations are ready, the Gorgon hard fork can be scheduled. Its dynamic pricing model aims to make standard transactions roughly 100 times cheaper while making malicious transactions exponentially more expensive, resolving the security concern that blocked the fee reduction vote in April.
Developer tools and wallet enhancements
Neo-CLI now supports BIP-39 mnemonic phrase import and export for wallet management. The feature allows users to back up and restore wallets using standard 12- or 24-word mnemonic phrases, aligning Neo with industry-standard wallet recovery practices. BIP-39 support was first introduced at a basic level in v3.9.0 and has been expanded in this release.
Four new RPC methods improve wallet operations and message signing workflows. The sign and relay methods handle transaction signing and broadcasting, while signmsg and verifymsg enable arbitrary message signing and verification with wallet keys.
RPC diagnostics have also been enhanced with improved transaction validation and error reporting. A new “Expired” verification result flags transactions that exceed their validity window, and duplicate Conflicts attributes are now rejected, giving developers clearer feedback when troubleshooting failed transactions.
A new DeferredRelay plugin automatically relays pending transactions once they enter their valid relay window, improving handling for time-sensitive operations.
Docker deployment
An official Dockerfile has been added to the neo-node repository, providing a containerized deployment option for Neo-CLI nodes. The addition includes a Quick Start guide and is aimed at lowering the barrier to entry for new node operators, particularly for cloud deployments and CI/CD pipelines where consistent, reproducible environments are essential.
Infrastructure and stability
Beyond the headline features, v3.10.0 includes a substantial set of bug fixes and infrastructure improvements. Consensus reliability has been improved through a ChangeView fix and the removal of invalid transactions from PrepareRequest payloads. Storage snapshot leaks have been addressed, and MaxTransactionsPerBlock has been set to 200 for N3 MainNet, consistent with the parameter change the Council approved in April.
Logging has been migrated to Serilog, RPC server security defaults have been strengthened, and integration tests now verify that all 12 plugins install correctly. An auto-release workflow for the CLI and plugins streamlines the build pipeline going forward.
Deployment timeline
Node operators can upgrade to v3.10.0 without resynchronizing the chain. The release is based on .NET 10 and is available from the GitHub releases page. MainNet deployment is planned for June 26.
The full release announcement can be found at the link below:
https://neo.org/blog/details/4338
