Avalanche is built for many chains. AVAX is the rent layer.

Avalanche is explicitly architected as a platform for launching application-specific blockchains across permissioned and permissionless deployments, alongside scalable dapps and custom digital assets.

That design goal matters for tokenomics because it creates two competing truths about AVAX.

First, AVAX is the native utility token of the Avalanche Primary Network. It is used for fees, staking, and as an economic weight in network decisions, with fees burned at the protocol level.

Second, Avalanche is designed to host many “Avalanche L1s” (formerly “subnets”) that can carry their own execution environments and economic rules. AVAX can still be the coordination asset, but the platform does not force every chain to route end-user value capture through AVAX the way a single-chain design can.

From an allocation fairness lens, this is the core tension: you can fund builders and attract ecosystems by letting chains customize their economics, but every customization option weakens the guarantee that AVAX holders automatically benefit from adoption.

Supply policy: capped, but governed, with minted staking rewards

AVAX has a capped supply at 720,000,000 tokens, with 360,000,000 minted in the genesis block and the remaining supply minted over time via staking rewards.

That cap also makes AVAX structurally different from uncapped designs like Dogecoin’s supply.

As of March 6, 2026, CoinGecko shows 431,771,961 circulating supply, 463,441,061 total supply, and the 720,000,000 max supply based on its circulating supply fields.

Two mechanics drive how fast the network walks toward that cap:

1) Minting for security. Avalanche mints rewards to validators (and delegators indirectly) according to a formula that explicitly references the remaining un-emitted supply: MaximumSupply = 720,000,000 AVAX, and rewards scale with factors like stake size and staking period.

2) Burning for usage. Transaction fees are burned, permanently removing AVAX from circulating supply.

The protocol docs are unusually clear that these flows are not “recycled” internally. Validator rewards are minted on the P-Chain, and fees are burned rather than paid out to validators.

Staking is also parameterized in a way that shapes who can realistically participate. The defaults include 2,000 AVAX minimum validator stake, 25 AVAX minimum delegation, 2 weeks minimum staking duration, and 1 year maximum staking duration. For a primer on the common questions these parameters raise in models, see our FAQ.

Finally, Avalanche uses an all-or-nothing reward eligibility rule tied to uptime. Uptime requirement tightening is proposed in ACP-267, which raises eligibility from 80% to 90% to remain eligible for rewards.

One more economic choice is worth calling out. Avalanche does not slash staked principal in the core model described in official docs. The punishment for poor behavior is forfeiting rewards rather than losing stake.

Genesis allocation: the power map

Genesis allocation is where long-run “fairness” usually dies or survives. It sets who can fund ecosystems without asking permission, who can lean on markets via distribution, and who gets to be patient while everyone else needs liquidity.

The most load-bearing fact in AVAX distribution is that half the cap is reserved for staking rewards over time, while the other half was minted at genesis and distributed across sales and internal or quasi-internal buckets. If you want adjacent context across networks, we publish ongoing tokenomics research that tracks how these choices tend to play out.

Below is the canonical breakdown shown in widely-circulated AVAX distribution materials. Percentages are of the 720,000,000 max supply. Token amounts are computed mechanically as (percentage × 720,000,000).

Fairness critique, stated plainly: this distribution is builder-friendly because it funds ecosystem spend and incentivizes long-horizon security. It is also concentration-prone because the non-staking half includes multiple large discretionary buckets (team, foundation, strategic partners, endowments) that can become a long-lived sell-overhang if they are treated as operating budget rather than as scarce capital.

Vesting helps. It does not remove discretion. It mostly time-shifts it.

Utility, fees, and fiscal flows: burn everything, mint for security

The AVAX “cashflow loop” is intentionally simple.

Users pay fees in AVAX, and the protocol burns them. Avalanche’s official docs state that transaction fees are paid in AVAX and burned.

On C-Chain specifically, fee mechanics are described as EIP-1559-style dynamic fees, and Avalanche burns both the base fee and the priority fee.

Validators do not get paid those fees. The token economics paper makes this explicit: fees are burned rather than distributed to validators.

Validators get minted rewards instead. Rewards are minted on the P-Chain, independent of fee burning.

This design avoids the obvious “MEV-or-fees arms race” that can centralize block production. But it also means the network’s long-run security budget must come from ongoing issuance until burn rates meaningfully offset it, and that depends on usage.

Where AVAX economics get tricky is Avalanche L1 flexibility. Official materials note that on Avalanche L1s, networks may designate different assets for gas and staking, separating user fee UX from validator economics.

That is great for adoption. It reduces friction for apps that want stablecoin gas or app-specific incentives.

It is not great for “AVAX automatically accrues from ecosystem growth” narratives. If a meaningful share of activity migrates to L1s where users do not need AVAX, then fee-burn-driven scarcity becomes less sensitive to real adoption. In that world, AVAX’s primary structural demand is staking and whatever fees remain on the Primary Network, not “Avalanche the brand.” The token can still win, but the link is weaker by design.

Governance reality: parameters are “governable” but control is gated

Avalanche’s token dynamics paper describes a governance model where key parameters can be modified dynamically, with system-wide polls and “hysteresis” constraints intended to prevent abrupt changes.

That is the aspiration. The practical surface area that AVAX holders can influence is narrower and more upgrade-mediated than many people assume.

Example: Avalanche’s staking materials note that the 25 AVAX minimum delegation amount is baked into the genesis block as a network parameter, and changing it would require a network upgrade. They also note the plan has been to make parameters “decided by consensus (e.g. voting), but that code hasn’t been written yet.”

In practice, Avalanche’s improvement process is formalized through Avalanche Community Proposals (ACPs), with a workflow centered on public discussion and implementation.

The ACP system is real governance infrastructure. It still is not the same thing as direct, on-chain tokenholder parameter voting with binding outcomes. If you are modeling “governable monetary policy,” you should treat it as upgrade-governance. That means fewer decision-makers in the loop, more coordination cost, and a different set of capture risks.

Even modest economic shifts matter. ACP-267 is a clean example of policy tightening: increasing validator uptime requirements from 80% to 90% to receive rewards.

For a useful point of comparison on PoS design tradeoffs, see our Cardano tokenomics review.

Risk register: concentration, value-capture leakage, and policy uncertainty

Avalanche’s design is coherent. It also concentrates a lot of long-run outcomes into a few levers: who holds large discretionary balances, whether L1 growth routes through AVAX, and how predictable the network’s economic parameters remain.

Dominant risk: concentration plus discretion in the genesis distribution creates persistent sell-pressure optionality and soft governance power that is hard to price.

The headline “team = 10%” looks moderate in isolation. The real issue is the cluster of buckets that are operationally adjacent: foundation, strategic partners, community endowment, plus any large holders from sales. These are not passive holdings. They are designed to be spent, granted, partnered, or distributed.

That spend can be productive. It is also structurally asymmetric. Regular holders absorb uncertainty while the allocator holds the option: slow distribution when markets are weak, accelerate when there is a strategic push, or re-route incentives across narratives. Vesting schedules reduce immediate dumping risk, but they do not remove the core governance problem, which is that large pools of AVAX exist specifically to be deployed by a small set of decision-makers.

The mechanism-level consequence is reflexive. If markets expect discretionary supply to overhang price, price weakens. If price weakens, the cost of security (denominated in AVAX) rises in “real terms,” pushing the network to rely more on issuance to keep staking attractive. Rewards are minted, not paid from fees.

Now you are in a regime where (1) burn is uncertain because it depends on activity, and (2) staking rewards are a policy variable that can be adjusted within a governance process described as “governable,” but implemented through upgrades and ACP coordination.

None of this guarantees a bad outcome. It does set a higher bar for transparency. If you want AVAX to be a credibly neutral asset, you need credibly neutral disclosure about how discretionary pools are deployed, and you need a market that believes those deployments are net accretive rather than dilution disguised as “incentives.” Public docs are not thin on mechanics. They are thinner on forward policy commitments around treasury behavior.

Builder incentives vs concentration risk is the trade. Avalanche chose strong builder incentives. The cost is that AVAX holders must underwrite allocator discretion for a long time.

Top 3 risks

  1. Concentration and discretionary distribution overhang. Trigger: large scheduled unlocks, major ecosystem incentive waves, or elevated operating spend from large allocation buckets. Mechanism: high-conviction allocators can convert AVAX to fund programs, creating persistent sell-side liquidity that outpaces organic fee-burn demand; market anticipates this and reprices the risk premium. Who bears it: liquid holders first, then validators/delegators via weaker price support and more reliance on issuance for attractive yields. Measurable indicators: on-chain transfers from known foundation/treasury addresses to exchanges, changes in outstanding supply/circulating supply, and publicly disclosed grant or incentive program sizes relative to network fee burn.

  2. Value-capture leakage as Avalanche L1s decouple from AVAX. Trigger: flagship L1s choose non-AVAX gas tokens or user abstractions that minimize direct AVAX usage. Mechanism: lower fee-driven burn and weaker transactional demand for AVAX, leaving staking demand as the main structural sink; AVAX becomes “security collateral” more than “usage rent.” Who bears it: long-only AVAX holders and ecosystem participants who expected adoption to translate into burn-driven scarcity. Measurable indicators: burn rate trend versus minted rewards, share of activity occurring on environments where AVAX is required for gas, and public L1 configurations that designate alternative gas/staking assets.

  3. Economic parameter and upgrade uncertainty. Trigger: changes to staking eligibility, fee dynamics, or reward settings via upgrades, or rapid iteration in ACP-driven best practices that effectively redefines “standard” validator economics. Mechanism: shifts in validator ROI and operational constraints can change staking participation, security margins, and the emission path implied by the reward formula. Who bears it: validators and delegators (direct), and application teams (indirect) via changing reliability and cost structure. Measurable indicators: ACP volume and adoption affecting validator economics, changes like uptime requirement adjustments, and realized staking participation relative to expectations.

If you are designing around these risks, you end up doing less “tokenomics theory” and more operational policy: disclosures, spend rules, and clear commitments on how incentives map to measurable adoption outcomes. That is where tokenomics consulting is actually valuable, because it forces treasury behavior and distribution policy into modelable constraints instead of vibes.



This article is part of our Tokenomics Deep Dive series.