Coins and tokens can look identical in a wallet: a name, a symbol, a balance, and a transfer button. Their relationship to the underlying blockchain is different, however. A coin is generally the native asset of a blockchain. A token is an asset created using a blockchain's existing infrastructure, often through a smart contract.

That distinction helps explain which network an asset uses, what pays its transaction fees, and which additional rules deserve investigation. It does not tell you whether an asset is useful, secure, or valuable. If you are still getting familiar with the broader category, start with our guide to what altcoins are.

What makes a coin native?

A native asset is built into a network's basic accounting and transaction rules. Bitcoin is native to the Bitcoin network. Ether, commonly identified by the symbol ETH, is native to Ethereum. The network's protocol defines these native assets without needing a separate token contract.

Depending on the network, a native asset may pay transaction fees, support the mechanism used to agree on valid transactions, or serve other purposes. These roles vary. Being a coin does not automatically mean an asset is mined, has a fixed supply, or gives its holders voting rights.

When researching a coin, begin with the network itself. Ask how transactions become final, who can participate in validating them, how software changes are adopted, and how the asset enters circulation. The coin's behavior is connected to those protocol choices.

How a token uses an existing network

A token adds a separate set of asset rules to a network. On Ethereum, a token contract can record balances and define how transfers work. The blockchain processes the contract's operations, while the contract supplies the token-specific logic.

The Ethereum documentation for ERC-20 describes a common interface for fungible tokens, including balance queries, transfers, and spending approvals. Fungible means units of the same token are interchangeable. A shared interface helps wallets and applications interact with tokens in a consistent way.

A standard is a technical agreement, however. It does not certify a project's promises, inspect its management, or establish the economic meaning of its token. Two assets can follow the same interface while having very different issuance rules, administrative controls, and purposes.

The word token is also used more broadly in some technical discussions. Treat the coin-versus-token distinction as a useful starting convention, and read the project's actual architecture when precision matters.

Why a transfer can involve two assets

Suppose a fictional project issues Harbor Credits as an Ethereum token. Your wallet shows a Harbor Credits balance, but you want to send some to another address. The asset being transferred and the asset used to pay for processing are separate.

In a standard user-paid Ethereum transaction, the network fee is paid in ETH. Holding Harbor Credits alone therefore does not necessarily provide what you need to send them. A wallet may show a sufficient token balance while explaining that the account lacks the asset needed for fees.

Some applications sponsor fees or arrange payment through other mechanisms, so the interface may hide part of this process. Check what the particular transaction requires. Do not assume every token can pay for its own transfer, or that the fee rules you learned on one network apply elsewhere.

Our wallet guides explain the practical relationship between accounts, supported networks, and asset balances.

Identify the asset beyond its name

A familiar ticker is an incomplete identifier. Names and symbols can be reused, including by unrelated or misleading projects. For a contract-based token, its network and contract address are much more useful identification details.

Imagine seeing Harbor Credits on two networks. One version might be issued directly by the project; another might represent assets moved through a bridge. They might instead be unrelated tokens sharing a name. Their wallet icons would not settle the question.

Build a small identity record before evaluating an unfamiliar asset: its full name, symbol, network, contract address when applicable, and the official documentation connecting those details. Compare the information across the project's documentation and the relevant blockchain explorer. A displayed logo or search ranking is insufficient evidence.

When transferring an asset, the receiving service must support the particular network and asset version. An address that looks familiar does not establish that compatibility.

Wrapped assets make the distinction more useful

Wrapped ether, or WETH, illustrates why an asset's economic reference and technical form should be considered separately. ETH is Ethereum's native asset. WETH represents ETH through an ERC-20 token contract, allowing applications to handle that representation using the token interface.

This does not make ETH and WETH identical in every transaction. A contract expecting a token interface may require WETH, while ordinary Ethereum gas payment uses native ETH. The intended relationship between their values does not remove the operational difference.

Bridged representations introduce further questions. What mechanism connects the representation to the original asset? Who can release the underlying assets? What happens if the bridge pauses? A token described as representing another asset still needs its own dependency review. The DeFi learning hub provides context for understanding how applications combine these components.

Purpose and architecture answer different questions

Coin and token describe an asset's technical relationship to a network. Labels such as governance, utility, or stablecoin describe its intended role. Those are different dimensions, so a single asset can fit more than one description.

A governance token might allow participation in certain decisions, but the exact powers depend on the system. A utility token may be required for a particular activity, although the activity's usefulness still needs examination. A stablecoin aims to maintain a reference value; its name alone says little about the mechanism or whether holders can redeem it.

Ask what possessing the asset actually enables. Separate documented functionality from expectations about future development. An appealing category label cannot substitute for a clear explanation of the asset's role.

Questions that make research more concrete

Once you understand whether you are examining a native coin or a token, use that answer to direct your next questions:

  • Which network records the balance? Confirm the exact network rather than relying on a ticker or an application's default setting.
  • Where are the asset's rules defined? For a token, locate the relevant contract and documentation. For a native coin, examine the network's protocol and governance.
  • Who can change those rules? Look for upgrade powers, issuance controls, transfer restrictions, and the people or processes responsible for using them.
  • What must work for the asset to remain usable? Consider the network, contracts, supporting applications, and any issuer, custodian, or bridge involved.
  • What does the holder receive? Identify the documented function or claim, then investigate the conditions and limitations attached to it.

For a practical exercise, describe a proposed transaction in one sentence: which asset version you are moving, which network records it, what pays the fee, and which application or contract is involved. If you cannot fill in one of those details, you have found a specific question to resolve before proceeding.

Keep your notes separate from a project's promotional language. Record the evidence you checked and any unresolved assumptions. For example, knowing that a token follows a familiar standard answers an interface question; it leaves questions about supply controls and administrative access open. This habit turns a broad impression of familiarity into a more precise account of what you understand.

You do not need to become a programmer to organize these questions. You do need to recognize where an answer is missing. Our guide to researching altcoins develops this process further, and the security guides cover account and transaction precautions.

Use the label to find the next question

A native coin can belong to a poorly designed network. A token can have a clear, useful function while depending on several systems that deserve scrutiny. Neither label establishes quality or determines an appropriate financial decision.

The practical value of the distinction is that it makes the next research step clearer. Identify the network, understand the asset's technical form, check the rules that govern it, and trace its dependencies. With those foundations in place, the projects in our altcoin learning hub become easier to compare on meaningful terms.