Short conclusion: a coin is generally the native asset of a blockchain or comparable distributed ledger, while a token is created and managed through a smart contract or token program running on an existing network. Bitcoin on Bitcoin and ether on Ethereum are coins under this technical convention; an ERC-20 asset on Ethereum is a token. The distinction is useful for understanding fees, addresses, network compatibility and technical risks, but it is not a universal legal classification.
How the Claims Were Checked
The technical points below rely primarily on protocol documentation, published standards and original project materials. Bitcoin’s design paper is used for the base-layer example, while Ethereum documentation and EIP-20 establish the difference between Ethereum’s native asset and contract-based tokens. Regulatory texts are used only to show that legal terminology does not necessarily follow the informal coin-versus-token convention.
Where a source provides a publication or last-update date, that date is recorded in the Claim Register. Dynamic matters such as network support, exchange availability and compliance requirements cannot be inferred from a token symbol or an old documentation page. No price, fee, profitability or market-share calculations are required for this comparison, and none are presented.
The Basic Technical Difference
A coin belongs to the base protocol of its network. Its issuance, ownership records and transfers are governed by that network’s consensus rules rather than by a separately deployed token contract. Bitcoin’s original design describes electronic coins and a peer-to-peer network that establishes an agreed transaction history, making BTC the native asset of the Bitcoin system. [1]
Ether provides a second clear example. Ethereum’s official documentation identifies ETH as the network’s native cryptocurrency and states that Ethereum gas fees are paid in ETH. This protocol-level role is one of the most practical signs that an asset is a coin on a particular network. [2]
A token, by contrast, is represented through rules deployed on top of a host network. On Ethereum, the ERC-20 specification defines a standard smart-contract interface for fungible tokens, including functions for checking balances, transferring units and granting spending allowances. The standard helps wallets and applications interact with different tokens through a common set of methods, but it does not make those tokens native ETH. [3]
- BTC on the Bitcoin network: native coin.
- ETH on Ethereum: native coin and the asset used for Ethereum gas fees.
- An ERC-20 asset on Ethereum: token represented by a smart contract.
- An NFT created under ERC-721: also a token, but non-fungible rather than interchangeable unit for unit. Ethereum documentation distinguishes ERC-20 fungible tokens from ERC-721 non-fungible tokens. [4]
This means that “coin versus token” and “fungible versus non-fungible” answer different questions. The first asks whether the asset is native to the network. The second asks whether individual units are interchangeable.
Why “It Has Its Own Blockchain” Is Only a Shortcut
The common explanation that a coin “has its own blockchain” is serviceable for beginners, but the more precise test is whether the asset is native to the ledger on which it is being transferred. A token depends on an additional issuance or representation layer, such as a smart contract, token program or bridge mechanism.
The same economic exposure can therefore appear in more than one technical form. BTC transferred on the Bitcoin network is the native coin. A wrapped representation of BTC issued on another network is a token on that destination network, even if it is designed to track or be redeemable for BTC. Bridge documentation describes mechanisms that lock assets on a source chain and mint corresponding assets on a destination chain. The resulting representation introduces smart-contract, bridge and sometimes counterparty risks that native ownership does not have in the same form. [5]
Migration can also change an asset’s classification. A project may initially issue a token on a host chain and later launch a separate network where a migrated version becomes the native coin. The ticker alone cannot establish which version a wallet, exchange or transaction screen refers to.
Claim Register
| Claim | Verification status | Primary source type and name | Publication or update date | Limitation | What could change the conclusion |
|---|---|---|---|---|---|
| ETH is Ethereum’s native cryptocurrency and is used to pay Ethereum gas fees. | Confirmed | Official network documentation: “What is Ether?” and “Ethereum Gas and Fees” [2] | “What is Ether?” updated July 15, 2026 | The claim concerns Ethereum protocol operation. It does not describe fees on unrelated networks or costs charged by custodial services. | A protocol change replacing ETH as Ethereum’s fee asset would require reassessment. |
| An ERC-20 token is implemented through a standard smart-contract interface rather than as native ETH. | Confirmed | Ethereum Improvement Proposal: EIP-20, “ERC-20: Token Standard” [3] | Created November 19, 2015 | EIP-20 covers one Ethereum fungible-token standard. Other networks and token types use different standards or programs. | A particular asset may migrate, adopt a different contract or become native to a newly launched network. |
| A cross-chain representation of a native coin is technically a token or wrapped representation on the destination network. | Dependent on conditions | Official ecosystem documentation: Ethereum bridge documentation [5] | Updated April 3, 2026 | Bridge designs differ. Some lock and mint, some burn and mint, and others use swaps or protocol-specific mechanisms. | The conclusion changes if the destination asset is independently native rather than contract-issued, or if the bridge architecture changes. |
| “Coin” and “token” are not universal legal categories with identical meanings in every jurisdiction. | Confirmed within the stated scope | EU legislation: Regulation (EU) 2023/1114; US regulatory material: SEC crypto-asset guidance [6] | EU regulation dated May 31, 2023; SEC material updated May 15, 2026 | Legal treatment depends on jurisdiction, asset rights, issuance structure and transaction context. Technical classification does not determine securities, payments, tax or consumer-law status. | New legislation, court decisions, regulatory rules or changes to an asset’s structure could alter its treatment. |
| A particular exchange direction, network or verification procedure is available when a user initiates a transaction. | Unknown until checked | Current operational data required; no qualifying static primary source can establish future availability | Not applicable | Pairs and networks may be unavailable, paused or subject to direction-specific compliance checks. | The live request form, network status and compliance outcome at the time of the operation determine availability. |
After identifying the asset and its network, users can check currently available exchange directions and supported networks. This operational check is not evidence for the technical classification and should be repeated before creating a request.
What the Difference Means in Practice
Network fees may require a different asset
If a wallet holds an Ethereum token but no ETH, it may be unable to submit an ordinary token transfer because Ethereum gas is paid in ETH. A platform may abstract or sponsor fees in some circumstances, but that service-level arrangement should not be confused with the underlying network rule. [7]
The same question should be asked on every network: which native asset pays transaction fees, and does the sending wallet have enough of it? The answer cannot be derived reliably from the token’s displayed dollar value.
The network label matters as much as the ticker
A familiar symbol does not guarantee that two balances represent the same on-chain asset. Wallets can display native coins, contract tokens and bridged versions with similar names. Before sending, the user needs to match the asset, network and, where applicable, the official contract or token identifier.
For example, selecting “BTC” does not by itself establish whether the recipient expects native Bitcoin or a tokenized representation on another network. Sending a technically different version to an unsupported deposit route can make recovery difficult or impossible.
Token rules may include additional control points
ERC-20 defines core transfer and allowance functions, but it does not prescribe one universal supply or governance model. Token implementations can add mechanisms such as minting, burning, transfer pauses, allowlists or blocklists. The existence and control of these functions must be checked in the specific contract and project documentation rather than assumed from the ERC-20 label. [8]
A native coin also has governance and protocol risks, but they arise through network consensus, client software and protocol upgrades rather than solely through a token contract. Calling an asset a coin therefore does not make it automatically decentralised, safe or valuable. Calling it a token does not make it inherently inferior.
Legal status cannot be inferred from the technical label
Regulators often use broader terms such as “crypto-asset” and then classify assets according to their rights, reference assets, issuer structure or economic function. The EU’s MiCA framework, for example, defines categories including asset-referenced tokens, e-money tokens and utility tokens. US regulatory materials likewise use “coins” and “tokens” among several colloquial descriptions while focusing legal analysis on the asset and transaction structure. [6]
Consequently, “it is a coin, not a token” is not a legal, tax or regulatory conclusion. Applicable obligations differ between countries and may change over time.
Risks That the Label Does Not Resolve
- Volatility: both coins and tokens can change sharply in market value. The technical category does not predict price or return.
- Wrong network or asset version: a correct-looking address may still belong to an incompatible network or unsupported deposit route.
- Transaction finality: blockchain transfers generally do not provide a bank-style cancellation process. Bitcoin documentation warns that a confirmed payment cannot simply be reversed and can only be returned by the recipient. [9]
- Contract and bridge exposure: tokens may depend on contract code, administrative keys, issuers, custodians or bridge operators. The exact risk model varies by asset. [5]
- Phishing: fake token pages, wallet prompts and support messages may attempt to obtain seed phrases or induce malicious signatures. Official Ethereum security guidance advises never sharing a seed phrase and highlights phishing websites and wallet-draining transactions. [10]
- Jurisdictional differences: technical classification does not settle whether an asset or service is permitted, regulated or taxable in a particular country.
A Repeatable Check Before Sending or Exchanging
- Identify the network. Do not rely on the asset name or ticker alone.
- Determine whether the asset is native or contract-issued. For a token, obtain the official contract or token identifier from the project’s primary documentation and compare the full value.
- Check the fee asset. Confirm which native coin the wallet needs to submit the transaction.
- Match the receiving route. The recipient or exchange must support the exact asset version and network. Check whether a memo, tag or other destination identifier is required.
- Review additional dependencies. For wrapped or bridged assets, identify the bridge, custody or redemption mechanism rather than assuming equivalence with the native coin.
- Confirm live conditions. Network availability, exchange directions and verification requirements may change. Compliance checks can vary by transaction direction and their results.
- Verify the destination independently. Check the entire address, avoid links from unsolicited messages and consider a small test transfer where fees and platform rules make that practical.
The durable rule is technical rather than promotional: classify an asset on the network where it actually exists. Native protocol asset means coin under the common industry convention; contract- or program-issued asset means token. Then verify the specific network, identifier, fee asset and receiving support, because those details—not the label alone—determine whether a transaction can be completed correctly.
Related Articles
Consultation Locations
Manchester Hospital
Manchester Private Hospital New Court, Regents Place, Windsor
Street Salford, Greater Manchester, M5 4HB.
