Coins, tokens and standards: what you actually own

A coin is the native asset of a blockchain — the thing the protocol itself creates and uses to pay fees. A token is an entry in a smart contract that runs on top of a blockchain. Both appear side by side in your wallet, which hides an important difference: the rules governing a coin are the chain's consensus rules, while the rules governing a token are whatever its contract author wrote.

What is a native coin?

The native asset is created by the protocol under its issuance rules and is the unit fees are denominated in. Nobody can mint more outside those rules, freeze your balance, or change what the asset is, without changing the protocol itself and persuading node operators to run the change. That is a high bar, and it is the source of a native coin's credibility.

What is a token?

A token contract keeps a ledger of balances and exposes functions to move them. Your balance is a number in that contract's storage; your wallet reads it and displays it alongside your coins. Transfers are calls to the contract, which is why moving a token still costs the chain's native coin as a fee.

Because the contract is ordinary code, it can implement anything its author chose: a fixed supply, unlimited minting, an owner who can pause transfers, an allowlist, a tax on every transfer. The standard it follows tells you how to call it, not how it behaves.

What do the standards define?

Following a standard means wallets and exchanges can integrate a token without bespoke work. It is an interoperability promise, not a safety certificate — and the approval mechanism it defines is exactly the one covered in our guide to token approvals.

What can a token contract do to you?

• Mint more supply, diluting holders, if the function exists and is callable.
• Freeze or blacklist addresses — a feature regulated stablecoin issuers use deliberately.
• Pause all transfers, sometimes as a security control and sometimes as an exit trap.
• Charge a fee on transfers, so the amount received differs from the amount sent.
• Upgrade behaviour entirely, if deployed behind an upgradeable proxy.

None of these are inherently sinister; several exist for legitimate compliance or safety reasons. The problem is assuming none of them apply. Checking the verified source on an explorer, or a reputable token scanner, takes a minute — our guide to using a block explorer covers where to look.

Why does this matter for fees and wallets?

Holding a token with no native coin means you cannot move it: there is nothing to pay the fee with. This traps people regularly after bridging or receiving an airdrop on an unfamiliar chain. Similarly, a wallet that does not display a token has not lost it — the balance is in the contract, and adding the contract address makes it visible again.

Where does this fit in evaluating a project?

Reading a token's contract is part of the same diligence as reading its documentation. Ask who can mint, who can pause, whether the contract is upgradeable and by whom, and how supply is distributed. Our guide to reading a crypto whitepaper covers the narrative side; the contract is where you check whether the narrative is enforced by anything.

How do wrapped and bridged versions fit in?

A wrapped asset is a token that represents a coin — either the same chain's native coin in token form, so it can be used by contracts expecting a standard interface, or an asset from another chain held by a bridge. Both are tokens, and both carry the token risk model rather than the coin's.

The distinction matters when things go wrong. If a bridge holding the reserves is drained, the wrapped token can trade far below the asset it names while that asset itself is unaffected. Holding the native coin on its own chain is a different position from holding a claim on it elsewhere.

• Check which wrapper you hold: the canonical one recognised by the ecosystem, or a third party's.
• Wrapped assets can be minted by whoever controls the contract, subject to whatever reserves back them.
• Unwrapping usually means using the same bridge in reverse, with the same trust assumptions — see our guide to how bridges work.
• Do not hold a wrapper longer than the use that required it.