The NEAR Protocol has officially launched the first release candidate for nearcore 2.14.0, introducing a series of impactful changes aimed at improving the overall functionality and efficiency of the network.
Designated as 2.14.0-rc.1, this release is notable for being both a protocol upgrade and a database upgrade, making it a significant step forward for node operators, who will need to carefully consider the implications of these changes.
Despite its importance, it’s critical to recognize that this is still a release candidate. Therefore, while the proposed changes are noteworthy, they are not yet finalized and are subject to further testing and adjustments before the official stable version is rolled out.
The Protocol Upgrades Explained
The changelog for version 2.14.0 brings several key modifications that warrant attention. Among the most significant is the removal of contract gas rewards, which has seen the burnt-gas reward parameter drop from 30% down to zero. This shift may have implications for how contracts are incentivized on the network.
Another important change is the introduction of a limit on the combined size of resolved promise inputs. This enhancement is designed to prevent excessively large receipt inputs from expanding indefinitely, thereby ensuring smoother operation and scalability.
Additionally, the update includes a new ml_dsa_verify host function, enabling contracts to verify ML-DSA-65 signatures on-chain. This is particularly intriguing as ML-DSA represents a post-quantum digital signature standard, offering a level of future-proofing for developers aiming to utilize such signatures.
While this does not make the NEAR network entirely quantum-proof, it provides a native primitive within smart contracts for verifying this class of signature.
The Importance of Testing Before Final Release
The status of this update as a release candidate emphasizes the necessity for thorough testing. Release candidates are critical for validator operators and developers, allowing them to run the software in realistic environments ahead of the final stable build.
In particular, database upgrades require meticulous attention, as they can significantly affect how the node state is stored and migrated. With a protocol-version change, the stakes are even higher; nodes must ensure they are running compatible software to continue participating effectively in consensus.
For everyday NEAR users, there are no immediate actions required. This update primarily targets the infrastructure software that supports the network’s operations. However, it is important to note that these foundational releases often lay the groundwork for features that users will experience in the future.
As nearcore 2.14.0 makes its way through the development pipeline, the NEAR community remains eager to see the benefits these upgrades will bring to the ecosystem.
For more details, check the official release on GitHub: nearcore 2.14.0-rc.1.
