Question 1

What is AVAX?

Accepted Answer

AVAX is the native utility token of the Avalanche Primary Network. It is used to pay network transaction fees, provide economic weight for network security through staking, and serve as one of the base units of account across Avalanche's different L1s. AVAX is not equity in an application. Its network role arises from protocol rules: accounts initiating Primary Network transactions pay fees in AVAX, while validators participate in network decisions by staking AVAX and receive rewards when conditions are met.

Question 2

What does each of the Primary Network's three chains do?

Accepted Answer

The Avalanche Primary Network consists of the P-Chain, C-Chain, and X-Chain; they are not different names for the same chain. The P-Chain handles validators, staking, and platform operations at the Avalanche L1 level; the C-Chain is an EVM implementation for deploying and executing Solidity smart contracts; and the X-Chain is used to create and trade Avalanche Native Tokens. This division of responsibilities determines operational paths: interaction with EVM applications is generally completed on the C-Chain, validation and staking operations are handled by the P-Chain, and creating and trading native smart assets fall within the X-Chain's responsibilities. Transaction fees on all three chains are denominated in AVAX.

Question 3

How are AVAX transaction fees determined and handled?

Accepted Answer

When a transaction is executed on the Primary Network, the initiator pays a fee denominated in AVAX, and the protocol permanently burns that AVAX. In other words, fees are not paid to a centralized operator or distributed directly to validators; they are removed from circulating supply. The actual cost depends on the chain being used and the resources required by the transaction; for example, a C-Chain contract call generally consumes more execution resources than a simple transfer. Other Avalanche L1s can choose their own tokens and fee arrangements, so the Primary Network's AVAX fee rules should not automatically be applied to all Avalanche L1s.

Question 4

How do AVAX's supply cap, issuance, and burning work together?

Accepted Answer

AVAX has a supply cap of 720 million tokens, of which 360 million were minted at genesis; the remaining capacity can be minted gradually according to staking reward rules, but protocol minting cannot exceed the cap. Transaction fees are burned, so the “protocol minting cap,” “amount minted,” and “circulating cap after deducting cumulative burns” are not the same figure. Protocol documentation explains that transaction-fee burning and validator-reward minting coexist, and reward minting will generally offset the effect of burns; while far from the supply cap, the asset generally remains in net issuance. Therefore, supply cannot be assumed to necessarily decline merely because burns occur, nor can burns be ignored merely because rewards exist.

Question 5

What role does AVAX staking play in the network?

Accepted Answer

Yes. Primary Network validators stake AVAX to participate in network validation; the current official documentation lists a minimum validator stake of 2,000 AVAX. A validator's stake determines its relative weight in network decisions, rather than every node having equal weight. Holders who do not run validator nodes themselves can participate through delegation, but delegation and direct validation differ in operational responsibilities and conditions. In either form, staking means tokens are locked or restricted under protocol rules for a specified period, rather than being an ordinary balance that can be freely used at any time.

Question 6

Where do AVAX staking rewards come from, and how are they determined?

Accepted Answer

Validators receive newly minted AVAX rewards only after successfully completing their staking period; if they do not complete it successfully, they do not receive the reward. Avalanche's mechanism does not use conventional slashing that forfeits existing staked principal as the treatment for negligent or malicious staking periods; instead, loss of rewards forms the primary economic constraint. Rewards are not a fixed annualized rate. The relationship stated in the documentation is that rewards depend on unminted supply, the proportion of the staked amount relative to current supply, the applicable minting rate, and staking duration; the closer a staking period is to the one-year minting period, the closer the applicable minting rate is to its maximum. The closer supply is to the cap, the less remaining minting capacity there is.

Question 7

What implemented effects has the Helicon upgrade had on the AVAX network and staking rewards?

Accepted Answer

Helicon is an upgrade that took effect on mainnet on September 22, 2026, after which the C-Chain runs the Continuous Execution VM. It changes the C-Chain's execution implementation and should not be generalized as every Avalanche L1 automatically adopting the same execution environment. ACP-285, associated with Helicon, also reduced the minimum consumption rate from 10% to 7.5%, with a linear transition over 90 days after the upgrade; the maximum consumption rate remains 12%. Therefore, reward calculations for shorter staking periods are affected, while the maximum consumption rate for a full one-year period does not change because of this adjustment.

Question 8

How do Avalanche L1s relate to the Primary Network's AVAX rules?

Accepted Answer

Avalanche Mainnet consists of the Primary Network and deployed Avalanche L1s. The Primary Network's AVAX rules serve its own transactions, staking, and security model; an Avalanche L1 can have independent rules and token-economic design. Therefore, an application being in the Avalanche ecosystem does not necessarily mean its transactions must be paid in AVAX or that its validation rules fully inherit those of the Primary Network. To determine the Gas, settlement, and security arrangements for a specific asset or application, the L1's actual configuration must be reviewed.

Avalanche (AVAX) Price

Price of Avalanche (AVAX) Today in USD