How to Distinguish Native Tokens from Wrapped Tokens
Don't rely on token symbols. The key is whether the token is a "native resident" of the chain. Native tokens are the local assets used to pay gas fees and secure the network; wrapped tokens are "migrants" from other chains, issued 1:1 on the target chain by locking the native asset. Their values may be the same, but their uses and risks are completely different.
1. Start with the most intuitive criterion: usage
The core use of a native token is to pay the chain's gas fees and secure the network.
For example, on Ethereum, all transaction fees for sending ETH, deploying contracts, and interacting with dApps must be paid in ETH. The same goes for BNB on BNB Chain and MATIC on Polygon.
Wrapped tokens cannot pay gas fees. Their value lies in letting assets from other chains—like Bitcoin—move to Ethereum to participate in DeFi and trade NFTs.
The difference is: can you use it to pay transaction fees? ETH is always gas; WETH cannot be used as gas.
Completion standard: You have confirmed whether this token can be used to pay transaction fees on its chain.
2. Second method: check the contract address and issuer
Scenario A: Check the official documentation or website.
Take USDC as an example. Circle officially only issues native USDC on eight blockchains: Ethereum, Solana, Avalanche, TRON, Algorand, Stellar, Flow, and Hedera. If you see USDC on other chains (like Fantom or Polygon), it is all wrapped assets—while the value is pegged, the issuer is not Circle.
Scenario B: Use a blockchain explorer (Etherscan, BscScan, etc.) to verify the contract address.
Enter the token's contract address on Etherscan and look at the "Contract Creator" and "Token Name". Native assets usually have verified official contracts with a green checkmark.
Open your wallet, find the token you want to check, and click to view its "Contract Address". Compare it with the official contract address of the native asset on that chain. If they don't match, or if the contract appears to be a third-party bridge contract, it's a wrapped asset.
Token symbols can be faked. Don't just look at the token name (e.g., "USDC"); rely on the contract address, because anyone can create a token with the same name.
Completion standard: You have confirmed the token's contract address on that chain and can determine whether it is the official native contract.
3. Two most confusing examples
ETH vs WETH:
ETH is Ethereum's native asset. It is not ERC-20 compliant by itself and cannot be used directly in dApps that require the ERC-20 standard. WETH is a wrapped version of ETH, minted 1:1 by locking ETH in a smart contract. It is ERC-20 compliant and can be used in DeFi protocols like Uniswap and Aave.
The "WETH/DAI" pair you see on Uniswap uses WETH—because Uniswap only accepts ERC-20 tokens.
Native USDC vs Bridged USDC:
Native USDC is issued directly by Circle, backed 1:1 with reserves, and redeemable for US dollars. Bridged USDC (such as USDC.e on Starknet) is minted on the target chain by a third-party bridge protocol after locking native USDC, and cannot be redeemed directly through Circle.
Completion standard: You can distinguish these two classic cases and apply the same logic to other tokens.
4. Simple decision flowchart
Open your wallet and view the token's contract address.
Search for the chain's official native asset list (go to the official website or a blockchain explorer's official directory).
Compare contract addresses: match = native; no match = wrapped asset.
If they don't match, check the contract's creator/label on the block explorer—it is often labeled "Bridge" or "Wrapped".
Prerequisites
Know how to use blockchain explorers (Etherscan, BscScan, etc.) to look up addresses and contract information.
Be able to find the native asset contract addresses listed in the chain's official documentation.
Common failure reasons
Failure reason: Confusing native and wrapped assets by using a centralized exchange's deposit page to determine "what asset can be deposited".
The assets an exchange supports for deposit do not equal the native properties of those assets. An exchange may support the same token on multiple chains simultaneously, most of which are wrapped versions.
Risk warnings
Wrapped tokens depend on the security of the bridge or custodian: If a third-party bridge is attacked or the custodian has issues, the wrapped token may depeg or even become worthless.
Sending a wrapped token as if it were a native token to an official address will be rejected on-chain or result in loss: Transfers are only recognized when sent to the correct contract address on the correct chain.
Tokens with the same name on certain chains may be outright scams: Always verify the contract address first.
How to confirm you're done
Enter your wallet address in a block explorer and look at the "Token" holdings list—native assets will show as "Native" or with no extra label, while wrapped assets usually carry a "Wrapped" tag or the corresponding bridge label (e.g., "Multichain", "Celer"). After cross-checking, confirm that the token type you hold matches your expectation.
Next step: If you need to swap a wrapped token back to the native asset, use the official unwrapping path (e.g., unwrap WETH via Uniswap, redeem bridged USDC via the respective cross-chain bridge). While holding wrapped tokens, regularly monitor the bridge's security status and official announcements. If you're unsure whether a token you hold is safe, prioritize swapping it for the native asset or moving it to a mainstream exchange for custody.
