A token is a digital unit or individually identified record whose balances or ownership are tracked under a ledger's rules. In digital-asset markets, the word often means an asset implemented by a smart contract on an existing blockchain. For a quant, a token balance tells you how much of a particular instrument is recorded; its market value and the holder's economic rights require separate information.
“Token” also has broader usage, sometimes including native cryptocurrencies. A common distinction calls the network's native asset a coin and a contract-issued asset a token, but terminology varies. Ether, for example, is Ethereum's native cryptocurrency and pays for transaction execution; an Ethereum token can have a separate balance maintained by a contract. Ethereum's technical introduction to ether explains the native asset's role.
Interchangeable units or distinct records?
A fungible token treats units of the same token as interchangeable. The balance is a quantity: transferring part of a holding changes the amounts assigned to the sender and recipient. Ethereum's ERC-20 standard defines an interface for balances, total supply, transfers and spending allowances. An allowance authorises a spender up to a specified amount; it is different from transferring that amount immediately.
A non-fungible token, or NFT, distinguishes individual records. Under ERC-721, the contract tracks the owner of each token identifier. An aggregate NFT count therefore does not tell you which items an account holds or whether they have similar prices. The identifier belongs to a particular contract on a particular network.
These standards make software interfaces more consistent. They do not standardise cash flows, asset backing or investors' legal rights. A token following an interface can still have product-specific rules and risks.
A transfer is redistribution
Consider a fictional fungible token with 1000 units in total, held only by A and B. A holds 600 units and B holds 400 units. A then transfers 100 units to B. Assume the transfer succeeds, with no token-denominated fee, minting or burning. Network transaction costs are outside this simplified token ledger.
| Token balance, in units | Before | Change | After |
|---|---|---|---|
| Holder A | 600 | −100 | 500 |
| Holder B | 400 | +100 | 500 |
| Total supply | 1000 | 0 | 1000 |
Original fictional ledger in human-readable token units. Only A and B hold the token; there are no token fees, minting or burning. Bars use the same scale.
The transfer changes who holds the supply. It does not create new units. Minting creates units and burning destroys them; whether these actions are available, and who can initiate them, depends on the token's rules. The example's constant supply is an assumption about this transfer, not a promise that every token has a fixed maximum supply.
Nor does this ledger establish a price. A's remaining balance needs a price in a stated quote currency to produce a marked value. An unchanged total supply can coexist with a changing market price. A limited supply alone does not establish demand, liquidity or a valuation floor.
Identify the instrument before adding balances
For a contract-based token, record the network and contract address, rather than relying on a name or ticker. For an NFT, record the token identifier as well. Normalise the unit convention: a raw contract balance and a wallet's displayed quantity may differ because of decimal formatting. ERC-20's display-decimal metadata is optional, so a data pipeline needs a verified convention rather than an assumed one.
Balances on different networks or under different contracts should not be combined merely because their tickers match. Establish what each instrument represents and how, if at all, it converts into the other. Also distinguish the on-chain record from a provider's account balance: the cryptocurrency article explains why custody arrangements matter.
What does holding it entitle you to?
A token balance does not automatically confer company equity, cash redemption or legal ownership of an external asset. A contract may record an NFT holder while separate terms determine any licence or claim associated with the referenced object. Similarly, a stablecoin label does not itself establish the holder's redemption entitlement.
Read the protocol or contract rules alongside the issuer's terms and connected arrangements. Separate what code permits from what a person or entity is obliged to deliver, and identify who bears the risk if that obligation fails. Legal treatment depends on the arrangement, jurisdiction and applicable law. In Australia, ASIC's INFO 225 assesses the rights and benefits attached to the digital asset and related arrangements, rather than treating the token label as decisive.
Sources
- Ethereum Improvement Proposals, ERC-20: Token Standard: balance, supply, transfer, allowance and optional display-metadata interfaces.
- Ethereum Improvement Proposals, ERC-721: Non-Fungible Token Standard: distinguishable records, ownership tracking and contract-specific identifiers.
- Ethereum documentation, Technical intro to ether: native ether and transaction execution costs.
- Ethereum documentation, Token Standards: fungible and non-fungible interface families.
- ASIC, Digital assets: Financial products and services, INFO 225: Part A, rights, benefits and connected arrangements. Official sources checked 28 October 2026.