NEAR has released nearcore 2.14.0-rc.1, a release candidate that combines a protocol upgrade with a database upgrade. That makes the update more significant for validators and node operators than a routine maintenance release, even though it is still a pre-production build rather than the final version.
The candidate adds changes to gas rewards, places a new limit on resolved promise input size, and introduces a host function for on-chain verification of ML-DSA-65 signatures. The software is now moving through testing before any stable release is issued.
Why this RC matters
Release candidates are meant to be tested in conditions that are close to production before a final stable build is published. In this case, the update carries extra weight because it changes both protocol behavior and the database layer.
For validators, protocol version changes mean compatible software is needed to remain aligned with network consensus. For node operators, database upgrades can require especially careful handling because they may affect state storage and migration.
Gas reward parameter cut to zero
One of the main protocol changes in nearcore 2.14.0-rc.1 is a revision to contract gas rewards. The release reduces the burnt-gas reward parameter from 30% to 0.
The source article identifies this as a notable change in the candidate release, but does not describe any broader economic effect beyond the parameter adjustment itself.
Input-size bound and new signature verification function
The release also adds a bound on the combined size of resolved promise inputs. According to the source, the aim is to stop excessively large receipt inputs from expanding without a protocol-level limit.
Another addition is a new host function called ml_dsa_verify. This allows smart contracts to verify ML-DSA-65 signatures on-chain.
ML-DSA is described in the source as a post-quantum digital signature standard. At the same time, the article notes that adding this function does not make the NEAR network as a whole quantum-proof; it provides a native smart-contract primitive for this class of signatures.
Testing path before final rollout
Because nearcore 2.14.0-rc.1 is still a release candidate, it is not yet the final production version. The current stage is intended to surface issues under realistic testing before a stable build is approved.
The confirmed next step is continued movement through NEAR's testing pipeline toward a final release. Until then, the update should be treated as a candidate build rather than a completed rollout.
Source: bitcoinist.com