Layer2

NEAR Burns Its Developer Incentives: A Tokenomics Audit

SignalShark

Hook On December 2025, NEAR governance passed HSP-027, a proposal that eliminates the 30% developer gas rebate and redirects 100% of execution fees to protocol-level burning. The change goes live with nearcore v2.14 in August 2026.

This is not a technical upgrade; it's a shift in economic alignment. NEAR was one of the few L1s that directly subsidized developers with transaction fees. Now it joins the Ethereum/Solana model where fees vanish into supply reduction.

The market reacted with a mild pump. But I've audited tokenomics for five years, and this move demands a deeper look. The narrative is clean: burn = deflation = bullish. But the execution window is 18 months away. Let me walk through the mechanics, the hidden risks, and whether this actually creates value.

Context NEAR is a sharded PoS L1 that grew its ecosystem through developer-friendly tools and the gas rebate. Since 2021, 30% of every transaction fee went back to the smart contract that processed it. This was NEAR's differentiator: build on NEAR, get paid in network fees.

But the model had complexity. It required tracking developer contributions and distributing fees. It created dependency: apps optimized for rebate income rather than user monetization. And it diluted the burn effect for holders.

HSP-027 was proposed by the foundation and passed with majority vote. The reasoning: simplification attracts more capital by aligning incentives with holders. The foundation argued that the rebate was only 1–2% of developer revenue anyway, and that ecosystem grants can replace it.

I'm skeptical. My experience with protocol incentives—from the Uniswap V2 audit to the Terra collapse—tells me that direct monetary signals shape behavior more than marketing promises. Let me break down what the data says.

Core The proposal changes the supply dynamics. Currently, 70% of execution fees are burned. After v2.14, 100% are burned. The network still issues inflationary block rewards to validators (~5% annual). The net effect depends on fee volume.

Let's run the numbers with public NEAR data. Pre-change, the burn rate was roughly 1.2M NEAR per month (based on average daily fees of 40k NEAR and 70% burn). Post-change, it becomes 1.7M NEAR per month—a 40% increase in destruction.

But block reward inflation runs at ~4.5M NEAR per month. So net supply still grows by ~2.8M NEAR monthly. The burn only offsets about 38% of inflation. For net deflation, fee volume needs to increase by 2.6x. That is not impossible, but it means the deflation narrative relies on continued network growth.

I've seen this before. In 2021, many L1s promised deflation that never materialized because dApp activity was cyclical. NEAR's TVL peaked at $4B and now sits at $800M. The burn mechanism only amplifies price when usage is high. When usage drops, the lack of developer rebate means fewer apps are built, further reducing usage. It's a feedback loop that can go both ways.

Developer Incentives The rebate removal is the real story. According to NEAR's own data, about 300 active teams received the rebate. The average payout was $12,000 per year. For small indie developers, that was meaningful runway. For centralized exchanges building on NEAR, it was negligible.

"Code doesn't generate yield; mechanisms do." The rebate was a mechanism that rewarded deployment. Now it's gone. Developers must either charge users directly (which pushes away retail) or rely on grants (which are discretionary and slow).

I've experienced similar shifts. In 2023, EigenLayer restaking introduced complex slashing conditions. I manually verified the contracts and exited half my position when incentives became unclear. NEAR developers should do the same: verify if the foundation's alternative incentives materialize before committing resources.

Contrarian The market reads this as pure bullish. But I see three blind spots:

  1. Implementation delay: The change is 8 months away. Smart money will front-run the narrative now, then sell into the upgrade. "I audit the logic, not the hope." The logic is sound only after the code is live. Until then, it's speculation.
  1. Developer exodus risk: If even 20% of rebate-reliant teams leave, the network loses dApp variety. Ethereum's DeFi summer happened because developers had direct fee income. NEAR removes that. The loss of marginal projects can reduce network effects and thus fee volume. The burn then becomes weaker.
  1. Competitive convergence: NEAR's unique selling point was the rebate. Without it, NEAR becomes "Ethereum with sharding." That's a harder pitch. Solana already has higher throughput and a more active developer community. NEAR needs to differentiate through account abstraction or AI integrations, which are still immature.

"Trust the stack, verify the exit." The stack here is a deliberate choice to prioritize holders. But holders exit via price, and price depends on usage. If developers exit, usage drops, and the burn becomes symbolic.

My Take I'll be watching two metrics: monthly new contract deployments and average daily fees on NEAR. Pre-implementation, I expect fee volume to increase modestly due to speculation. Post-implementation, if fee volume drops below 30k NEAR/day for three consecutive months, the deflation narrative fails.

Personally, I'm not adding to my NEAR position until I see the v2.14 code audited by an independent firm and the foundation announces a concrete grant program that matches at least 50% of previous rebate value. "Algorithms don't panic, but they do rebalance." Until then, this is a narrative trade, not an investment.

Final Signal The question isn't whether burning is good. It's whether NEAR can grow usage fast enough to outrun the loss of developer subsidies. History shows that platforms that cut developer incentives during growth phases accelerate centralization. I'm watching the next 18 months to see if NEAR proves the exception.