A governance vote on NEAR Protocol just quietly rewrote one of the network’s most fundamental economic rules — and the implications reach well beyond a single line item in a developer’s budget.
The House of Stake, NEAR Protocol’s on-chain governance body, passed proposal HSP-027 on July 8, removing the developer gas rebate that has been part of the network’s design since its early days. Every gas fee from smart-contract interactions will now be burned in full — no portion returned to developers.
The margin wasn’t close. The final tally came in at 46 votes representing 4.66 million veNEAR in favor, against just 2 votes representing 1,819 veNEAR against. That’s not just a supermajority — it’s a near-total consensus among active governance participants, signaling broad alignment across the NEAR ecosystem on the direction the protocol needs to take.
For context, veNEAR is the voting-weight token used within the House of Stake system, meaning that in terms of economic stake behind the decision, the result was overwhelmingly lopsided. The governance body’s authority over a core economic parameter of this magnitude is itself part of the story — NEAR co-founder Illia Polosukhin explicitly described the vote as “a great test” ahead of future governance proposals and said he was “excited to have explicit governance for economics of $NEAR.”
Under NEAR’s current fee structure, 30% of gas fees generated by calls to a smart contract flow back to that contract’s owner, with the remaining 70% burned. Once HSP-027 is implemented, the rebate drops to zero — meaning the full 100% of gas fees will be burned going forward.
The rebate was originally designed by Polosukhin to reward developers who built reusable, widely-used smart-contract components. The logic made sense at the time: the more users interacted with your contract, the more gas revenue you earned back. It was a direct incentive loop between usage and developer compensation.
But the web3 application landscape evolved. Most NEAR-based dApps today don’t monetize through gas fees at all — they sponsor gas costs for users and generate revenue through spreads, subscriptions, or advertising models instead. The rebate, in that context, became noise rather than signal. Polosukhin also flagged an accounting problem: the 30% return was difficult to distinguish from ordinary user fund deposits on-chain, adding unnecessary complexity to financial tracking for both developers and the protocol itself.
The change is expected to go live around August 2026 alongside the nearcore v2.14 release. NEAR’s developer-relations team has already moved to get ahead of the transition, warning builders directly: “don’t factor this gas bonus into your dApp’s budget anymore.” That’s a clear signal that developers need to revisit any financial models that assumed rebate income as a revenue stream.
Polosukhin’s framing of the change centers on two things: cleaner protocol economics and the removal of incentives that no longer serve their original purpose.
The NEAR governance account described HSP-027 as reducing “protocol complexity and misaligned incentives for builders.” Polosukhin echoed this, calling the outcome a step “to keep NEAR Protocol simpler and cleaner going forward.” The argument isn’t that the rebate was harmful — it’s that it became irrelevant to how the ecosystem actually operates, while adding accounting overhead and creating edge-case incentive distortions.
When an economic mechanism no longer matches the behavior it was meant to reward, keeping it in place creates more confusion than value. That’s the core logic here, and it’s hard to argue against when the data on dApp monetization patterns backs it up.
The most direct consequence of this change is a shift toward a more deflationary token model. By eliminating the rebate carve-out, every unit of gas spent on the NEAR network now permanently exits circulating supply through burning. That increases the deflationary pressure on NEAR’s token issuance without altering the network’s broader value-capture mechanics.
It’s worth being precise about what this doesn’t change: the underlying economics of how NEAR generates and captures value remain intact. The removal of the NEAR developer gas rebate doesn’t affect transaction throughput, fee levels, or validator economics. What it does is tighten the burn mechanism, making each transaction marginally more deflationary than before.
For developers, the transition requires some recalibration. Any dApp that was passively treating rebate income as part of its financial model needs to update those assumptions before August 2026. In practice, most modern NEAR applications were likely already ignoring this revenue stream given the shift to gas sponsorship models — but the warning from the developer-relations team suggests edge cases still exist.
The broader significance here is institutional. This vote demonstrated that House of Stake can move decisively on core protocol economics when the case is clear and the community is aligned. Polosukhin’s framing of HSP-027 as a governance stress test sets a precedent: future proposals touching NEAR’s economic parameters now have a template to follow — and a benchmark for what community consensus actually looks like in practice.
It is a mechanism that currently returns 30% of gas fees from smart-contract calls to the contract owner, with the remaining 70% burned. After the implementation of HSP-027, the rebate will drop to 0% and all gas fees will be burned.
NEAR aims to simplify protocol economics and remove misaligned incentives for builders. Most dApps on the network no longer monetize through gas fees — they sponsor gas costs and recover revenue through spreads, subscriptions, or ads — making the rebate both redundant and a source of accounting complexity.
The change is expected around August 2026 with the nearcore v2.14 release.
Removing the rebate makes NEAR’s token issuance more deflationary by burning all gas fees instead of returning a partial rebate to contract owners. It does not alter the network’s broader value-capture model.
Article produced with the assistance of artificial intelligence and reviewed by the editorial team.
