Beginner · Lesson 2
Coins, tokens and networks: what you are actually buying
Bitcoin, ether, USDC and a memecoin are not the same kind of object. One runs a network; another is an entry in a contract.
Most people buy their first crypto by typing a ticker into a search box. That habit hides the most important question in the market: what kind of object does the ticker point at? A coin that pays for space in a block, a token that exists only as a row inside a contract, and a receipt issued by a company are three different things wearing the same interface.
Three words used as synonyms
A network is the set of computers that agree on one ledger. A coin is the native asset of that network: it is what the protocol pays the people who secure it, and it is what you must hold to use it. A token is an asset created by a contract running on a network. It has no chain of its own, no independent miners or validators, and no security budget of its own. It rents all three.
That is not a ranking of quality: it is a ranking of dependencies, which is what you are really pricing.
What the native asset pays for
On Ethereum you pay gas in ether. On Bitcoin you pay a fee in bitcoin. On Solana you pay in SOL. The pattern repeats: the native asset is the toll for using the network, and the network's security depends on that toll being worth something.
This gives a native coin a source of demand that a token does not have. It does not give it a stable price, but the link between the asset and the machine that secures it is direct.
A token is an entry in someone else's ledger
When a project issues a token it usually deploys a contract. Inside the contract there is a mapping: address, balance. Your "ownership" is a number in that mapping, and the rules for changing it live in the contract's code.
Worked example. A project deploys a token with a total supply of 100,000,000 units. It places 4% of supply — 4,000,000 units — into a liquidity pool alongside 600,000 units of a dollar stablecoin. Ignoring fees, the opening price implied by simple division is 600,000 ÷ 4,000,000 = 0.15 per token. Later the pool holds 3,000,000 tokens and 900,000 stablecoins, so the implied price is 900,000 ÷ 3,000,000 = 0.30. Nothing about the token changed. The pool's composition changed, because people traded against it.
That is the whole structure in miniature. The price lives in a contract, not in a protocol, and a contract can be upgraded, paused or emptied if it was written with that power and nobody removed it. Reading the contract's admin functions tells you more than reading the project's blog.
The same ticker on four chains
USDC is the clearest example of a naming problem. Versions of it are issued natively on several networks, and other versions are minted by bridges on networks where no issuer operates. They share a ticker and a promise, not a chain. Sending the wrong version to an address is not a small mistake: the receiving network has no record of your transfer, because your transfer happened on a different ledger.
A useful habit is to treat "USDC" as a family name rather than an address. The address includes the network.
The rule that survives every cycle. A token inherits its network's security and its own contract's risk. It does not inherit the network's liquidity, and it does not inherit the network's credibility.
Where the risk actually changes
| Object | Secured by | Main failure mode |
|---|---|---|
| Native coin | The network's own consensus | Consensus failure, or a lasting collapse in fee demand |
| Contract token | The network, plus the contract's code and admin keys | Bug, upgrade, pause, freeze, or a mint function |
| Exchange balance | The company's solvency and operations | Withdrawal freeze, insolvency, account closure |
| Wrapped or bridged asset | The network, the contract, and the bridge | Bridge exploit, or a loss of the backing |
The third row is not an on-chain asset at all. It is a claim on a business, which is the subject of how exchanges work and the distinction beginners skip most often.
Why this is practical rather than pedantic
Suppose you hold two assets of equal value. One is a native coin with a large validator set and years of uninterrupted operation. The other is a token whose contract has an owner key that can mint unlimited supply. The same balance appears on your screen, formatted the same way, in the same list. The second can reach zero through a single transaction nobody can reverse, and the price chart would not have warned you.
You do not need to predict which contracts will fail. You need to know which category you hold, so you can size the position and decide where it is kept.
One question that sorts almost everything
If the issuing team disappeared tomorrow, would the asset still work? A native coin would keep producing blocks. A token in a contract with an upgrade key controlled by that team might keep trading for a while, but the rules could change without your consent.
Check yourself
- What does a token rent from its network, and what must it supply on its own?
- A pool holds 2,000,000 tokens and 500,000 stablecoins. What price does simple division imply, and what does that number fail to tell you?
- Why is a balance on an exchange a different kind of object from a token in your own wallet?
If the third question is not obvious, read How exchanges work next, then Altcoins and tokens. The terms here — smart contract, stablecoin, bridge — are defined in the glossary without circular language.