Is Avalanche an ERC20 Token

AVAX is the native coin of the Avalanche network, not an ERC-20 token. The ERC-20 standard is a smart-contract interface that lives on top of a blockchain — a set of functions a token contract implements so wallets and exchanges can read its balance and move it. A native coin works at a lower level than that: it is the asset the protocol itself pays validators and charges fees in, and there is no contract behind it to implement a standard. ETH plays this role on Ethereum, BNB on the BNB Chain, and AVAX on Avalanche. So when someone asks whether Avalanche is an ERC-20 token, the precise answer is no — the base asset is a native coin, and only representations of it elsewhere can be ERC-20.

What ERC-20 actually means

ERC-20 is an Ethereum token standard: a contract that exposes functions like balanceOf, transfer and approve so any compatible wallet can handle it the same way. Thousands of tokens follow it, which is why they all slot into the same wallets and exchanges. Crucially, ERC-20 describes tokens that run on a chain — it says nothing about the chain's own native coin.

Why a native coin is different

A native coin is minted and tracked by the protocol itself, not by a separate contract. It pays transaction fees and, on networks that stake, secures the chain. Because there is no token contract, there is no ERC-20 interface to implement. AVAX is minted and managed by Avalanche's consensus layer, which is exactly what makes it native rather than a token sitting on top.

The question comes up for good reasons, not from ignorance. Avalanche's main smart-contract chain, the C-Chain, is EVM-compatible, so the tokens people interact with there look and behave like Ethereum's ERC-20 tokens. Many users also first encounter AVAX as a tradable asset on an exchange or inside a multi-chain wallet, where it sits in the same list as genuine ERC-20 tokens and is hard to distinguish by sight. On top of that, bridges really do create an ERC-20 version of AVAX on Ethereum, so the word ERC-20 and the name AVAX genuinely do appear together — just not for the native coin.

The C-Chain runs Ethereum's code

Because the C-Chain uses the Ethereum Virtual Machine, developers deploy the exact same ERC-20 contracts there that they would on Ethereum. A stablecoin or project token issued on the C-Chain is a real ERC-20 token. That shared standard is a feature — it makes tooling portable — but it leads people to assume AVAX itself must follow the same rule, when AVAX is the gas coin those tokens are paid with.

Wallets blur the distinction

In a wallet's asset list, a native coin and an ERC-20 token are shown with the same icon, name and balance. Nothing on the screen announces 'this one is native and that one is a contract'. So a user holding AVAX alongside ERC-20 tokens reasonably assumes they are the same kind of thing, which keeps the question alive.

The cleanest way to settle the question is to separate the three things people lump together under the name AVAX. There is native AVAX on Avalanche; there is a wrapped, ERC-20 version of AVAX that can exist on Ethereum through a bridge; and there are the many ERC-20 tokens that live on Avalanche's own C-Chain but are not AVAX at all. Each sits on a different chain or follows a different standard, and knowing which one you are looking at tells you immediately whether ERC-20 applies.

Form	Chain	Standard	Main use
Native AVAX	Avalanche (C/P/X)	Native coin — not a token	Gas and staking on Avalanche
Wrapped AVAX on Ethereum	Ethereum	ERC-20 token	Using AVAX value inside Ethereum DeFi
C-Chain tokens (e.g. stablecoins)	Avalanche C-Chain	ERC-20 token	Trading and DeFi on Avalanche

Native AVAX

This is the real AVAX. It lives on Avalanche, pays gas on the C-Chain, and is staked on the P-Chain to help secure the network. It is a native coin with no token contract, so it is not ERC-20 by definition. When you hold AVAX in an Avalanche wallet and spend a little of it to send a transaction, you are using the native coin.

Wrapped AVAX on Ethereum

A bridge can lock native AVAX and issue a matching ERC-20 token on Ethereum that represents it. That token follows the ERC-20 standard because it has to live inside Ethereum's rules, and it tracks the value of the AVAX locked behind it. This is the one case where the phrase 'AVAX as an ERC-20' is technically correct — but it is a representation on Ethereum, not the native coin itself.

ERC-20 tokens on the C-Chain

These are tokens other than AVAX that were issued on Avalanche's C-Chain, such as stablecoins and project tokens. They are ERC-20 because the C-Chain is EVM-compatible, but they are not AVAX. People sometimes see 'ERC-20 on Avalanche' and wrongly conclude that AVAX is one of them.

Part of why AVAX resists a single label is that Avalanche is not one chain but three, each with a distinct job, and AVAX is native across all of them. The C-Chain is the smart-contract chain where ERC-20 tokens live; the P-Chain coordinates validators and staking; and the X-Chain handles asset creation and transfers. Understanding this split explains why native AVAX cannot be an ERC-20: it is the shared asset underpinning a multi-chain system, not a contract deployed on one of them.

Chain	Name	What it does
X-Chain	Exchange Chain	Creating and transferring assets
P-Chain	Platform Chain	Validator coordination, staking and subnets
C-Chain	Contract Chain	EVM smart contracts and ERC-20 tokens

The C-Chain is where ERC-20 lives

The C-Chain runs the Ethereum Virtual Machine, as described in the Avalanche documentation, which is why it hosts ERC-20 tokens and the DeFi applications people use. AVAX is the gas coin here, but the tokens traded here are the ones following the ERC-20 standard — AVAX pays for their movement.

The P-Chain and staking

The P-Chain manages validators and the staking of AVAX that secures the network, and it coordinates subnets. Staking is a native-coin function — you lock AVAX itself, not a token wrapper — which is another reminder that AVAX operates at the protocol level rather than as an ERC-20 contract.

Because wallets display native coins and tokens side by side, the reliable way to know what you have is to check the chain and the contract, not the name. If the asset is sitting on Avalanche and is being used to pay gas, it is native AVAX. If it is on Ethereum and has a token contract address, it is a wrapped ERC-20 representation. A block explorer resolves the question in seconds.

Check the network first

Look at which network your wallet is connected to. Native AVAX appears on the Avalanche C-Chain and is what the wallet deducts for gas. The same wallet connected to Ethereum would show a wrapped AVAX balance as a token, not as the gas coin. The network context tells you most of what you need.

Confirm the contract on an explorer

A native coin has no contract address; a token always does. Look up an Ethereum token on Etherscan or an Avalanche C-Chain token on Snowtrace. If there is a token contract, you are holding an ERC-20; if the asset is simply the gas balance the chain spends, it is native.

The one place AVAX legitimately becomes an ERC-20 is through bridging. A bridge locks native AVAX on Avalanche and mints an equivalent ERC-20 token on Ethereum that stands in for it, letting AVAX value participate in Ethereum-based applications. The wrapped token is genuinely ERC-20, but it is a derivative of the native coin, redeemable one-for-one by burning it and unlocking the original. This is the mechanism that makes both statements true: native AVAX is not ERC-20, yet an ERC-20 form of AVAX can exist.

• Native AVAX is locked in a bridge contract on Avalanche.
• A matching ERC-20 token is minted on Ethereum to represent it.
• The wrapped token moves and trades like any other ERC-20 on Ethereum.
• Burning the wrapped token unlocks the original native AVAX on Avalanche.
• The two always track one-to-one, so the wrapped form carries the native coin's value without being the native coin.

A few persistent misconceptions keep the question circulating, and naming them directly is the fastest way to put it to rest. None of them survive a look at how Avalanche is actually built, but each one sounds plausible enough to repeat.

Myth: AVAX is an ERC-20 because it works with MetaMask

MetaMask supports the Avalanche C-Chain as a network, so it can hold AVAX and C-Chain ERC-20 tokens together. Working in MetaMask does not make an asset an ERC-20 — MetaMask handles native coins on every EVM network it supports. AVAX there is the gas coin, not a token.

Myth: all tokens on Avalanche are AVAX

The C-Chain hosts many ERC-20 tokens, but they are distinct assets issued by different projects. AVAX is the single native coin that pays for all of their transactions. Holding a C-Chain stablecoin is not holding AVAX, and neither one being present changes what the other is.

Myth: wrapped AVAX and native AVAX are interchangeable everywhere

They track the same value, but they live on different chains and follow different rules. Native AVAX pays gas on Avalanche; wrapped ERC-20 AVAX only functions inside Ethereum's ecosystem. You cannot pay Avalanche gas with the wrapped version without bridging it back first.