Neo has announced the release of Neo X MainNet v0.5.1, a significant patch update that introduces support for event subscriptions from enveloped transactions while also scheduling the Cancun and Prague upgrades on MainNet. This update maintains compatibility with both v0.4.2 and v0.5.0, allowing for a seamless transition without the need for node resynchronization.
The deployment of Neo X v0.5.1 sets the stage for the Cancun and Prague hard forks, slated to occur at timestamp 1,763,000,000, following their successful implementation on the TestNet. The Cancun hard fork is designed to enhance rollup scaling by incorporating a new data format known as blobs. These blobs enable Layer 2 solutions to manage substantial amounts of data that require only temporary storage by nodes, thereby optimizing costs.
On the other hand, the Prague upgrade focuses on various enhancements to the execution layer. This includes the introduction of a new precompile that supports the BLS12-381 curve for zkSNARK proof verification, an increase in calldata gas costs to promote blob adoption, and improvements aimed at stateless clients. Notably, Prague also empowers externally owned accounts with the ability to set account code, enabling them to function similarly to smart contracts. This advancement allows for multicalls and delegation to other addresses, paving the way for account abstraction and other innovative functionalities.
The update also refines PreBlock construction, particularly in how enveloped transactions are processed. The handling of PreBlock has been restructured to minimize the chances of unexpected envelope reverts. Additionally, the introduction of real-time event subscriptions for envelopes allows applications to monitor specific activities as blocks are generated.
Node operators are strongly encouraged to upgrade to v0.5.1 to ensure ongoing stability and compatibility with forthcoming upgrades. Those operating on TestNet can upgrade directly from v0.5.0 without any configuration adjustments. However, MainNet operators transitioning from v0.4.2 must reinitialize their databases using the updated genesis configuration, while ensuring the existing database remains intact.
For further details, the complete announcement can be found at the following link: Neo X MainNet v0.5.1 Upgrade Announcement.
