SEO Sub Developers drop the first release candidate for nearcore 2.14.0, introducing major protocol modifications, database upgrades, and pioneering post-quantum cryptographic verification tools.
Main Facts
The infrastructure underpinning the NEAR Protocol is undergoing a significant evolution. Developers have officially published the first release candidate (RC) for nearcore version 2.14.0, a development milestone that marks a pivotal moment for the layer-1 blockchain network. Unlike routine maintenance patches or minor bug fixes, 2.14.0-rc.1 has been explicitly categorized by the core engineering team as both a comprehensive protocol upgrade and a critical database upgrade.
This dual classification immediately signals to validators, node operators, and ecosystem participants that the release demands careful consideration, rigorous pre-production testing, and ultimate network-wide synchronization.
At the heart of this release candidate are several high-impact modifications to how the NEAR blockchain processes transactions, manages smart contract execution, and handles state storage. The most prominent updates include:
- The Elimination of Contract Gas Rewards: The parameter governing burnt-gas rewards for smart contracts has been permanently slashed from 30% down to 0%. This fundamentally alters the economic incentives surrounding contract deployment and interaction.
- Resolved Promise Input Bounding: To protect the network from memory bloat and potential denial-of-service (DoS) vectors, the protocol now enforces a strict upper limit on the combined size of resolved promise inputs, preventing excessively large receipt inputs from expanding unchecked.
- Post-Quantum Cryptographic Support: The introduction of the
ml_dsa_verifyhost function enables smart contracts to natively verify ML-DSA-65 signatures directly on-chain.
While the software is currently sitting in a release candidate stage—meaning its components are not yet permanently locked into the production environment—it outlines the definitive trajectory of NEAR’s technical roadmap. For the average crypto enthusiast or decentralized application (dApp) user, no immediate action is required. However, for the backbone of the network—the validator nodes and RPC providers—this release kicks off a crucial testing window that will dictate the future stability and security of the NEAR ecosystem.
Chronology
To understand the weight of the nearcore 2.14.0-rc.1 release, it is essential to trace the historical cadence of NEAR Protocol’s infrastructure upgrades and how this specific release candidate came to fruition.
Q4 2024 to Early 2025: The Push for Scalability and State Optimization
Throughout late 2024, the NEAR core development teams focused heavily on state pruning, RPC performance enhancements, and reducing the hardware requirements for running validator nodes. As decentralized applications on NEAR scaled to handle millions of daily active users—largely driven by consumer-facing AI agents and social applications—the strain on the underlying database architecture became increasingly apparent.
During this period, core contributors began identifying bottlenecks in receipt execution and gas distribution mechanics. Discussions within GitHub repositories and developer forums laid the groundwork for adjusting economic parameters, such as the contract gas rewards system, which many economists within the ecosystem argued created unintended execution incentives.
Mid-February 2025: The Cryptographic Horizon Expands
Concurrently, cryptographic researchers within the broader Web3 space grew increasingly vocal about the theoretical threat of quantum computing breaking current elliptic-curve cryptography (such as Ed25519 and secp256k1). While a cryptographically relevant quantum computer (CRQC) capable of cracking modern blockchains is still estimated to be years away, proactive foundational work began in earnest across multiple leading networks.
NEAR developers collaborated to integrate post-quantum primitives into the core codebase. The choice fell upon ML-DSA (Module-Lattice-Based Digital Signature Algorithm), standardized as part of the NIST post-quantum cryptography standardization process.
February 2025: The Unveiling of 2.14.0-rc.1
The culmination of these multi-threaded development efforts materialized with the publishing of the nearcore 2.14.0-rc.1 release via the official NEAR GitHub repository. Node operators were immediately greeted with release notes highlighting the compounding nature of the update. Because the release alters both consensus-critical protocol rules and the underlying database state management, it bypassed the classification of a standard iterative update, entering a deliberate, high-scrutiny testing phase designed to catch edge cases before mainnet deployment.
Supporting Data
To fully grasp the technical mechanics of nearcore 2.14.0-rc.1, we must examine the specific data points, parameters, and architectural adjustments introduced in the changelog.
1. Zeroing Out Contract Gas Rewards
Under previous versions of the NEAR protocol, a designated percentage (historically set at 30%) of the gas fees burnt during smart contract execution was funneled back or accounted for as a reward mechanism to incentivize contract deployment and creator engagement.
- The Adjustment: Version 2.14.0-rc.1 reduces the burnt-gas reward parameter to 0%.
- The Economic Impact: This shift means that contract developers will no longer receive a subsidized kickback from the gas burned by users interacting with their smart contracts. While this may slightly alter the revenue models for pure infrastructure contracts, it streamlines the protocol’s tokenomics, aligning burnt gas strictly with native deflationary mechanisms (where transaction fees are permanently removed from circulation) rather than redistributing them to contract creators.
2. Bounding Resolved Promise Inputs
Asynchronous composability is one of NEAR’s most powerful architectural features, allowing smart contracts to make cross-contract calls via "promises" and handle the results when those promises resolve. However, malicious or poorly optimized contracts could previously pass excessively large data payloads within these resolved promises, straining network memory and slowing down block processing times.
- The Adjustment: The 2.14.0 release introduces a hard architectural bound on the combined size of resolved promise inputs.
- The Technical Benefit: By capping these inputs, the protocol prevents unbounded memory consumption, ensuring that validators are protected against memory-exhaustion attacks and that block propagation times remain deterministic and fast.
3. Integrating the ml_dsa_verify Host Function
Perhaps the most forward-looking data point in the release is the inclusion of the ml_dsa_verify host function.
- What is ML-DSA-65? Module-Lattice-Based Digital Signature Algorithm (specifically security category 3, corresponding to ML-DSA-65) is a post-quantum cryptographic scheme designed to withstand attacks by both classical and quantum computers running Shor’s algorithm.
- Functionality: By exposing this as a native host function, NEAR allows WebAssembly (Wasm) smart contracts to execute high-performance cryptographic verifications of ML-DSA signatures directly on-chain.
- Nuance: Core developers emphasize that this addition does not instantly transform the entire NEAR network into a quantum-proof blockchain—consensus mechanisms and existing account keys still rely on standard elliptic curves for now. Instead, it provides the vital cryptographic primitive required for developers to build quantum-resistant smart contracts, multi-signature wallets, and cross-chain bridges today.
Official Responses and Developer Insights
The release of nearcore 2.14.0-rc.1 has generated significant discussion within the NEAR developer community, validator forums, and core engineering channels.
The Validator Perspective: Caution and Preparation
Node operators and validator guilds have approached the release with their customary professionalism. Because 2.14.0-rc.1 is classified as both a protocol upgrade and a database upgrade, validators cannot simply deploy the update lazily. Database migrations carry inherent risks; if a state migration script encounters an unexpected edge case on a heavily loaded node, it could lead to desynchronization or downtime.
Leading validator representatives noted in technical coordination chats:
"A database upgrade combined with a protocol state change means we treat this RC with maximum diligence. We are spinning up testnet nodes immediately to monitor memory consumption during the state migration phase, ensuring that the new promise-input bounds and gas parameter shifts behave precisely as documented under heavy simulated transaction loads."
Core Engineering Rationale
While formal statements accompanying the GitHub release emphasize standard operational procedures—urging community members to report bugs, file issues, and test on beta networks—internal architectural notes shed light on the philosophy driving the release.
Core contributors noted that preparing for a multi-chain, AI-integrated future requires ruthlessly optimizing execution layers while simultaneously future-proofing cryptographic infrastructure. By stripping away redundant gas subsidies and hardening the protocol against unbounded data inputs, NEAR is intentionally prioritizing lean, predictable execution performance. Meanwhile, the inclusion of post-quantum tools like ml_dsa_verify demonstrates that the protocol is unwilling to wait for a quantum crisis to begin building the solutions of tomorrow.
Implications
The deployment of nearcore 2.14.0—once it successfully transitions from a release candidate to a stable mainnet production build—carries far-reaching implications for various stakeholders across the NEAR ecosystem.
1. For Smart Contract Developers
- Economic Realignment: Developers who relied on contract gas rewards must re-evaluate their monetization strategies. DApp creators can no longer factor protocol-level gas kickbacks into their financial sustainability models.
- Enhanced Security & Capabilities: Developers gain a powerful new tool in the form of
ml_dsa_verify. Security-conscious projects—particularly those handling institutional assets or bridging high-value state across cryptographic boundaries—can begin experimenting with post-quantum signature verification, future-proofing their smart contract architectures against emerging technological threats. - Stricter Payload Limits: The new bounds on resolved promise inputs mean that developers must write cleaner, more modular code. Passing bloated, monolithic data structures through cross-contract promises will no longer be tolerated by the protocol.
2. For Validator and Infrastructure Operators
- Operational Vigilance: Node operators must allocate time and resources to test the database migration path thoroughly. Ensuring zero downtime during epoch transitions that involve database schema updates is paramount for maintaining network reliability and avoiding slashing penalties.
- Hardware Efficiency: Over the long term, the constraints placed on promise inputs and the optimization of core execution paths will result in a healthier, more predictable state growth curve, potentially lowering the long-term hardware barriers for keeping a full archive or validator node.
3. For the Broader Blockchain Industry
- Proactive Post-Quantum Adoption: While many layer-1 networks treat post-quantum cryptography as a distant, theoretical talking point, NEAR’s integration of ML-DSA host functions places it among the forward-thinking vanguard of blockchains actively equipping their developer ecosystems with quantum-resistant primitives.
- Economic Maturity: Removing the 30% burnt-gas reward parameter signals a maturing tokenomic model—one willing to prune legacy incentive structures that no longer serve the network’s long-term health as it scales toward mass adoption.
Conclusion
The release of nearcore 2.14.0-rc.1 represents much more than a routine software patch; it is a calculated step forward in NEAR Protocol’s technical and economic maturation. By tightening protocol parameters to secure the execution layer against memory bloat, recalibrating gas reward economics, and introducing native post-quantum cryptographic verification capabilities, NEAR continues to fortify its position as a high-performance, future-proof blockchain.
As the software moves through the rigorous release candidate testing pipeline, the responsibility now rests on the shoulders of validators and developers to vet the build under real-world conditions. Once stabilized and pushed to mainnet, nearcore 2.14.0 will solidify a leaner, more secure, and technologically advanced foundation for the next generation of decentralized applications and autonomous agents running on the NEAR network.
