MIGRATE TO N3


BLOG April 30, 2025

Neo N3 Releases Neo-CLI v3.8.0 & Proposes Block Time and GAS Generation Rate Adjustments

Neo-CLI v3.8.0 is released on April 30, 2025, and the T5 TestNet will be updated at the same time. The MainNet upgrade is scheduled for May 14, 2025.

This version includes a hard fork, so we strongly recommend upgrading as soon as possible.

  • TestNet hard fork height: Block 5,870,000

  • MainNet hard fork height: Block 7,300,000

Key Updates in v3.8.0

This upgrade mainly includes the following improvements:

  1. Introduces block generation time management in the Native Policy Contract

  2. Enhances CalculateNetworkFee to better support contract signers

  3. Adds a new NotaryAssisted transaction attribute

  4. Enables recovery of public keys from signatures and messages using Secp256k1

  5. Adds a new Notary native contract

In addition, this update introduces a significant proposal aimed at improving the performance of the Neo N3 network:

Target block generation time: reduced from 15 seconds to 3 seconds

Target GAS generation rate: reduced from 5 GAS per block to 1 GAS per block

Policy Contract Enhancements:

  • Two new methods, SetMillisecondsPerBlock and GetMillisecondsPerBlock, will be added to the Native Policy Contract

  • The Neo Council will be able to adjust these parameters through voting transactions using their multisig address

  • DApps and smart contracts will be able to retrieve accurate block timing by invoking the Policy Contract

Next Steps & Considerations

This proposal is being announced in advance to the Neo developer community and will not take effect until it is formally voted on by Neo Council Members, expected in approximately three months.

Potential Impact: This proposal may affect certain dApps that currently rely on a hardcoded 15-second block interval.

Developer Recommendations:

  1. Retrieve block generation time using GetMillisecondsPerBlock from the Native Policy Contract instead of using fixed values.

  2. Node maintainers should upgrade their TestNet nodes as soon as possible before the hard fork height to avoid data incompatibility issues.

Stay informed and prepare accordingly. If you have any questions, please reach out via our Discord channel.

Written by:
NGD