Avalanche is a layer-1 blockchain that uses a probabilistic consensus protocol called Snowman to finalize transactions in under one second across a network of three coordinated chains. The C-Chain runs an EVM-compatible smart contract environment, the X-Chain handles asset issuance and transfers using a UTXO model, and the P-Chain coordinates validators and the network of sovereign chains formerly known as subnets. Following the Avalanche9000 upgrade activated December 16, 2024, those subnets are now called Avalanche L1s, and the cost to launch one dropped from a 2,000 AVAX continuous stake to a flat monthly fee starting at 1.33 AVAX per validator.
​

This guide explains how Avalanche works in 2026, what changed with the Etna hard fork, how the C-Chain compares to Ethereum L2s and Solana, the AVAX tokenomics that govern issuance and burning, and how stablecoins move on the network through Circle's Cross-Chain Transfer Protocol and other rails. It covers gaming chains like Beam, institutional deployments from JPMorgan Onyx and Citi, the developer toolchain via AvaCloud, and how Eco Routes settles USDC across Avalanche alongside fourteen other chains.
​

Avalanche launched mainnet on September 21, 2020, after Ava Labs, founded by Cornell professor Emin Gün Sirer, raised $42 million in a public token sale. The network is built around a family of consensus protocols collectively called Snow, with Snowman serving as the linear-chain variant used by the C-Chain and P-Chain. Snowman replaces the energy-heavy proof-of-work consensus of Bitcoin and the slower BFT finality of older proof-of-stake chains with repeated random subsampling: validators query small random samples of peers, gather their preferences, and converge on a single answer in milliseconds.
​

As of Q1 2026, Avalanche secures roughly $1.6 billion in total value locked across its DeFi protocols according to DeFiLlama, with the C-Chain accounting for the majority. The network processes more than 4 million transactions on an average week and has approximately 1,300 validators staking AVAX to secure the primary network. Subsecond finality and the EVM-compatible C-Chain are the features that drove early adoption among DeFi protocols looking for faster settlement than Ethereum mainnet without abandoning Solidity tooling.
​

Avalanche is not a single chain. It is a heterogeneous network of chains, each of which can carry its own VM, its own validator set, and its own gas token. The Primary Network — the C-Chain, X-Chain, and P-Chain — is mandatory for all validators. Beyond that, anyone can deploy an L1 with custom rules. Beam, a gaming-focused L1, runs its own validator set and uses BEAM as its native gas token. DeFi Kingdoms operates a separate L1 with JEWEL as its gas token. The flexibility to issue purpose-built chains is the architectural bet that distinguishes Avalanche from monolithic L1s like Solana or modular rollup ecosystems like Ethereum.
​

Avalanche's three-chain Primary Network divides labor by transaction type. The C-Chain, or Contract Chain, runs the Avalanche-customized version of go-ethereum called Coreth. It handles all smart contract activity, ERC-20 transfers, and DeFi protocol logic. Block time on the C-Chain is approximately two seconds, and finality is achieved within the same block thanks to Snowman consensus rather than the probabilistic finality of Ethereum's longest-chain rule.
​

The X-Chain, or Exchange Chain, uses a UTXO model and the Avalanche consensus protocol (a DAG-based variant of Snow) to handle native asset creation and peer-to-peer transfers. Most retail users never interact with the X-Chain directly; it sits beneath wallet UIs that handle the cross-chain shuffles automatically. The P-Chain, or Platform Chain, is where validators register, where staking and delegation happen, and where the registry of all Avalanche L1s lives. Cross-chain transfers between X, P, and C use atomic export and import transactions that settle within seconds.
​

Snowman consensus works as follows. When a validator receives a new transaction, it queries a small random sample of other validators (the default sample size, K, is 20). Each queried validator returns its current preference. If a supermajority — by default, alpha is 15 of 20 — votes the same way, the querying validator updates its own preference and increments a confidence counter. After enough consecutive successful queries (beta, default 20), the transaction is considered finalized. The protocol is metastable: small biases compound rapidly into network-wide agreement. The full mechanism is described in the Snow whitepaper.
​

The result is finality in roughly 0.8 to 1.5 seconds for the C-Chain, depending on validator distribution and network conditions. That is materially faster than Ethereum mainnet (≈12 seconds with two-epoch reorg risk before economic finality at ~13 minutes) and competitive with Solana's optimistic confirmation time of ~2.5 seconds, though Solana's TowerBFT finality lands later at roughly 12-13 seconds.
​

Avalanche9000, activated via the Etna hard fork on December 16, 2024, was the largest protocol change in Avalanche's history. The upgrade implemented seven Avalanche Community Proposals, the most consequential being ACP-77, which restructured how sovereign chains relate to the Primary Network. Subnets, the original term for application-specific chains, were renamed Avalanche L1s and decoupled from the requirement to validate the Primary Network.
​

Before Etna, every subnet validator was required to also stake 2,000 AVAX and validate the C-Chain, X-Chain, and P-Chain. That was a hard cost barrier: at AVAX prices in late 2024 hovering around $40 to $50, a 2,000 AVAX stake represented an $80,000 to $100,000 outlay per validator before any subnet-specific economics. After Etna, L1 validators pay a flat continuous fee on the P-Chain. The base rate is 1.33 AVAX per validator per month, adjustable by governance, and L1 validators are no longer required to validate the Primary Network. The minimum requirement to launch an L1 with a single validator dropped by more than 99 percent.
​

The economic implication of this change is significant. A team launching a gaming chain, a payments rollup, or an institutional permissioned chain previously needed multiple millions of dollars in AVAX collateral just to operate a small validator set. After Etna, the same team can run a 5-validator L1 for under 7 AVAX per month in protocol fees. Existing subnets were grandfathered into a 12-month transition window during which they could elect to migrate to the new fee structure or maintain their pre-Etna staking arrangement. Most active L1s, including Beam and Dexalot, completed migration in the first quarter following the upgrade.
​

The other ACPs in the upgrade addressed scaling. ACP-103 dynamically scales C-Chain gas limits in response to demand. ACP-118 introduces signature aggregation primitives that let L1s coordinate without trusting a single validator. ACP-125 reduces the C-Chain base fee, lowering transaction costs for the EVM-compatible chain. ACP-131 added a configurable minimum gas price for L1s, giving deployers explicit control over their fee floor. The Avalanche Foundation announced a follow-on ecosystem program called Retro9000 that allocated up to 40 million AVAX in retroactive grants to L1 builders. The first cohort of Retro9000 grants, distributed in mid-2025, went to roughly 30 teams across gaming, DePIN, and consumer applications.
​

AVAX is the native asset of the Avalanche Primary Network. The token has three roles: it pays gas on the Primary Network, it secures the network through staking, and it is burned as part of every transaction's base fee. The maximum supply is capped at 720 million AVAX. As of Q1 2026, circulating supply sits near 415 million according to CoinGecko, with the remainder vesting through staking rewards over the long emission curve.
​

Staking on the P-Chain requires a minimum self-stake of 2,000 AVAX for a validator and 25 AVAX for a delegator. Validators choose their own commission rate (between 2 and 100 percent) and a stake duration (minimum 14 days, maximum 365 days). Annualized staking yield averaged 7-8 percent through 2025 and adjusts dynamically with total staked supply. Approximately 55-58 percent of circulating AVAX is staked at any time, a high participation rate compared to other proof-of-stake L1s.
​

The burn mechanism, introduced through Apricot Phase 3 in 2021, removes AVAX from circulation in proportion to network activity. Every C-Chain transaction's base fee is burned rather than paid to validators, mirroring Ethereum's EIP-1559 design. As of early 2026, more than 5.4 million AVAX has been burned cumulatively across the network's lifetime, with daily burns ranging from 1,000 to 8,000 AVAX depending on activity. Burns are tracked at Avascan.
​

Stablecoin supply on Avalanche reached approximately $2.4 billion as of Q1 2026, with USDC accounting for the majority of issuance. USDC is natively issued on the C-Chain by Circle and is fully redeemable through Circle's institutional rails. Native USDC on Avalanche uses the standard ERC-20 interface and integrates directly with Circle's Cross-Chain Transfer Protocol, allowing burn-and-mint transfers between Avalanche and any other CCTP-supported chain — Ethereum, Arbitrum, Base, OP Mainnet, Polygon PoS, Solana, and others.
​

USDT is issued on Avalanche by Tether, with circulating supply around $400 million as of Q1 2026 according to Tether's transparency report. EURC, Circle's euro-denominated stablecoin, is also natively issued on the C-Chain and supported by CCTP. Beyond fiat-pegged stables, decentralized options include MakerDAO's DAI (bridged from Ethereum) and Frax's FRAX. Stablecoin payments are increasingly the dominant transaction category on Avalanche, with C-Chain stablecoin transfer volume averaging $300-500 million weekly through 2025.
​

For developers building stablecoin payment flows that span multiple chains, the choice is rarely "Avalanche only." Most production teams need to accept stablecoins from users on Ethereum, route to USDC on Avalanche for execution, and settle to a treasury on Base or Solana. Eco Routes coordinates these flows by accepting an intent to deliver USDC on Avalanche and selecting solver liquidity across the source chains, returning settlement in approximately 30 seconds versus the 8-15 minute window for canonical CCTP burn-and-mint.
​

The L1 ecosystem has grown beyond the original Avalanche-led subnets. As of early 2026, the Avalanche Foundation lists over 50 active L1s, with several driving meaningful onchain activity.

Each of these L1s makes a different trade-off between sovereignty (running their own validators), economics (custom gas tokens), and security (relying on Avalanche's interchain messaging primitives rather than fully independent finality). The Foundation maintains a directory of live L1s at stats.avax.network.
​

The biggest engineering question for any multi-chain network is how chains coordinate without a trusted intermediary. Avalanche's answer is Interchain Messaging (ICM), formerly branded Avalanche Warp Messaging, which uses BLS signature aggregation to let any L1 validator set sign messages that any other L1 can verify. Teleporter is the higher-level smart contract framework that wraps ICM with developer-friendly APIs.
​

The mechanism works as follows. When an L1 wants to send a message — for example, "burn 100 USDC on chain A and mint 100 USDC on chain B" — its validators produce BLS signatures over the message hash. The aggregated signature is much smaller than the individual signatures and is verifiable on the destination chain in a single operation. The destination chain checks that signers represent a sufficient stake-weighted threshold of the source chain's validator set, then executes the message. There is no external relayer trust assumption; the security is the source chain's own validator set.
​

Teleporter is used in production by Beam to bridge BEAM tokens to the C-Chain, by DeFi Kingdoms for cross-realm asset transfers, and by AvaCloud-deployed L1s for default cross-L1 messaging. ICM does not solve the problem of cross-chain liquidity — moving fungible assets between L1s with the same underlying token requires a burn-and-mint contract on both sides, which Teleporter provides as a library.
​

AvaCloud is Ava Labs' managed L1 deployment service. It abstracts the operational work of running validators, configuring chain parameters, and integrating standard tooling. A team that wants to launch its own Avalanche L1 can do so through AvaCloud's web console without writing custom validator code. The service handles validator hosting, RPC infrastructure, indexing, and a default block explorer. AvaCloud also exposes a programmatic API for chain configuration, so deployment can be automated as part of a CI/CD pipeline rather than performed manually.
​

For self-hosted deployments, the open-source avalanche-cli tool installs and configures local nodes, generates L1 genesis files, and manages cross-chain configurations. The Avalanche Subnet-EVM repository provides a configurable EVM that supports custom precompiles for permissioning, fee management, and KYC enforcement at the protocol level. Institutional deployments often use Subnet-EVM with custom precompiles to enforce allowlist-based access. JPMorgan's Onyx pilot for tokenized deposits is one example, where the precompile gate-keeps every transaction against an offchain KYC registry maintained by the bank.
​

Standard tooling for Avalanche development includes Hardhat, Foundry, ethers.js, and viem. The C-Chain RPC is fully Ethereum-compatible, so the same dApp code that runs on Ethereum mainnet runs on Avalanche with only a chain ID change in the deployment script (chain ID 43114 for mainnet, 43113 for Fuji testnet). Indexing is available through Goldsky, Subsquid, and the Graph. Wallet support is broad: MetaMask, Core (Ava Labs' first-party wallet), Rabby, Phantom (for Avalanche-supported assets), and most major embedded wallet SDKs ship Avalanche network configurations out of the box.
​

Avalanche occupies a specific point in the L1/L2 design space that is worth comparing directly to its closest peers.
​

Versus Ethereum L2s (Arbitrum, Optimism, Base): Avalanche L1s have full sovereignty over their validator set and can burn and mint native assets. Ethereum L2s inherit Ethereum's security but pay for it with sequencer dependence, withdrawal delays of 7 days for optimistic rollups, and no ability to issue native gas tokens that aren't bridged. Avalanche L1s give up Ethereum's security in exchange for full chain customization. For a gaming chain that needs sub-second confirmation and a custom gas token, an Avalanche L1 is structurally better than an L2. For a DeFi protocol that needs deep shared liquidity, an Ethereum L2 wins.
​

Versus Solana: Solana is a single global state machine with high throughput (>3,000 sustained TPS in steady state) and ~2.5 second optimistic confirmation. Avalanche's C-Chain runs at ~50-100 TPS in production with similar finality, but the L1 architecture allows horizontal scale: a portfolio of L1s collectively processes far more transactions than any single chain could. Solana's monolithic design is simpler operationally but creates global congestion when any single application spikes. Avalanche's subnetting isolates congestion to the affected L1.
​

The trade-off is liquidity fragmentation. A token issued on Avalanche L1 X is not natively the same asset as the same token on L1 Y; bridging is required. Solana avoids this entirely. Ethereum L2s share Ethereum mainnet liquidity (with bridging cost). Avalanche bets that ICM and Teleporter make the fragmentation manageable for production use cases.
​

Avalanche has found product-market fit in three categories that exploit its specific architecture: gaming, institutional pilots, and tokenized real-world assets.
​

Gaming. Beam, GUN, DeFi Kingdoms, and Dexterity collectively account for the bulk of L1 activity. Game developers value sovereign chains because they can subsidize gas (sponsored transactions are simple to implement at the validator level), issue custom in-game assets without competing for Ethereum blockspace, and run their economy on a chain whose performance they control. The Beam SDK has been used by 100+ studios. Onboarding flows that abstract wallet creation behind email login, common in Web2 games, are easier to implement on a sovereign chain than on a shared L2 because the L1 operator controls the gas-sponsorship policy at the protocol level.
​

Institutional pilots. JPMorgan's Onyx ran a tokenized portfolio rebalancing pilot on a permissioned Avalanche subnet in collaboration with WisdomTree and Apollo, demonstrating cross-fund collateral movement with KYC enforced at the protocol level. Citi has piloted similar tokenized deposit settlement on Avalanche infrastructure, focusing on intraday liquidity transfers between affiliate banks. Franklin Templeton and Hamilton Lane have explored Avalanche-based deployments for tokenized money market and private credit funds. The appeal for institutions is the ability to deploy a chain where every validator is known and KYC'd, while still benefiting from public-chain tooling.
​

Tokenized RWA. Securitize, Ondo Finance, and Backed all maintain Avalanche deployments for tokenized treasuries and equity. As of Q1 2026, Avalanche hosts approximately $370 million in tokenized RWA assets according to RWA.xyz. The Avalanche Vista program, announced in 2023, committed $50 million of AVAX-treasury capital to support RWA tokenization on the network. Vista has anchored partnerships with KKR, Hamilton Lane, and other private-markets issuers seeking onchain distribution rails for tokenized fund interests.
​

Payments. A growing share of Avalanche C-Chain volume is stablecoin payment activity. Merchants accepting USDC through processors like BVNK and Bridge increasingly route settlement to Avalanche when destination wallets sit on the chain, taking advantage of subsecond finality and per-transaction fees that average $0.02 to $0.05. Cross-border B2B settlement on Avalanche has grown alongside the broader stablecoin payments wave that Artemis tracks across the top 15 chains.
​

For teams whose product is moving stablecoins to and from Avalanche, the canonical CCTP path works but is slow (8 to 15 minutes for full attestation) and limited to USDC. Eco Routes treats Avalanche as one of fifteen supported chains and routes USDC, USDT, and other major stablecoins through a network of solvers who pre-position liquidity on each chain. A user with USDC on Ethereum who wants USDC on Avalanche submits an intent through the Routes API or CLI. A solver fills it within roughly 30 seconds and is later reimbursed via the underlying canonical bridge. The user gets near-instant settlement; the solver assumes the bridging time risk.
​

The result is that an integration which used to require separate code paths for CCTP USDC, LayerZero OFT USDT, and a Wormhole or Hyperlane fallback now collapses into a single intent submission. For developers building treasury automation, OTC desks, or payment products that touch Avalanche alongside Base, Solana, Arbitrum, and the rest of Eco's supported chains, Routes provides a single integration that abstracts the chain-by-chain complexity. The CLI and API documentation is at docs.eco.com.
​

Avalanche is a Layer 1 blockchain with its own consensus protocol (Snow), validator set, and native gas token (AVAX). It is not a rollup or sidechain of any other network. Avalanche L1s, formerly called subnets, are sovereign chains that run their own validators rather than inheriting security from Ethereum.
​

Avalanche9000, activated through the Etna hard fork on December 16, 2024, restructured the subnet model, renaming subnets to Avalanche L1s and replacing the 2,000 AVAX validator stake requirement with a flat continuous fee starting at 1.33 AVAX per validator per month. It cut the cost of launching an L1 by more than 99 percent.
​

Avalanche's C-Chain finalizes transactions in roughly 0.8 to 1.5 seconds versus Ethereum mainnet's 12-second block time and ~13-minute economic finality. The speed comes from the Snowman consensus protocol, which uses repeated random subsampling rather than longest-chain proof-of-work or full BFT rounds.
​

Yes. Circle issues native USDC directly on the Avalanche C-Chain and supports it through the Cross-Chain Transfer Protocol. Native USDC is fully redeemable through Circle's institutional rails and uses standard ERC-20 interfaces. Total stablecoin supply on Avalanche reached approximately $2.4 billion as of Q1 2026.
​

Avalanche L1s support custom virtual machines, custom gas tokens, custom validator sets, and protocol-level precompiles for permissioning or fee logic. Production L1s include gaming chains (Beam, GUN, DeFi Kingdoms), institutional permissioned chains (JPMorgan Onyx pilots), and specialized DeFi venues (Dexalot's onchain order book).
​