NEAR Backs 36% Issuance Cut as Staking Rewards Face Squeeze

NEAR issuance vote leaves activation pending

The official proposal, authored by SVRN chief executive Sal Ternullo, is marked succeeded. It retains the 90% staking and 10% treasury allocation and requires validator adoption, with a 90-day grace period before a 24-month reduction schedule.

A lower issuance rate means fewer new tokens are created relative to the supply base. The 36% headline measures the relative change in the ceiling, not a reduction in existing wallet balances or an immediate removal of circulating tokens.

PortalCripto reported that the ballot passed Monday and that the Security Council can veto the plan until November 16. That leaves a governance checkpoint ahead of any network implementation.

The separate House of Stake voting page also identifies the proposal as succeeded in its published metadata. Approval and software adoption remain different events: a vote expresses the governance decision, while a protocol upgrade changes the rules validators actually run.

An activation notice would therefore carry different information from another announcement celebrating the ballot. It would need to establish when the new schedule begins and how operators implement it.

NEAR staking yield model points lower

HSP-029’s table models gross staking yield falling from 5.268% to 3.372%, assuming 42.71% staking participation. These conditional figures use a September 22 network snapshot; they are neither current wallet quotes nor promised returns.

NEAR’s staking documentation explains that holders can delegate tokens to validators to help secure the chain and receive rewards. It advises checking operators’ records, uptime and commissions, all of which matter when comparing a protocol-level estimate with what a delegator receives.

A network issuance ceiling and a staking yield measure different things. Issuance relates new tokens to the overall supply; a staking return relates rewards to the tokens participating in staking. Using one percentage as a substitute for the other would misstate the economics.

If a smaller reward pool is shared among fewer staked tokens, the return per remaining token can change. A fixed-participation model holds that response constant to show a scenario; it cannot determine how delegators will actually react.

The distinction also reaches investment products. Our coverage of the Bitwise NEAR ETF’s staking charges explains how service-provider deductions sit between rewards generated and rewards retained. Protocol estimates alone cannot establish the return an ETF shareholder or a custodial-platform customer would receive.

For validator businesses, the analytical question is whether reward income still covers operating costs and attracts delegated stake. For holders who do not stake, slower issuance reduces dilution, but it does not determine demand or guarantee a higher market price.

NEAR tokenomics shifts beyond issuance

The decision follows a broader debate about how the network pays for security. In the September governance discussion, Ternullo separated an issuance reduction from longer-term research into a fixed supply. The latter was not presented as a completed design ready for approval.

NEAR’s February tokenomics update had already described a previous inflation halving, live onchain governance and revenue-linked buybacks. Those mechanisms address different parts of token economics: creating fewer tokens is distinct from purchasing tokens with revenue.

The site’s earlier NEAR quantum-safe signing upgrade coverage concerned network security technology. This vote changes the proposed economic incentives for the people operating that infrastructure, adding an implementation question alongside the token-supply debate.

Broader sentiment remained cautious. Alternative.me’s Fear and Greed Index read 34, or Fear, against 26 a day earlier when checked November 4. It describes the broader crypto market, rather than NEAR-specific staking demand.

As of 03:35 UTC on November 4, the reviewed records did not establish a completed activation or a final validator rollout date. The Security Council review, an implementation release and evidence of validator adoption are the next events needed to turn the approved policy into a running issuance schedule.