Neo has released Neo-CLI v3.10.1, a patch update that sets the Gorgon hard fork activation heights, targeting TestNet on approximately July 24 and MainNet on Aug. 1. The release also fixes an RPC wallet bug that was breaking ordinary transfers since v3.10.0 was deployed to MainNet on June 26.

The Gorgon hard fork will activate at block 17,960,000 on TestNet and block 12,020,000 on MainNet. Node operators running Neo-CLI must upgrade before these heights or fall out of consensus. No blockchain resync is required for operators who upgrade in time.

Dynamic opcode pricing clears the path for cheaper transactions

Gorgon is the hard fork the Neo Council deferred to in April when a proposed 100x execution fee reduction deadlocked in a 7-7 vote. The concern at the time was that a blanket fee reduction could allow an attacker to lock up the network for as little as US $15. Rather than approve the reduction, the Council opted to wait for Neo SPCC’s dynamic opcode pricing model, aimed at making standard transactions, such as Flamingo token swaps, approximately 100x cheaper while making malicious transactions exponentially more expensive.

Neo-CLI v3.10.0 introduced the Gorgon preparation code in June but did not set activation heights. v3.10.1 completes that process, incorporating protocol-level changes including corrected bitwise shift operations, optimized VM opcode dispatch, and updated cryptographic verification logic.

RPC wallet bug fix

The release addresses a bug in the sendtoaddress, sendfrom, and sendmany RPC methods that rendered ordinary wallet transfers unusable on MainNet since v3.10.0 was deployed on June 26.

The root cause was in the SignAndRelay method, which modified the NetworkFee field after transaction signing, invalidating witness signatures. Users attempting wallet transfers via RPC received InvalidSignature errors for approximately two weeks.

The fix rewrites SignAndRelay to calculate fees before signing, re-sign if fee adjustment is needed, validate sender balance, and enforce a maximum fee cap. The reworked method also eliminates a legacy fee overcharging issue. Under MainNet policy, the previous calculation systematically charged users more than the protocol’s own CalculateNetworkFee method required.

Additional fixes and security patch

The DeferredRelay plugin received a fix for a crash that affected fresh node installations. Nodes with the plugin enabled would encounter a KeyNotFoundException on startup because the plugin attempted to read ledger state before the genesis block was persisted.

The SQLiteWallet plugin now pins SQLitePCLRaw.lib.e_sqlite3 to v3.53.3, addressing CVE-2025-6965 in older transitive SQLite dependencies. Node operators using SQLiteWallet should upgrade to pick up the patch.

Release packaging overhaul

v3.10.1 introduces a new packaging format. Linux and macOS builds now ship as .tar.gz archives with single-file executables, and archive naming has been updated to include version numbers, for example, neo-cli.v3.10.1-linux-x64.tar.gz. Archives contain a versioned root directory. Windows and portable builds remain in .zip format.

Upgrade timeline

TestNet nodes are expected to upgrade beginning July 10, with MainNet node upgrades targeted for July 28 if TestNet runs stably. Operators upgrading from v3.10.0 who use the TokensTracker plugin should note that the plugin appends NetworkId to its storage directory name. Existing data folders may need to be renamed to match the new convention.

The full release notes can be found at the link below:
https://github.com/neo-project/neo-node/releases/tag/v3.10.1