Neo readies its client before Gorgon
Neo-CLI 3.10.0 adds node and wallet tooling ahead of a planned MainNet deployment on June 26.
Neo Global Development released Neo-CLI v3.10.0 on June 11 and plans to deploy it to the Neo N3 MainNet on June 26, 2026, after a T5 TestNet rollout on June 12. The important point is not a flashy product launch, but a network operations update: this version does not activate the Gorgon hard fork, does not require node resynchronization, and still prepares a set of changes that matter for both node operators and application developers.
Neo-CLI is the reference client used to run Neo N3 nodes. In a blockchain, this kind of software defines how nodes validate transactions, expose RPC interfaces and stay compatible with one another. The official notice lists several performance improvements, including fixes around virtual-machine operations, a VM JumpTable refactor and updated cryptographic verification logic. In plain terms, the release aims to make execution more reliable and easier to inspect without immediately changing consensus rules.
The most concrete part for developers is tooling. The release adds wallet import and export with BIP-39 mnemonic phrases, a common standard that turns a sequence of words into a recoverable key. It also introduces a DeferredRelay plugin, designed to relay a transaction automatically once it enters its valid relay window, plus new RPC methods and CLI commands to sign, relay, sign messages and verify signatures. These details matter because many blockchain frictions come from small repeated operations: managing a wallet, diagnosing an expired transaction, testing a contract or reproducing an error.
The announcement also says something about the maturity of public chains. Neo is not presenting a break with the past here, but maintenance work: better transaction validation, clearer error reporting, an official Docker image for one-command node deployment and richer RPC diagnostics for contract execution. For end users, nothing changes immediately. For teams maintaining nodes or applications, the window is clear: test the release on T5, then upgrade before June 26 if TestNet operation remains stable. The later Gorgon step may draw more attention, but this release is a reminder that blockchain robustness also depends on these intermediate updates, especially when they are explicit, compatible and operationally boring in the right way.