NEAR the network, NEAR the asset

NEAR is a proof-of-stake L1 designed around sharded execution (Nightshade) and an account model that treats contracts as accounts. The token, NEAR, sits at the center of three concrete protocol functions: (1) it is the staking asset that determines validator selection and reward share, (2) it is the unit used to pay execution fees (“gas”), and (3) it is the asset locked to cover on-chain state via “storage staking,” as described in the protocol design paper.

From a TradFi lens, the token is not equity-like. There is no hard promise that protocol “revenue” is distributed to passive holders. The closest thing to a recurring holder return is staking yield, and that yield is primarily a function of issuance policy, not fee cashflows. NEAR does have a burn mechanism, but the burn is a negative supply drift lever, not a dividend. For a comparable “utility-first” crypto asset, see our Chainlink tokenomics review.

Supply policy and initial distribution

Genesis supply was 1,000,000,000 NEAR, created at genesis on April 22, 2020, per NEAR’s token supply breakdown.

NEAR’s maximum supply is not capped in the way Bitcoin’s is, consistent with an inflationary security budget design.

On March 7, 2026 (this analysis date), the figures shown for NEAR are Circulating Supply: 1,289,514,256 and Total Supply: 1,289,514,272.

The genesis allocation (percentages shown in NEAR’s own distribution materials) breaks down as follows.

One structural update matters for holders. NEAR shipped a consensus-layer change (nearcore v2.9.0, released October 21, 2025) that reduced the maximum inflation rate from 5% to 2.5%, per the v2.9.0 release notes.

By December 1, 2025, the nearcore v2.10.0 release documentation references upgrading the protocol version from 81 → 82, which is consistent with protocol version 81 having become the active baseline in that period.

Cashflow map: fees, burns, developer rebates

NEAR’s fee model is best understood as a three-way split between (1) developers, (2) token supply burn, and (3) the security budget funded by issuance.

Execution fees (“gas”) are paid in NEAR. A key choice in NEAR’s design is explicit developer monetization at the protocol level: 30% of gas fees burned while executing a contract are paid to the contract’s account as a developer incentive, per the gas fee rules.

On the burn side, NEAR’s published economics describe that 70% of transaction fees are burned and 30% are rebated to the contracts touched.

The white paper frames the burn mechanism as “all transaction fees (minus the part allocated as the rebate for contracts) are burned,” and notes that sufficiently high fee volumes can, in principle, drive inflation toward zero or negative.

Here is the investable implication. Fee burn supports NEAR’s scarcity narrative only if fee volume is large enough. Developer rebates are economically meaningful, but they accrue to application-controlled accounts, not to token holders as a class. If you are underwriting NEAR as a financial instrument, that rebate looks like an ecosystem subsidy to builders, not a shareholder return. For a contrast in how protocols frame tokenholder value capture, see our Uniswap tokenomics review.

Storage staking: capital lock as a protocol “take”

NEAR also prices state, not just execution. When contracts store data, the owning account must stake (lock) NEAR proportional to bytes stored. If the account cannot lock enough NEAR for added storage, the transaction fails under the storage staking rules.

Storage staking has a clean mechanical property: it reduces the liquid float available for other uses. The docs explicitly note that storage-staked tokens are unavailable for validation staking, which mechanically increases validator yields for a given issuance budget.

NEAR documents the storage price parameter as 1E19 yoctoNEAR per byte, i.e. ~100kb per NEAR.

In TradFi terms, this is closer to a working-capital requirement than a fee. It is not burned and it is not paid to stakers. It is a balance-sheet lock that changes token velocity and the staking denominator.

Staking: issuance-funded yield, with low slashing risk

NEAR is proof-of-stake with delegation. Delegators start earning after the next epoch, described as roughly 12 hours.

Unstaking is not instantaneous. NEAR’s documentation describes a 4 epoch (~24 hours) unbonding period before tokens can be withdrawn.

Historically, NEAR’s published parameters described 5% annual maximum issuance with 90% of that issuance flowing to validators and 10% to a protocol treasury, while fee burn can reduce net inflation.

Then came the 2025 reset: nearcore v2.9.0 targets max inflation 2.5% (down from 5%). For a comparison point on PoS inflation and staking incentives, see our Polkadot tokenomics review.

On validator risk: the protocol does enforce performance consequences, but NEAR’s own integrator FAQ is explicit that validators who miss too many blocks or chunks can be removed from the validation set and lose rewards without slashing.

That “no slashing” statement matches nearcore-focused technical documentation that notes slashing is currently disabled (while still describing the intended design).

For tokenholders, this changes staking’s risk-return profile. Lower tail risk makes staking feel bond-like, but the return is still mostly issuance-funded. The cost is dilution borne by holders who do not stake. If you want a quick primer on staking terms and dilution mechanics, our tokenomics FAQ covers the basics.

Governance: validators control the money printer (in practice)

NEAR’s meaningful economic parameter changes arrive via protocol upgrades, not day-to-day tokenholder voting. The inflation halving is a good example because it is unambiguously “monetary policy.”

The nearcore v2.9.0 release lays out the mechanism: protocol change bundled into a client release, with protocol version 80 → 81 and voting starting October 28, 2025. The release notes describe the upgrade as becoming effective when a stake threshold is met.

NEAR’s RPC protocol configuration documentation shows a parameter named protocol_upgrade_stake_threshold represented as [4, 5], which corresponds to an 80% stake threshold for upgrades in that example configuration.

Two takeaways for valuation. First, NEAR’s monetary policy is credibly changeable. That reduces “permanent 5% dilution” fatalism. Second, it concentrates economic control in the validator set and the upgrade process, which is operationally efficient but creates governance risk if large validators are captured by a small set of custodians or institutional operators.

Valuation lens and risk register

The core tension in NEAR tokenomics is simple. NEAR wants to be cheap to use. Cheap usage implies low fee load per transaction. Low fee load implies low burn. With weak burn, staking yield is mainly issuance-funded. That yield is attractive to stakers, but it is not the same thing as protocol earnings. It is a transfer from non-stakers, plus whatever marginal scarcity comes from burning.

NEAR’s strongest “revenue-share-like” feature is not for tokenholders. It is the developer rebate, which directs a slice of usage fees to the contracts being used. That is great for builder economics and can bootstrap a marketplace of sustainable apps. It does little for passive holders unless you believe it drives enough usage to raise burn or to increase long-term demand for NEAR as working capital and staking collateral.

Dominant risk: NEAR’s value accrual is structurally indirect, which makes it hard to underwrite the token as anything other than (a) a staking instrument whose yield is largely policy-driven, plus (b) an adoption option on NEAR becoming a high-usage settlement layer with meaningful fee burn. The halving to a 2.5% max inflation cap reduces the “policy tax,” which is real progress. But the mechanism still does not convert protocol activity into distributable cashflows for holders. Burns help all holders, but only if the burn is large enough relative to issuance. Meanwhile, developer rebates and ecosystem treasuries can be rational ecosystem spend, yet they look like operating expenses funded by token dilution unless they translate into persistent demand. This is the same underwriting problem TradFi has with high-growth businesses that never commit to returning capital. You can get a great product and still have a mediocre instrument if the claim on the economics is weak or too uncertain.

There is also a second-order version of the same risk: if staking yield remains meaningfully above “opportunity yields” inside the ecosystem, staking can crowd out DeFi usage. NEAR’s own rationale for reducing inflation explicitly points at increasing incentives for productive on-chain participation versus passive staking.

Top 3 risks

  1. Monetary-policy volatility, Trigger: a new nearcore release proposes changing inflation, treasury take, or fee policy. Mechanism: validator-coordinated upgrades change the supply curve and staking economics at the protocol layer. Who bears it: non-stakers (dilution), validators (security budget), and holders pricing the token on expected real yield. Measurable indicators: new nearcore releases tagged as protocol upgrades, protocol-version transitions, and explicit changes like the 5% → 2.5% maximum inflation cut in v2.9.0.
  2. Weak fee burn relative to issuance, Trigger: sustained low gas fees and low aggregate fee volume, even as token supply grows. Mechanism: net inflation stays positive because the burn (70% of fees) is too small to offset issuance, and staking yield remains mostly redistribution rather than economically earned return. Who bears it: long-only holders who do not stake, and stakers if price pressure offsets nominal yield. Measurable indicators: total supply trend, burn metrics from explorers/analytics, and the gap between nominal staking APY and fee-derived burn. For ongoing tracking frameworks and comparable benchmarks, see our research reports.
  3. Governance capture via validator concentration, Trigger: a small subset of validators (or custodians) accumulates enough stake to strongly influence upgrade outcomes. Mechanism: stake-weighted upgrade thresholds mean concentrated operators can accelerate or block economic changes, shaping “monetary policy” for the entire network. Who bears it: smaller validators (competitive viability), users (policy instability), and holders (risk premium). Measurable indicators: validator stake distribution, participation rates in upgrade windows, and how quickly protocol-version upgrades clear the 80% threshold.

If you are building on NEAR or designing incentives around NEAR-denominated fees, treat this as token economy design work, not just “emissions tuning.” For teams that need help stress-testing supply, fee routing, and stakeholder incentives, this is the kind of scope where tokenomics consulting is worth paying for, because small parameter mistakes compound quickly once they’re on-chain.



This article is part of our Tokenomics Deep Dive series.