NEAR has shipped nearcore 2.14.0-rc.1, and this one matters more than a routine patch. The release is flagged as both a protocol upgrade and a database upgrade, while also changing gas reward mechanics and adding native ML-DSA-65 signature verification for smart contracts.
- Release candidate, not final
- Protocol and database upgrade
- Gas reward changes and input limits
- New on-chain ML-DSA-65 verification
According to the NEAR nearcore GitHub release for 2.14.0-rc.1, this is the first release candidate for version 2.14.0. That RC label matters. It means the software is meant to be tested carefully before a stable rollout, not treated like a casual upgrade-and-forget release.
For ordinary NEAR users, there is nothing obvious to install. This is infrastructure software for the people running the network: validators, node operators, and developers who need to know whether their systems will keep syncing cleanly or start acting up at the worst possible time.
Why this release carries extra weight
The headline detail is simple: NEAR describes nearcore 2.14.0-rc.1 as both a protocol upgrade and a database upgrade.
A protocol upgrade changes the rules the network follows. If node operators do not upgrade in time, their software may stop following the network correctly once the upgrade activates. In plain English: no compatible software, no smooth participation in consensus.
A database upgrade is different, but no less important. It usually means node state storage or migration behavior is changing in some way, which raises the stakes for anyone running infrastructure. Database changes are where “looks fine on paper” can quickly turn into “why is this node sulking at me?”
That is exactly why release candidates exist. They give validators and developers a chance to test the build under real conditions before the final version goes live. In blockchain infrastructure, the people who skip testing are usually the same people who later write long angry posts about “unexpected behavior.”
What changed in nearcore 2.14.0-rc.1
One notable change is the removal of contract gas rewards. The release notes also say the burnt-gas reward parameter is reduced from 30% to zero. That is a blunt economic shift, not a cosmetic tweak.
For readers less familiar with the term, gas is the fee used to pay for computation on a blockchain and to help prevent spam. When a chain changes how gas-related rewards work, it can alter incentives for validators and protocol participants, even if everyday users never notice the mechanics directly.
The release also adds a bound on the combined size of resolved promise inputs. NEAR’s wording is technical, but the practical goal is clearer: it puts a limit on how large certain asynchronous contract inputs can grow, instead of letting oversized receipt inputs expand without an explicit protocol cap.
That kind of guardrail is not glamorous, but it is useful. Blockchains do not usually fall apart because of one dramatic failure. They get dragged down by a thousand tiny edge cases, and unbounded inputs are exactly the sort of thing that can become a headache later.
The most interesting cryptography change is the addition of ml_dsa_verify as a host function. That lets smart contracts verify ML-DSA-65 signatures on-chain.
ML-DSA is a post-quantum digital signature standard, meaning it is designed with future quantum-resistance in mind. In simpler terms, it is a signature scheme meant to hold up better if large quantum computers ever become practical enough to threaten today’s public-key cryptography.
That does not make NEAR quantum-proof. It does, however, give smart contracts a native primitive for verifying that class of signature when developers want to use it. That is a real capability, and a useful one. It is also a long way from magical, because no single host function turns an entire network into some invincible sci-fi fortress.
What node operators need to pay attention to
The real audience for this release is the infrastructure crowd: validators, node operators, and developers testing compatibility. If you are running NEAR infrastructure, this is the kind of build you inspect closely, not the kind you toss onto production because the changelog looked short.
The release notes are clear that nodes need compatible software before the protocol upgrade activates if they want to keep participating normally in consensus. That is the practical risk here. Miss the upgrade window, and your node may stop tracking the network properly.
Database upgrades deserve equal attention because they can affect how node state is stored and migrated. Even if the upgrade path is well designed, operators still need to test it. The boring part of infrastructure work is often the part that saves your skin.
For ordinary users, the impact may be invisible unless something goes wrong. That is how good infrastructure usually works: nobody claps because the plumbing stayed dry. They only notice when it does not.
Why the ML-DSA change is worth watching
Adding ml_dsa_verify is more than a neat cryptography checkbox. It suggests NEAR wants to make post-quantum verification easier for developers without forcing them to build custom verification logic from scratch.
That matters because native support can lower friction. If a smart contract can verify a signature directly at the protocol level, developers do not have to reinvent the wheel, and they do not have to trust a brittle workaround just because it was convenient.
Still, the hype machine should keep its hands off the steering wheel here. Post-quantum support is useful, but it is not a blanket shield against every future cryptographic problem. Good tools help. They do not repeal physics, mathematics, or human error.
Key questions and takeaways
-
Is nearcore 2.14.0-rc.1 the final release?
No. It is a release candidate, which means NEAR is still asking validators and developers to test it before the stable version ships. -
Why does the protocol upgrade matter?
Protocol changes affect the network’s rules. Nodes that are not running compatible software by activation time may stop following the network correctly. -
Why is the database upgrade important?
Database upgrades can change how node state is stored or migrated, so operators need to handle them carefully and test for compatibility. -
What changed with gas rewards?
NEAR removes contract gas rewards and reduces the burnt-gas reward parameter from 30% to zero, which changes part of the chain’s incentive structure. -
What does ml_dsa_verify do?
It lets smart contracts verify ML-DSA-65 signatures on-chain using a native host function. -
Does this make NEAR quantum-proof?
No. It adds support for verifying a post-quantum signature scheme, but it does not make the whole network quantum-proof. -
Who should care most about this update?
Validators, node operators, and developers. Ordinary users are less likely to notice anything unless the rollout runs into trouble.
The bigger picture
This release is a reminder that serious blockchain progress usually looks unsexy from the outside. Tighter limits, cleaner migrations, and better cryptographic primitives do not make for flashy marketing slides, but they are the kind of changes that keep networks from wobbling when things get busy.
NEAR is clearly doing two things at once here: tightening protocol mechanics and preparing for newer cryptographic use cases. That is a sensible direction. It is also the kind of work that only looks boring if you have never had to debug a broken node at 2 a.m.
For now, the message is straightforward. nearcore 2.14.0-rc.1 is an important pre-final release, and the people running NEAR infrastructure should treat it with the attention it deserves.
Further reading
A few useful side roads if you want to track the technical, psychological, and market angles around NEAR.
