Crypto Gloss

Bitcoin Runes

Bitcoin Runes is a protocol for creating and transferring fungible tokens through ordinary Bitcoin transactions. It records token rules in OP_RETURN “runestones” and tracks balances across Bitcoin UTXOs, so Runes can use Bitcoin’s base-layer block space without adding smart contracts to Bitcoin itself.

What Runes are

A Rune is a fungible token: each unit of the same Rune is interchangeable. The Runes protocol was designed by Casey Rodarmor and activated at Bitcoin block 840,000, on April 20, 2024. Runes do not change Bitcoin’s consensus rules or create a separate blockchain. Instead, Runes-aware software interprets data in Bitcoin transactions and applies the protocol’s rules to calculate balances.

This distinction matters: Bitcoin nodes validate the underlying Bitcoin transactions, while wallets and indexers that implement Runes interpret the token activity. A token’s existence in the Runes system does not by itself establish that it is useful, safe, or valuable.

How a Runestone works

A transaction can include one Runestone, a protocol message carried in an unspendable OP_RETURN output. It can describe an etching (creating a Rune), a mint (creating units under an existing Rune’s mint terms), or transfers called edicts. Rune balances are associated with UTXOs, and a UTXO can carry balances of more than one Rune.

  • Etching: creates a new Rune and fixes its properties, such as divisibility, symbol, premine, and any open-mint terms.
  • Minting: creates units only when the Rune’s stated mint conditions permit it. An open mint may have an amount per mint, a cap, and block-height limits.
  • Transfers: edicts identify a Rune, an amount, and transaction output(s). Any unallocated balance goes to the first non-OP_RETURN output or a specified pointer.

Because protocol messages are transaction data, Runes transactions compete with payments and other uses for Bitcoin block space. When demand rises, the fee needed for timely confirmation can rise too. Runes do not provide a separate, cheaper fee market.

Names, minting, and token supply

Rune names use letters A–Z; a bullet-like spacer can improve readability, but spacers do not make an otherwise identical name unique. Names are etched once under the protocol’s rules. At launch, names of thirteen letters and longer were available, with shorter names unlocking over time. The name or symbol is not proof of a project’s identity or legitimacy.

An etcher can set a premine and may allow later public minting under fixed terms. Those settings describe how units can be created; they do not promise that anyone will buy them or that a market will exist. A malformed Runestone can also cause balances to be burned under the protocol rules, so compatible wallet software and careful transaction review matter.

Runes compared with BRC-20 and Ordinals

Ordinals inscriptions attach arbitrary data to individual satoshis using Bitcoin transaction witness data. BRC-20 is an experimental token convention built using Ordinals inscriptions; software indexers read the inscriptions and calculate token state. Runes instead encode token operations in Runestones and associate fungible balances with UTXOs. These are different protocols with different transaction formats, and support for one does not guarantee support for another.

Runes are simpler in some respects, but they are not general-purpose smart contracts. They define a limited set of token-creation and transfer operations; apps and marketplaces still need compatible indexing and wallet support. Both Runes and BRC-20 activity use Bitcoin block space and can contribute to congestion when demand is high.

Risks and practical checks

  • Protocol and wallet compatibility: check that the wallet and service support the exact Runes asset and transfer flow. A Bitcoin address alone does not show which token standards a service supports.
  • Token identity: verify the Rune ID and project information with a trusted explorer. Similar names and symbols can mislead buyers.
  • Supply and mint terms: inspect whether a Rune is preminted, still mintable, or subject to a cap. A displayed maximum or ticker is not a guarantee of scarcity or value.
  • Fees and transaction handling: review the Bitcoin fee and all outputs before signing. Mistakes in token-aware transactions may be irreversible.
  • Market risk: many tokens are speculative, thinly traded, or inactive. The protocol provides transfer rules; it does not vet issuers or guarantee liquidity.

History

  • September 2023: Casey Rodarmor published the Runes design proposal, describing a fungible-token protocol that uses Bitcoin’s UTXO model.
  • April 20, 2024: Runes activated at Bitcoin block 840,000, coinciding with the fourth Bitcoin halving. Early interest brought token activity into the same block space used by Bitcoin payments.
  • After launch: wallets, explorers, and marketplaces added varying levels of support. The protocol’s existence should not be read as evidence that Runes tokens have broad adoption or durable demand.

Common misconceptions

“Runes are part of Bitcoin’s native consensus assets.” Runes use Bitcoin transactions, but Rune balances are interpreted by Runes-compatible software; Bitcoin’s base protocol does not create a native fungible-token standard.

“Runes eliminate transaction fees.” Runes transactions still use Bitcoin block space and pay Bitcoin transaction fees.

“Every Rune is a legitimate project token.” Anyone meeting the protocol’s rules can etch a Rune. The protocol does not review projects, promises, or token economics.

Social Media Sentiment

An April 2024 discussion in r/btc framed Runes as a possible source of higher Bitcoin fees and questioned the protocol’s practical purpose. Replies showed disagreement about whether token activity was useful demand or avoidable block-space competition. This is one small, time-specific thread, not a measure of current or overall Bitcoin-community opinion.

Last updated: October 19, 2026

Related Terms

See Also

Swap crypto with ChangeNOW

Sources