Coins vs Tokens: Native Assets and Smart-Contract Tokens
A native coin is part of a network’s own accounting and fee system. A token is an asset represented by application rules, often a smart contract, on an existing network. Labels do not establish rights, safety or value.
How it works
ETH is Ethereum’s native asset; an ERC-20 token is tracked by a particular contract. Token transfers usually require the native asset for fees unless a supported sponsorship mechanism changes the user experience. Wrapped assets add an issuer, contract or bridge relationship rather than becoming identical to the original asset.
Worked example
An address has 100 units of a token and zero ETH on Ethereum mainnet. An ordinary token-transfer transaction can fail to proceed because the address cannot pay the required gas in ETH. Holding a token called “ETH” at an unknown contract address does not automatically solve that problem or make it native ETH.
Amounts, prices and scenarios are fictional teaching examples. They exclude any effects not explicitly stated and are not trade recommendations.
Limits and common mistakes
Ticker names can be copied. The same project name may appear on multiple chains with different contracts and redemption arrangements. Identify chain ID, contract address, issuer rights, upgrade permissions and source documentation before treating two balances as interchangeable.
Knowledge check
Can two tokens share a ticker but be unrelated?
Read the explanation
Yes. Symbols and names are metadata, not globally unique identifiers. Network and verified contract identity are essential.
References and further reading
- Ethereum developer documentation: accounts, transactions and gas
- Ethereum improvement specifications
- Bitcoin Developer Guide: transactions, blocks and consensus
These sources explain the underlying concepts and specifications. They do not endorse QBMFX Academy. Check the relevant market, protocol version and reporting rules before applying an example.