Follow a Runes balance across Bitcoin transaction outputs. Distinguish the transactions Bitcoin confirms from the token rules an indexer interprets, including transfers and burns.
Runes is a token protocol interpreted from Bitcoin transactions
Runes represents fungible tokens using Bitcoin transaction data and balances associated with unspent transaction outputs (UTXOs). Bitcoin confirms and orders the underlying transactions. Runes-aware software applies the additional token rules. Ordinary Bitcoin validation alone does not supply a wallet’s complete Runes balance accounting.
The previous statement that transfers require “no third-party indexers” was misleading. Users can run their own compatible indexing software or rely on a service. Either way, the token data must be interpreted. Onchain data availability is different from having no indexing layer.
Etching, minting and edicts
The Ordinal Theory Handbook’s Runes overview describes etching to define a rune, minting under its permitted terms and transferring balances. Runestones carry protocol messages in Bitcoin transaction outputs. An edict specifies how token amounts are allocated to outputs; tokens do not simply follow a chosen bitcoin payment without regard to these rules.
A balance example
Imagine an input UTXO containing 1,000 units of a hypothetical rune. A correctly constructed transfer could allocate 250 units to a recipient output and the remaining 750 to a change output. The recipient must track the right token ID and output. This is an accounting illustration, not raw transaction-building instructions or a claim that a particular token name is available.
Malformed messages can destroy token balances
The Runes specification describes malformed runestones called cenotaphs. Runes in inputs to a cenotaph transaction are burned, and other minting or etching consequences can apply. Software compatibility and transaction construction therefore matter. Treating a token-bearing output as ordinary spendable bitcoin without understanding the wallet’s handling can produce an unintended result.
What “Bitcoin-native” does and does not establish
Using Bitcoin’s UTXO data model does not prove that every wallet, marketplace or indexer is decentralized, reliable or liquid. Independent software must agree on interpretation. Bitcoin transaction fees still apply, and demand for block space varies. Increased activity is not a guaranteed permanent revenue stream for miners.
Runes also does not automatically make a token transferable over the Lightning Network. That would require a specific implementation and compatibility evidence. This revision removes the earlier suggestion of near-term support as an established expectation.
A practical reading checklist
- Separate the confirmed Bitcoin transaction from the interpreted token balance.
- Identify the token ID and exact output, not only a display name or logo.
- Check the wallet and indexer versions and their treatment of token-bearing inputs.
- Understand mint terms, burns, fees and the limits of exchange liquidity.
Runes offers a particular way to encode and track fungible tokens. Its merits should be evaluated through those mechanics rather than blanket claims of perfect efficiency or preserved decentralization in every application.
Revision history and scope
Revised 19 October 2026. Corrected the claim that Runes needs no indexers and distinguished Bitcoin settlement from Runes balance interpretation.
24 October 2026: Moved the earlier correction note below the lesson and added a reader-focused introduction. This is a presentation edit; the earlier factual review date is unchanged.