Coin

Overview

A Coin is commonly defined in blockchain operations as the asset built into a base network. Bitcoin has BTC, Solana has SOL, TRON has TRX, and DigiByte has DGB. The protocol itself defines how the coin is issued, transferred, accounted for, and used to pay resource costs.

Native coins can use different ledger models. Bitcoin, Bitcoin Cash, Litecoin, and DigiByte record spendable value through UTXOs, while Solana and TRON manage native balances through accounts. The shared label does not make transaction construction, fee calculation, or finality behavior interchangeable.

A coin differs operationally from a token issued by a smart contract or token program. A native transfer follows base-protocol rules, while a Token Transfer calls contract or program logic. Users can need the native coin for fees even when the asset they intend to send is a stablecoin or another token.

Coin issuance can come from proof-of-work block rewards, proof-of-stake rewards, genesis allocations, protocol inflation, burns, or a combination of rules. Supply should be evaluated through the active Blockchain Protocol and current Circulating Supply methodology rather than one broad assumption about scarcity.

For payments, the asset record should include symbol, network, smallest denomination, address format, fee asset, confirmation model, and provider support. Symbols can collide and wrapped or bridged forms can resemble the native coin. The exact chain and asset identity matter more than whether an interface labels the asset a coin.

Wrapped versions need special care. A token representing a coin on another network is not the native coin itself, even if it tracks the same market price. The wrapper adds contract, custody, bridge, redemption, and liquidity dependencies that should be shown separately in payment and treasury records.