What Are the Main Forms of Cryptocurrency?

Cryptocurrency is often used broadly for crypto assets, although terminology varies. A technical definition derived from NIST publications describes cryptocurrency as “a digital asset, credit, or unit that can be cryptographically transferred between users of a blockchain network.” This definition concerns blockchain-network cryptocurrency; it does not cover every legal category called a digital asset.

There is no single, universally standardized functional taxonomy in the supplied evidence. A practical classification can still ask four separate questions: What role does the asset have in its network? What use does its documentation describe? How is its value designed to behave? What functions or claims do the relevant materials specify for holders? These dimensions should not be treated as mutually exclusive categories or universal legal classifications.

What counts as a form of cryptocurrency?

One useful distinction is between a blockchain’s native asset and a token issued on an existing network. The accepted evidence here supports a specific example, rather than a universal definition of either category: Ethereum’s technical overview describes ether as Ethereum’s native cryptocurrency and as part of the protocol’s market for computation. Other cryptocurrencies can use different issuance, utility, accounting, and consensus rules. That is why an example of one network’s native asset should not be generalized into a description of all crypto assets.

Token standards can describe technical interfaces without establishing an asset’s economic or legal meaning. Ethereum’s ERC-20 standard defines a common fungible-token interface that includes total supply, balances, transfers, allowances, approvals, and Transfer and Approval events. The interface does not establish backing, issuance policy, market value, compliance, or implementation safety. It can describe specified interactions, but it does not by itself establish what a token represents or what holders may claim.

These distinctions set useful boundaries for the categories that follow. An asset’s network relationship, a stated use, a value objective, and a holder’s documented functions are different questions. Evidence for one does not automatically answer the others.

Native network and payment-oriented cryptocurrencies

The supplied evidence identifies ether as Ethereum’s native cryptocurrency and places it within the protocol’s market for computation. This supports a bounded example of a network-related role. It does not support a general claim that every native asset pays transaction fees, supports network security, or performs the same protocol operations. Those functions must be verified for the specific system.

“Payment-oriented” can be used as a descriptive label when documentation identifies transferring value as an intended function. But that label alone does not establish how a particular network processes transfers or whether its native asset has any additional network role. Check the relevant protocol materials for the specific function and its scope.

Keep payment use separate from value design. An intended use for transferring value does not mean an asset is designed to maintain a stable value, and it does not establish suitability for a particular transfer or organization. The word “payment” describes a function; it is not a statement about price behavior or a recommendation.

Stablecoins and other value-linked tokens

A stablecoin aims to maintain a stable value relative to a specified asset, currency, or basket through a stated stabilization mechanism. This definition describes an objective, not a guaranteed outcome: market value and redemption value can diverge from the reference.

To classify a particular asset under this description, identify the reference named in its materials and the stabilization mechanism those materials state. Do not infer a specific mechanism, reserve arrangement, collateral structure, or redemption term from the word “stablecoin” alone. The accepted evidence supports the general objective and its limitation, but not an account of particular designs or the arrangements of any named stablecoin.

It is also important to keep “tracks a reference” distinct from “can be redeemed for the reference.” The objective of maintaining a relationship to a reference does not, by itself, establish a redemption arrangement. For asset-specific conclusions, consult documentation that directly addresses the claimed mechanism and any claimed redemption terms. If the documentation available does not establish a detail, treat it as unconfirmed.

Utility and governance tokens

“Utility token” and “governance token” are commonly used as functional labels, but the accepted claims supplied for this article do not establish definitions for either category. A specific token may be described in its own documentation as providing access to a service or as enabling participation in protocol decisions; those descriptions should be attributed to and checked against that documentation rather than assumed from the category name.

Even when a particular function is documented, separate it from broader conclusions about holder rights. A stated ability to participate in a defined process does not by itself establish enforceable rights or control. Likewise, a described service function does not establish any additional use, financial return, or legal entitlement. For a specific token, verify the stated function and its limits in the relevant protocol or token materials; do not treat a label as a complete account of what ownership means.

The categories can describe different aspects of an asset, but this article’s evidence does not establish general rules for how utility and governance functions are implemented or combined. Those details require asset-specific support.

Asset-backed and tokenized claims

“Asset-backed,” “tokenized asset,” and “tokenized claim” should not be treated as interchangeable descriptions without evidence. A reference to an off-chain asset establishes only that the materials name or refer to that asset; it does not, by itself, establish backing, representation, ownership, a legal claim, custody, or a right of redemption. The supplied accepted claims do not provide definitions or asset-specific evidence for these arrangements, so no general conclusion about what a particular token represents or entitles its holder to can be drawn here.

For a specific arrangement, keep separate the on-chain token, the off-chain asset or claim mentioned in the documentation, and the terms that describe their relationship. Issuer, contractual, and custody materials may be relevant to verifying that relationship, but the appropriate evidence depends on the claim being made. Do not infer that an underlying asset is held in a particular way, that a holder has a particular right, or that redemption is available unless suitable documentation establishes that exact point.

A token’s technical interface does not fill this evidence gap. For example, ERC-20 specifies interface features such as balances and transfers, but the standard does not establish backing or market value. Technical interoperability and the nature of any claimed relationship to an off-chain asset are separate matters.

How the forms differ—and why categories overlap

A practical classification workflow is to record what is known in four dimensions, without forcing every asset into one exclusive label:

  1. Network relationship: Identify the specific network and determine whether its technical documentation describes the asset as native to that protocol or as a token using an existing network. The available evidence gives ether on Ethereum as a specific native-asset example; do not infer other networks’ arrangements from it.
  2. Stated use: Record the function described in the relevant protocol or token materials, such as a transfer function or a particular network operation. Distinguish what the documentation states from an assumption about how the function works or what it guarantees.
  3. Value objective: If an asset is described as a stablecoin, identify the specified reference and stated stabilization mechanism. Keep that objective separate from any conclusion about market value, redemption value, reserves, or collateral unless asset-specific evidence supports the conclusion.
  4. Documented functions and claims: Record what the relevant materials say holders can do or claim. For utility, governance, or tokenized-claim descriptions, verify the precise function or relationship and avoid inferring enforceable rights, control, ownership, or redemption from a label alone.

Match each conclusion to evidence capable of supporting it. Protocol documentation can describe a network’s functions; a token standard can specify an interface; and issuer or contractual materials may address a particular token’s stated arrangements. One source type should not be used to answer a different question: an interface does not establish backing, and a reference to an off-chain asset does not establish holder rights.

The result may be a combination of descriptions, or it may remain incomplete where documentation does not establish a category. These labels are best treated as a functional map of network relationship, stated use, value objective, and documented functions—not as a single standardized taxonomy, a substitute for asset-specific verification, or a recommendation about whether to use or hold an asset.

Sources and references