What is a crypto token?

A crypto token is a digital unit defined by a blockchain protocol or an onchain program, which can be recorded and transferred through a blockchain. A blockchain can record token ownership in data units such as addresses, accounts or spendable outputs; the token rules then specify how those records are created, transferred, destroyed or restricted.

A token can be used to pay network fees, take part in protocol governance or access a particular feature, and it can also be designed to establish a connection with offchain assets, interests or data. But the existence of a token record onchain does not automatically prove that it has a given price, redeemability, legal right or backing by a real-world asset. Those meanings depend on the token rules and on offchain issuance and service arrangements.

A token is a combination of records and rules

An ordinary reader may picture a token as a digital file sitting in a wallet. In practice, a wallet usually holds the keys needed to authorize transactions and reads token balances or holding records from the blockchain; the token itself is represented by shared state and program rules on the blockchain.

One common design uses a balance table to record "address A holds this many units, address B holds that many". On transfer, the network validates the authorization and the token rules, then decreases the sender's balance and increases the recipient's.

Another design does not maintain total account balances but records a set of outputs that have not yet been spent. A transfer consumes old outputs and creates outputs belonging to the new controller, and the wallet then adds up the relevant outputs into an available amount. Some tokens instead give every unit its own identifier, with the ledger recording who currently controls each one.

Different blockchains implement these records differently; Ethereum and Solana are two such examples. On Ethereum, many tokens have their own smart contract maintaining balances and permissions. On Solana, tokens are usually managed by a shared token program. In Solana, a mint is the onchain record that identifies a particular token and holds its supply along with related permissions such as minting and freezing; a mint address uniquely identifies that token and is not an ordinary wallet address.

How a token differs from a blockchain's native asset

A blockchain's native asset usually belongs directly to the underlying protocol. The network uses it to pay transaction fees, reward participants or support consensus, and node software enforces its balances and transfer rules. A network can, for example, handle its own native asset without any additional token contract.

An application-layer token is instead built on top of an existing blockchain and is usually defined by a smart contract or a shared token program. It inherits the underlying network's transaction confirmation and security rules, but has its own issuance, transfer permissions or other functionality. When transferring such a token, users often still have to pay the network fee in the underlying native asset.

Everyday use of "coin" and "token" is not consistent. Some material calls every blockchain digital unit a token, while other material reserves "token" for application-layer assets. When identifying a specific object, what matters more than the name is whether it is defined by the underlying protocol or by an application, who can change the supply and transfer rules, and which asset pays the transaction fee.

A token from creation to transfer

Record structures vary between networks, but a token usually goes through definition, minting, holding, transfer and destruction.

Defining a token and its permissions

The creator first selects the program or standard the token will follow, and sets a name, display symbol, number of decimal places and related permissions. The name and symbol mainly help interfaces display the token and cannot identify it uniquely; different tokens may use the same name or symbol.

What actually distinguishes tokens is usually a contract address, a mint address or another unique identifier the protocol specifies. A wallet or application that displays assets by name alone may conflate different tokens, so the network and the unique identifier still have to be checked.

Minting new units

Minting increases supply according to the token rules and records the new units to a designated address, account or other holding record. Who can mint, how much can be minted at most, and whether minting permission can be revoked are all determined by the specific design.

Some tokens create a fixed amount once and never add more; some allow an authorized account to keep minting; others change supply according to collateral, rewards or other protocol conditions. A "maximum supply" shown in an interface only carries the corresponding technical meaning when the code and permissions really do limit new supply.

Recording holdings and approvals

A token is recorded under an address, account or other record unit, which usually means its controller can authorize transfers under the rules. Control comes from the corresponding private key, a multi-signature rule or smart contract permissions — not from the token being stored inside a wallet application.

Some standards let a holder authorize another address to transfer tokens on their behalf up to a set allowance. An approval does not send tokens immediately, but the approved party can call the transfer function while the permission is valid. An unlimited allowance or a long-standing approval widens the impact of key compromise, malicious contracts and mistakes.

Transferring or destroying

A transfer checks signatures, balances, permissions and other restrictions under the network and token rules, then updates the sender's and recipient's records. Tokens that follow a common interface are easier for wallets and applications to recognize, but adopting the same standard does not mean every token's additional rules are the same.

Destruction removes tokens from available supply or records them in a state the protocol defines as no longer usable. How that affects total supply and circulation records depends on the implementation; sending tokens to an address that appears to be controlled by nobody is not necessarily equivalent to the destruction operation the protocol defines.

Fungible and non-fungible

Equal amounts of a fungible token can usually be exchanged for one another. One unit of a given token, for instance, serves as the same unit of account as another under the program rules. A balance table only needs to record how much each account holds, without tracking the separate identity of every unit.

A non-fungible token (NFT) instead gives each token its own identifier. A ledger can record the holder of a particular number along with related metadata, so different numbers can point to different objects or attributes.

Non-fungible does not mean a complete image, ticket or physical object is automatically stored onchain. A token may hold only a number and a link pointing to other data; whether the linked content remains accessible long term, who can change it, and what offchain rights the holder obtains all have to be verified separately.

Some standards also let one program manage both fungible units and separately numbered ones. The classification helps in understanding how records work, but on its own it says nothing about a token's purpose, value or rights.

What a token standard specifies

A token standard is a shared interface that lets wallets and applications know how to query balances, initiate transfers or read approvals. It addresses how software interacts with a token; it is not responsible for guaranteeing the token's purpose, an issuer's commitments or security quality.

Fungible tokens on Ethereum, for example, often use an interface standard called ERC-20. ERC is the category for Ethereum application-layer standard proposals; ERC-20 specifies basic interfaces such as balance queries, transfers and approvals, so different applications can call standard-compliant contracts in the same way.

A consistent interface still does not mean identical implementation. A token can add transfer fees, pausing, freezing, allowlists, blocklists or other logic, and it may also deviate from what the standard expects because of an implementation error. When integrating a token, an application still has to handle the specific contract's return conventions, permissions and exception cases.

Other blockchains may use a shared token program instead of deploying a similar contract for every token. For example, Solana's token program handles minting, account balances and transfers in one place, with each mint recording supply and optional minting or freezing permissions. That shows a token standard is an approach to compatibility rather than a single technical structure.

What a token can represent

A token's onchain functionality and what it claims to represent have to be considered separately. Common designs include:

• Network or application use: paying fees, using a feature or meeting an access condition.
• Governance use: submitting proposals, voting or delegating weight under protocol rules.
• Value reference: attempting to maintain a relationship with a reference asset through reserves, collateral or an algorithm.
• Certificate or receipt: recording a deposited asset, a completed operation or an acquired standing.
• Unique identifier: using a unique number to associate a digital item, account standing or real-world object.

The same token can serve several functions at once, and its function may later change through an upgrade or governance. A display name containing "dollar", "gold", "certificate" or a brand is not enough to prove that the issuer holds the corresponding asset, or that the holder has redemption, ownership or other offchain rights.

Where a token is connected to an offchain asset or service, also examine who safeguards the asset, who maintains the register, how redemption works, and what happens in the event of a shortfall or a service ending. A blockchain can record token transfers, but it cannot by itself verify that those offchain arrangements have been honoured.

Supply is more than a single number

Total supply usually means the number of units created under the token rules and not yet destroyed under those rules. Maximum supply refers to the upper limit the design claims to allow, but some tokens have no fixed limit, and some limits can be affected by upgrade or administrative permissions.

Circulating supply attempts to describe the portion currently able to move among markets or users, and may exclude locked, vesting or reserve tokens, or those held by particular parties. It usually depends on a chosen methodology rather than a single field that every blockchain provides directly.

Supply figures shown by wallets, block explorers and data sites may therefore differ. When comparing them, confirm whether the figure counts units minted, not destroyed, able to circulate, or estimated at a point in time — and check who holds permission to keep minting, freeze or upgrade.

Who can change a token's rules

Whether a token can be changed after deployment depends on its program structure and permissions. Common control capabilities include:

• creating new units, by whoever controls the minting permission;
• destroying specified units, by holders, approved parties or accounts explicitly granted the ability to destroy, depending on the particular code and authorization;
• pausing all or some transfers;
• freezing or unfreezing certain accounts;
• changing fees, lists or other parameters;
• upgrading the program responsible for handling the token;
• replacing the accounts that hold the permissions above.

These capabilities may be controlled by a single key, a multi-signature arrangement, onchain governance or the network protocol, and they may also have been permanently revoked. Two tokens with the same name and the same standard can still have entirely different permission structures.

A "decentralized token" also cannot be judged from promotional material alone. Supply control, upgrade permissions, key data sources, the distribution of token holdings and the underlying network each need separate examination, rather than a single label covering every layer.

What holding a token means

Holding a token means first of all that an address, account or other record unit is under someone's control according to the current onchain rules. Whoever holds the corresponding private key or satisfies other authorization conditions can initiate transfers or operations that the rules permit.

It does not necessarily mean the holder owns the issuing organization, intellectual property, an underlying physical object or future revenue. Whether a token carries service rights, a redemption claim, voting standing or other arrangements requires reading the specific terms and how they are actually carried out; it cannot be inferred automatically from an onchain balance.

A token balance shown by a custodial platform may also be only that platform's internal bookkeeping. Whether the user holds the corresponding onchain address, how the platform pools assets, and whether withdrawal is possible under given conditions all need to be understood separately from the onchain record in a self-custody wallet.

Common risks and misconceptions

• Impersonating tokens: anyone may create a token with a similar name and symbol, so a name cannot substitute for a contract or mint identifier.
• Permission risk: minting, freezing, pausing or upgrade permissions can change supply and transferability.
• Program risk: a token contract, a shared program or an application interacting with it may contain defects.
• Offchain dependencies: reserves, redemption, custody and real-world asset registers may not match the onchain record.
• Underlying network risk: congestion, reorganization, downtime or protocol changes affect token transactions and confirmation.
• Cross-chain representations: bridged or wrapped tokens usually depend on locking, minting or custody mechanisms, which is not the same as the original chain's asset having moved to another chain.

A successful transaction only shows that the network updated its records according to the rules in force at the time. It does not prove that a token is genuine, that an asset is backed, that a program has no administrative permissions, or that a holder will be able to use or redeem it as expected.

FAQ

Are all tokens issued by smart contracts?

No. Some tokens are managed by their own smart contract, some by a token program shared across the blockchain, and some belong directly to the underlying protocol. The structure depends on the network.

Can a token's name and ticker identify an asset uniquely?

No. Different tokens can use the same name and ticker. Identification also requires checking the blockchain network, the contract address, the mint address or another unique identifier the protocol specifies.

Does adopting the same token standard mean identical functionality?

Not necessarily. A standard usually specifies only basic interfaces; a specific token can still add different permissions and transfer logic, and may contain implementation defects.

Does destroying tokens necessarily increase the value of the rest?

That cannot be inferred. Destruction may reduce one measure of supply, but price is also affected by demand, liquidity, permissions, market conditions and other factors.

Does a token appearing in a wallet mean it has value?

No. A wallet can display any onchain record that matches its recognition rules; a displayed name, amount or icon cannot prove market demand, redeemability or offchain backing.

Related concepts

Continue with smart contract, blockchain, crypto wallet and blockchain address, or return to the Crypto Glossary.

Sources

• NISTIR 8301: Blockchain Networks: Token Design and Management Overview — protocol-native versus application-layer tokens, fungible and uniquely identified tokens, account operations and offchain dependencies.
• Ethereum.org: token standards — Ethereum token interfaces and their compatibility role between wallets and applications.
• Ethereum application-layer standard: ERC-20 — balance, transfer, approval and event interfaces for fungible tokens.
• Solana Docs: tokens — the shared token program, mints, token accounts and minting and freezing permissions.