A Layer 1 crypto coins list should pair a base blockchain with an asset that the network’s own documentation identifies as native. The evidence available for this article does not establish specific network-and-asset pairs, so it cannot support named coin examples. It does support a careful classification process: verify the network’s documentation, distinguish native assets from tokenized representations, and record the source and date checked rather than treating a ticker as proof.

What counts as a Layer 1 crypto coin?

“Layer 1” commonly refers to a base blockchain network and its protocol; it is common usage, not a separately standardized technical category. For this article, a Layer 1 crypto coin means an asset that the documentation for a specific base network identifies as native to that network. The network is the system; the asset is a separate thing whose relationship to that system must be established.

A token issued on a network should not automatically be classified as that network’s native asset. Tokenization can create a digital representation of an asset using distributed ledger technology, but that broad description does not determine whether a particular asset is native to a particular chain. The documentation must establish the asset’s role and the network it belongs to. A familiar name or ticker is not enough on its own.

This distinction is about classification, not a conclusion about value or quality. It also does not say how an asset is used in every wallet or application. A list that mixes native assets with tokens, wrapped versions, or bridged representations without labeling them can obscure materially different relationships to the underlying network.

A transaction’s presence in a blockchain record does not, by itself, resolve that classification. At a high level, a transaction becomes part of a shared ledger after cryptographic authorization, validation under network rules, grouping into a block, and a consensus decision. Those are transaction-lifecycle steps; they do not establish that every asset referenced in a transaction is native to the network.

Layer 1 crypto coins list: examples by network

A responsible list should include a network-and-asset pair only when primary network or protocol documentation supports the native-asset relationship. The evidence authorized for this article does not provide that support for any named pair. Accordingly, the table below does not invent examples or imply that the absence of an entry means an asset or network does not exist.

NetworkAsset identified as nativeClassification status
No named pair supported by the authorized evidenceNot establishedNo specific network-and-asset relationship can be verified from the evidence available here.

This table is intentionally limited. It is not an exhaustive catalogue, a survey of all Layer 1 networks, or a claim about which assets are currently available. A publishable list of named examples needs a primary source for each entry: documentation that identifies the network and explicitly supports the asset’s native role. The source should be recorded with the entry so readers can check the classification themselves.

A dated list should also state when its classifications were checked. The authorized evidence here does not establish a date on which any named network-asset pair was verified, so no such date or named example is presented. Where documentation uses a different name, symbol, or description than a list might expect, the entry should preserve the source’s terminology and explain any qualification rather than silently standardizing it.

The list’s job is to answer a narrow identification question. It does not rank networks or assets, and inclusion would not establish investment merit, technical performance, or comparative security. Those claims require separate evidence and are outside this reference list’s scope.

How to verify whether an asset is native

Begin with the network’s official protocol or developer documentation. Find a direct statement about the asset’s role and confirm that the statement refers to the same network named in the proposed list entry. A project name, wallet display, or third-party directory label may help locate a candidate, but it is not a substitute for documentation that establishes the relationship.

Then check whether the asset is described as native or instead as a token or representation on the network. Keep those categories distinct. A digital representation made using distributed ledger technology is not automatically the network’s native asset; the relevant question is what the network’s documentation says about that specific asset. If the documentation does not settle the point, label the status unverified rather than inferring it from the asset’s symbol or appearance in an interface.

For explorer checks, be precise about what is being looked up. A draft URI proposal describes common explorer references for transactions by hash, blocks by hash or height, and addresses. These lookup objects can help locate records, but finding a transaction, block, or address is not itself evidence that an asset is native. Return to network documentation for that classification.

Treat “wrapped” and “bridged” as qualifications that need their own documentation. Bridged assets are not physically moved from one ledger to another. Depending on the bridge design, mechanisms such as locking, releasing, minting, burning, or swapping may coordinate value across chains; the exact accounting and redemption path depends on that design. Therefore, an asset represented on a destination chain should not be listed as native to that chain merely because it appears there. Check the bridge and network documentation, and describe the representation accurately.

A practical entry record can include the exact network name, the asset name and symbol as documented, the official source, the date checked, and any qualification such as wrapped or bridged status. If a source supports only part of the entry—for example, it names a network but does not establish the asset’s native role—do not combine that partial evidence into a stronger claim. Leave the pair out or mark it unresolved until the missing documentation is available.

What the list does not tell you

A native-asset label is a category, not an assessment of investment merit, reliability, or future value. A list of network-and-asset pairs also does not compare throughput, fees, decentralization, security, or scalability. Those topics need distinct criteria and evidence; they cannot be inferred from the fact that an asset is native.

Nor does inclusion establish availability through a particular wallet, application, provider, merchant, or exchange. The authorized evidence does not support conclusions about those services, and the list should not suggest otherwise. Likewise, classification as a native asset does not establish legal, tax, or compliance status. No such conclusion should be inferred from this reference list.

Network and asset descriptions may change, so readers using a list should revisit the official documentation rather than relying only on a copied name or symbol. Confirm that the source still identifies the same network and asset, preserve any stated qualification, and note the date of the check. Where the evidence cannot verify the relationship, leaving the entry blank is more accurate than presenting an unsupported coin list as complete.

Sources and references