The governance vote wasn't close. NEAR’s House of Stake, the chain’s on-chain decision-making body, approved HSP-027 with a clear majority. The proposal was simple on its surface: eliminate the 30% gas rebate that developers had collected since the network’s launch, and redirect those execution fees into a protocol-level burn. Effective August 2026, nearcore v2.14 will erase the last vestige of NEAR's unique developer-friendly fee model. The market cheered. I didn't.
I’ve seen this script before. In 2017, during the ICO mania, I was a junior engineer at a small security firm in Frankfurt, auditing the Parity Wallet multi-sig contract. I found a critical self-destruct vulnerability that could have drained millions. I hesitated to report it, fearing it would delay the project’s launch. But I chose transparency over speed. That moment taught me that code is law, but human ethics must guide it. The same ethical tension now haunts NEAR's decision. The burn mechanism is technically clean, mathematically elegant, and easy to market. But it removes a direct incentive for the very people who build the applications that give the network its value. Code has conscience. And sometimes, conscience means questioning the crowd.
Context: The Philosophy of the Rebate
NEAR Protocol launched in 2020 with a bold promise: not just sharding for scalability, but a developer-first economic model. The 30% gas rebate was a deliberate design choice, meant to attract builders by aligning their interests with network usage. Unlike Ethereum, where developers rely on secondary token sales or subscriptions, NEAR offered a direct slice of every transaction fee. It was a statement: “Your code is capital.”
The rebate cultivated a generation of builders who saw NEAR as a cooperative, not just a platform. Small teams built dApps with the confidence that a portion of user fees would fund their next iteration. The model was part of NEAR’s identity—a counter-narrative to the purely speculative economics of other L1s. But as the network matured, the governance debate shifted. Holders questioned why developers should capture 30% of fees when the network’s scarcity narrative remained weak. The argument for simplification gained steam.
By late 2024, the NEAR Foundation had internally modelled the impact of the rebate. They found that only a small fraction of dApps actually generated enough volume for the rebate to be meaningful. The cost to holders was disproportionate to the incentive effect. The push for HSP-027 was born.
Core: The Technical and Tokenomic Shift
The change is straightforward in code but profound in economics. Currently, when a user executes a transaction on NEAR, 30% of the gas fee is sent to the contract developer’s account, and 70% is burned. After nearcore v2.14, 100% of execution fees will be burned. The storage fees remain untouched (they are refundable). The implementation is a simple accounting tweak in the client’s fee distribution module—a few hundred lines of Rust. The technical risk is low; the team has a strong delivery record. No smart contract restructuring is needed.
But the tokenomics shift is seismic. The annualized burn rate will increase by roughly 43% (assuming current network activity). If NEAR’s transaction volume grows, the deflationary pressure becomes significant. In a bear market, survival matters more than gains—and a deflationary narrative can attract the capital that hedges against inflation elsewhere. The market loves a good burn. Trust is the new token.
Yet here is the hidden cost: the developer’s business model collapses. A dApp that relied on the rebate to cover server costs, audit fees, or developer salaries now has a hole in its P&L. The NEAR Foundation has promised alternative incentives—grants, ecosystem funds—but those are discretionary, not automatic. The rebate was a right, not a privilege. By turning it into a grant application process, NEAR shifts the power dynamic from a cooperative to a gatekeeper.
During my time as a Product Manager at a DeFi protocol during the DeFi Summer of 2020, I saw the tension between efficiency and inclusivity firsthand. I struggled to design community governance for Aave v2 that felt fair to retail users against institutional whales. I spent nights drafting whitepapers that emphasized 'financial sovereignty' over 'yield optimization.' That experience taught me that economic models are not just mathematical puzzles; they are social contracts. NEAR’s social contract with its developers is now being rewritten.
The proposal passed with 68% support. But the 32% opposition likely came from developers and small validators who saw the rebate as their lifeline. The governance dashboard doesn’t show identities, but the sentiment on the NEAR forum revealed a quiet fear: 'What happens to our project after August 2026?' The answer is unclear.
Contrarian: The Blind Spot of Simplification
The mainstream crypto media celebrated HSP-027 as a 'holder victory.' They called it a 'maturation' of the token model. They compared it to Ethereum’s EIP-1559 and praised NEAR for joining the deflationary club. But this triumphant view ignores a crucial reality: NEAR is not Ethereum. It does not have Ethereum’s network effects, its developer mindshare, or its liquidity moat. Ethereum can afford to burn all fees because its value as a settlement layer is proven. NEAR is still proving itself.
By eliminating the rebate, NEAR homogenizes its economic model. It becomes 'just another L1 with a burn'—a label that invites direct comparison to Solana, Avalanche, and even the emerging Move-based chains. Its competitive advantage was the explicit alignment with developers. That advantage is now gone.
What is the unspoken truth? The rebate was a subsidy for innovation. Not all subsidies are efficient, but they create a buffer for experimentation. Small teams could launch a dApp with minimal revenue pressure. Removing that buffer forces every builder to focus on immediate monetization. In the short term, that might lead to lower-quality apps or higher user fees as developers pass costs to consumers. In the long term, it could weed out weak projects. But the risk is that we lose the one project that would have become the next breakthrough.
I’ve seen this before. In 2022, after the FTX collapse, I retreated to Frankfurt, doubting my idealistic view of decentralization. I studied ZK-rollups, finding comfort in mathematical certainty. But the real lesson was that resilience comes from decentralized incentive structures, not just cryptographic proofs. NEAR’s move centralizes the incentive flow back to the protocol itself. It says, 'Trust us, we will reinvest in developers.' But trust is earned through transparency, not enforced through a burn.
Takeaway: The Long Bet
HSP-027 is a bet. A bet that the community of builders will stay despite the loss of direct revenue. A bet that the deflationary narrative will attract enough capital to create a virtuous cycle of higher token price, more development, and more network usage. A bet that the ecosystem fund can allocate capital more efficiently than automatic rebates.
But the market has a short memory. By August 2026, the hype around this change will have faded. What will remain is the actual developer experience. If builders leave, the burn will be meaningless—empty blocks produce no fees. If they stay, NEAR will have traded a complex incentive for a simpler story.
Liquidity flows where belief resides. The question is: do developers still believe?
I don't have an answer. But I know that every line of code is a moral choice. NEAR’s engineers chose a clean, elegant burn. Now the moral choice belongs to the builders. Will they forgive the lost rebate, or will they whisper the words that haunt every protocol: 'We were better before.'
Only time—and the 2026 release of nearcore v2.14—will tell. Until then, I watch the chain data, the developer forums, and the quiet exodus or quiet resilience. That is where the truth lies.