Tokens and Token Standards

An airdrop is a distribution of cryptocurrency tokens to selected addresses, often intended to introduce a project, reward earlier participation, or distribute governance rights. Eligibility may depend on a recorded snapshot of balances, past application activity, or a claim process defined by the distributor. Some airdrops arrive automatically; others require the recipient to submit a transaction and pay network fees. Receiving tokens does not establish their usefulness, market value, or legitimacy. Anyone may create assets with misleading names, and unsolicited tokens can advertise malicious claim websites. A genuine distribution does not require disclosure of a wallet's private keys or recovery phrase. Claim transactions and token approvals also deserve scrutiny because they may grant spending permissions. When evaluating an airdrop, separate the mechanics of distribution from the project's economic design, transfer restrictions, vesting schedule, and the security of the contract handling the claim.

Sources: ethereum.org · blog.uniswap.org

A BRC-20 token is a fungible token represented through an application-level convention associated with Bitcoin inscriptions. In the original BRC-20 experiment, small JSON inscriptions describe operations such as deploying a token, minting units, and preparing transfers. Indexing software interprets these records and calculates balances according to the convention's rules. Bitcoin nodes validate the underlying Bitcoin transactions, but they do not natively enforce a BRC-20 account ledger as a separate consensus asset. The name resembles Ethereum's ERC-20 standard, yet the original design does not provide the same smart contract execution model. Users must also distinguish token units from the satoshis and transaction outputs carrying associated inscriptions. Transfers can involve several steps, fees, and indexer-dependent interpretation. A token's existence on Bitcoin does not guarantee liquidity, useful rights, safe trading, or agreement among every application displaying its balance.

Sources: domo-2.gitbook.io

ERC-20 is an Ethereum token interface standard for fungible assets, meaning units within a particular token are treated as interchangeable. It specifies common functions and events for balances, transfers, total supply, and allowances that let another address spend an approved amount. This shared interface helps wallets, exchanges, and applications interact with many different tokens using similar software. It does not require a particular business model, fixed supply, market price, or governance arrangement. Some familiar metadata fields, including a token's name, symbol, and decimal precision, are optional in the original specification. Decimals affect display conventions rather than creating fractional arithmetic inside the token's integer balances. Implementations can add minting privileges, transfer restrictions, or other behavior, so interface compatibility is not a security certificate. Users should verify the contract address and understand approvals rather than relying only on a familiar ticker symbol.

Sources: eips.ethereum.org

ERC-721 is an Ethereum standard for non-fungible tokens that distinguishes individual assets through unique identifiers within a contract. Its interface provides methods for checking ownership, transferring tokens, and approving other addresses to manage specified tokens or an owner's collection. The combination of contract address and token identifier identifies a particular token more precisely than its image or collection name. Optional extensions can provide metadata or enumeration features, but the core standard does not require all associated media to be stored on-chain. A token may therefore refer to information hosted elsewhere, with separate availability and modification risks. Ownership of an ERC-721 token also does not automatically grant copyright, commercial use rights, or ownership of a physical object. Those claims depend on additional arrangements. The standard primarily defines interoperable ownership and transfer behavior, not the broader value or enforceability of the represented asset.

Sources: eips.ethereum.org

Fungibility is the property that units of an asset can be treated as equivalent and interchangeable for a particular purpose. For a fungible token, one unit normally carries the same protocol-level rights as another unit of the same token. This does not mean that tokens issued by different contracts are interchangeable merely because they share a name or ticker. Fungibility is also separate from divisibility: an asset can be split into smaller units without every identifiable item being equivalent. Non-fungible tokens instead distinguish individual identifiers and their ownership. In public cryptocurrency systems, transaction histories remain observable, so service providers may treat otherwise equivalent units differently based on their own policies or analysis. The concept therefore has both a technical dimension, concerning how balances are represented, and a practical dimension, concerning how people and applications actually accept the asset.

Sources: eips.ethereum.org · eips.ethereum.org

A governance token is a digital asset used in a protocol's decision-making arrangements. Depending on the implementation, holders may submit proposals, delegate voting power, approve parameter changes, or influence how a treasury is used. Some votes directly trigger on-chain execution, while others signal preferences that an operator or separate process must implement. The token's actual powers are defined by contracts and governance procedures, not by the label alone. Voting thresholds, delegation, quorum, timelocks, administrator privileges, and the distribution of holdings can substantially affect practical control. Owning a governance token does not automatically grant company equity, revenue rights, or authority over every part of an application. A protocol may also have emergency powers outside ordinary voting. Understanding who can propose, approve, execute, or block a change is therefore more useful than assuming that token ownership provides equal or comprehensive participation.

Sources: developers.uniswap.org

An inscription is content recorded using the Bitcoin inscription convention associated with Ordinals. It can contain text, an image, or other data, commonly placed in a Taproot transaction's witness through a script structure that carries the content without executing it as ordinary instructions. Ordinals-aware software associates the inscription with a satoshi and tracks its movement according to its indexing rules. Bitcoin nodes validate the underlying transaction and script requirements, but they do not need to interpret the content as a collectible or enforce a marketplace's claimed value. Inscribing data consumes block space and requires transaction fees. The content's presence on-chain also does not establish copyright ownership, authenticity of an artist, or rights to an external asset. Careful wallet handling matters because ordinary spending can move the output associated with an inscription even when the user intended to preserve it.

Sources: docs.ordinals.com

A non-fungible token is a token whose individual identifier distinguishes it from other tokens in the same system. Rather than representing interchangeable units of one balance, an NFT records ownership of a particular token instance. Applications use this structure for collectibles, game items, membership credentials, and references to other assets. The token and the associated content are separate concepts: many NFTs point to metadata or media stored outside the blockchain, and several tokens can refer to similar or identical images. Technical ownership therefore does not automatically establish authenticity, copyright, commercial permission, or ownership of a physical object. Those claims require additional evidence and arrangements. NFT standards define transfer and approval behavior, but implementations may add administrator controls or changing metadata. Evaluating an NFT involves checking its network, contract, identifier, storage method, transfer permissions, and the precise rights the issuer claims it represents.

Sources: ethereum.org · eips.ethereum.org

Ordinals is a convention for assigning numbers to individual satoshis and tracking them as Bitcoin transactions move value between outputs. Its numbering follows the order in which satoshis are mined, while transfer interpretation uses defined ordering rules. This creates a way for Ordinals-aware software to discuss particular satoshis rather than only aggregate bitcoin amounts. Inscriptions can associate content with these tracked units, but numbering and inscription content are distinct parts of the ecosystem. Ordinal identifiers are not a new native coin, and Bitcoin consensus does not assign different monetary denominations to satoshis based on their ordinal number. Marketplaces may attribute collectible significance to certain histories or categories, but that significance is separate from Bitcoin's base accounting rules. Using suitable wallet software matters because an ordinary transaction can move a tracked satoshi according to the convention even when the user was thinking only about its BTC value.

Sources: docs.ordinals.com

Runes is a Bitcoin-based fungible token protocol that uses an output-oriented accounting model. Its messages, called runestones, are encoded in designated OP_RETURN outputs and interpreted to define operations such as creating a rune, minting units under specified terms, and allocating balances to transaction outputs. Rune creation is commonly called etching. Unlike the original BRC-20 approach, Runes does not represent its basic operations as JSON inscriptions. Bitcoin full nodes validate the underlying transactions, while protocol-aware software interprets rune balances and transfer rules. The reference implementation is important because precise parsing behavior can affect outcomes, including the treatment of malformed messages. Rune units are separate from the satoshis in the outputs that carry associated balances and still require bitcoin for transaction fees. A valid token record does not establish demand, redeemability, or issuer credibility, and careless transaction construction can unintentionally move or destroy token balances.

Sources: docs.ordinals.com

A stablecoin is a cryptocurrency token designed to track a reference value, often one unit of a national currency. Designs differ substantially: some depend on reserves managed by an issuer, others use crypto collateral and liquidation rules, and others rely more heavily on algorithmic incentives. A target price is not a guarantee that the token will always trade at that price or be redeemable on demand. Reserve quality, redemption eligibility, custody, contract controls, market liquidity, and the performance of the stabilization mechanism all matter. Issuers or administrators may also have powers to freeze addresses or modify operations, depending on the implementation. Stablecoins can serve as trading units or payment instruments within blockchain applications, but they are not automatically equivalent to cash in a bank account. Their apparent price stability should be evaluated separately from operational, counterparty, collateral, and network risks.

Sources: ethereum.org

A token is a digitally represented unit of value, access, ownership, or another defined interest tracked under a protocol's rules. In common cryptocurrency usage, tokens are often distinguished from coins native to a blockchain: BTC is native to Bitcoin, while an ERC-20 asset is tracked by a contract on its host network. However, terminology varies, and not every token system uses a general-purpose smart contract. Bitcoin-based conventions can rely on separate indexing rules that interpret underlying transactions. A token's name or ticker does not uniquely identify it; the network, contract or protocol identifier, and issuance rules are more precise. Tokens can be fungible or non-fungible and can represent very different rights. Creating a token does not by itself create reserves, enforce off-chain promises, establish market demand, or guarantee that the issuer cannot change important controls. Those properties require separate examination.

Sources: ethereum.org · docs.ordinals.com

A token burn is a process intended to remove token units from usable supply. In a smart contract system, a dedicated burn operation may decrease a holder's balance and the contract's recorded total supply. Another approach sends assets to a demonstrably unspendable destination, although this may not change the supply figure reported by the token contract. These mechanisms should be distinguished from temporarily locking tokens or moving them into an issuer-controlled treasury. A burn can be part of redemption, fee processing, migration, or an economic policy, but reducing units does not guarantee higher market value. The effect depends on demand, remaining supply, future minting powers, and the credibility of the removal mechanism. Users should also distinguish intended burns from accidental loss of keys, which can make assets inaccessible without producing a verifiable supply-reduction event. The exact contract or protocol determines what a burn actually changes.

Sources: docs.openzeppelin.com · github.com

Tokenization is the process of representing an asset, entitlement, or defined relationship through a digital token. A system might tokenize a membership, an in-game item, a claim to stored goods, or an interest associated with a financial arrangement. Blockchain records can help track issuance and transfers, but the connection between the token and anything outside the chain requires additional mechanisms. A token referring to a physical asset cannot independently prove that the asset exists, remains available, or will be delivered. Custody, verification, redemption procedures, and applicable agreements therefore remain important. Tokenization also does not automatically divide an asset into economically useful fractions or make it liquid. The design must specify what each unit represents and whether transfers carry the intended rights. The central distinction is between ownership of the token record and the separate rights, obligations, or assets that the record is intended to represent.

Sources: ethereum.org · ethereum.org

Tokenomics is an informal term for the economic design of a cryptocurrency token. It includes how units are created, who receives them, when allocated tokens become transferable, what the token is used for, and whether supply can expand or contract. Relevant features can include maximum supply, ongoing issuance, vesting schedules, treasury holdings, fees, burns, governance rights, and reward programs. The term describes a framework for analysis rather than a guarantee that a project has a sustainable economy. A low circulating supply can look very different from the eventual supply after scheduled unlocks, while a burn mechanism can coexist with significant new minting. Token utility also needs to be distinguished from speculative demand or promises of future functionality. Understanding tokenomics means tracing actual incentives and control rights, including who can change them, rather than relying solely on a distribution chart or a headline yield figure.

Sources: docs.openzeppelin.com · blog.uniswap.org

Wrapped bitcoin is a general description for tokens on another network that are intended to represent BTC held or controlled through a separate arrangement. WBTC is one named implementation, while other systems use different custody, signing, and redemption mechanisms. The representation allows Bitcoin-linked value to interact with applications that cannot directly spend native Bitcoin outputs. However, possessing a wrapped token is not the same as controlling the underlying BTC with a Bitcoin private key. The connection depends on the issuer, bridge, operators, reserves, contracts, and rules for minting and redemption. A target one-to-one relationship does not guarantee unrestricted redemption or identical market prices at all times. Users should distinguish the official token on a specified network from additional bridged copies and look-alike contracts. The important questions are who controls the backing, how its existence is demonstrated, and what process returns native BTC to the holder.

Sources: wbtc.network · docs.threshold.network