Crypto Networks: Coins, Tokens and Transfer Basics

Native coin, issued token or wrapped representation?

A native coin belongs to a blockchain's own accounting system: BTC on Bitcoin and Gram (GRAM) on The Open Network are examples. A token is represented by contracts or another token mechanism on a host chain. USDT on TON is therefore a different asset from Gram, despite sharing the network.

Gram was previously called Toncoin (TON); the network is still TON. Naming sources, checked 24 September 2026: TON and Wallet's naming explanation.

A wrapped or bridged representation connects value on one chain to an asset elsewhere. Its operation may depend on a custodian, bridge contracts or other parties. The holder needs to understand those dependencies and any redemption conditions. Changing the network selector does not by itself convert one asset into another.

Stablecoins add another question: what supports the intended price? An issuer's native token and a third party's representation of that token should not inherit the same reserve, redemption or risk description without evidence. A familiar logo is not a substitute for the issuer's current contract directory.

For the underlying distinctions, see Ethereum's bridge documentation and the issuer references in the directory below.

Eight assets, with their network context

These are educational profiles, not a service-acceptance list. Protocols and providers can change; use the linked network or issuer documentation to identify an asset rather than inferring support from its inclusion here.

A network chooser based on compatibility

Start with the asset actually recorded in the wallet, not a preferred fee or a familiar ticker. The chain and asset recognized at the destination must match. A low quoted cost does not make an incompatible route usable.

A wallet shows the same ticker on two networks

Identify the chain and token contract for each entry. A shared ticker does not establish that either entry can be used in place of the other.

Two addresses both begin with 0x

Check the network separately. The prefix does not distinguish Ethereum, BSC or an EVM-compatible layer 2, and says nothing about the asset a service recognizes.

A token is described as wrapped, pegged or bridged

Identify its issuer, custodian or bridge, what backs it, and how redemption works. Compare those dependencies before comparing transaction costs.

The receiving instructions show a memo or comment

Treat it as part of the destination instructions. Copy the required value exactly; an address alone may not identify the intended account.

A network is advertised as the cheapest or fastest

Compare current estimates for the actual operation. Network inclusion, finality, service processing and provider charges are different measurements.

Compatibility has several layers: network, native coin or token contract, address, and any required reference. A mismatch in any one can prevent the intended result even when the wallet accepts the address text.

Addresses identify destinations; memos can identify accounts

An address format helps a wallet detect mistakes, but a valid address is not proof of the intended owner or correct network. Some networks use visibly different formats; others share the same shape. Copying a whole address and checking it against its trusted source is more useful than recognizing only its first few characters.

A service can use one address for multiple customers and distinguish them with a memo, tag or comment. The receiving service's current screen determines whether that additional value is required. If it supplies one, preserve it exactly. If the sender insists on a value that the receiver has not supplied, resolve the discrepancy through the service's verified documentation; arbitrary text is not a safe substitute.

TON also illustrates why encoding matters: two strings may refer to the same account while carrying different bounce flags. The TON guide explains that distinction and why it does not make every address variant interchangeable in every situation.

Compare fees in the unit and context that produced them

Bitcoin fees depend on transaction virtual size and a fee rate. Ethereum gas measures computational work, with the price paid in ETH. TRON distinguishes Bandwidth and Energy, while TON has storage, computation and message-related fee components. These are different accounting models, not one universal per-transfer price.

Record what a quote includes: network cost, a provider's own charge, or a combination. Then check the asset unit and the time of the estimate. Converting a fee into dollars adds a changing market price to the calculation. A token transfer can also cost more than moving the native asset on the same chain because the operations differ.

Timing needs the same discipline. A submitted transaction, inclusion in a block, network finality and a service's account update are separate events. An explorer can show chain activity without proving that a service has recognized an account. Avoid translating an average block interval into a guaranteed arrival time.

Read Bitcoin's fee explanation, Ethereum's gas guide, TRON's resource documentation and TON's fee components for the network-specific models.

Custody and issuer risk are separate from network choice

With self-custody, control of the signing keys carries responsibility for backups, device security and authorization. With a custodial account, a provider controls the keys and applies its own access and processing rules. A polished interface does not tell you which model is in use; read the product's account and recovery documentation.

The asset can add another layer. Keeping a wrapped token in a self-custody wallet does not remove the wrapper's reserve or redemption dependency. Likewise, holding an issuer-backed stablecoin yourself does not remove issuer restrictions or market-price risk. Evaluate the wallet and the asset separately.

A block explorer is useful for inspecting a public transaction. It does not need a recovery phrase or private key. Requests to reveal those secrets, sign unexplained approvals or use an unsolicited recovery link are reasons to stop and verify the request independently.

Detailed network guides