Runes

Runes is a protocol for issuing fungible tokens on Bitcoin, designed by Ordinals creator Casey Rodarmor and launched at the April 2024 halving (block 840,000). Unlike BRC-20, which inscribes JSON documents onto individual satoshis, Runes works natively with Bitcoin's unspent-transaction-output model and encodes all of its token data in an OP_RETURN output. Rodarmor's stated goal was a deliberately simple protocol with a minimal on-chain footprint and more responsible UTXO management, reducing the "junk" UTXOs that earlier token schemes tended to scatter across the chain.

How balances are tracked

A Rune balance is attached to a UTXO rather than to an address or an account. When a UTXO carrying tokens is spent, a data message in an OP_RETURN output — called a runestone — specifies how the tokens are allocated among the transaction's outputs. Creating a new token is called etching, and it fixes the rune's name, divisibility, symbol, and mint terms; an open mint lets anyone create supply within the etched limits by publishing mint transactions. The protocol includes an unusual fail-safe: a malformed runestone is a cenotaph, and tokens processed through one are burned rather than left in an ambiguous state — an intentionally harsh rule that keeps indexers in agreement. Like BRC-20, Runes accounting lives in off-chain indexer software, not in Bitcoin consensus: the chain stores the messages, and indexers replay them under the protocol's rules to compute who holds what.

Holding runes safely is mostly a wallet-hygiene problem. Because balances ride on specific UTXOs, a wallet that does not understand the protocol can destroy value through ordinary behavior — spending a token-bearing output as plain bitcoin, or sweeping it into a consolidation, allocates the tokens to whatever the runestone rules say happens by default. Rune-aware wallets solve this with strict coin control, fencing token UTXOs away from fee selection. The same caution applies to trusting balances: check more than one indexer before treating a large balance as real, since your tokens are, in the end, an interpretation of chain data rather than a chain-enforced fact.

Why the design is leaner

Because OP_RETURN outputs are provably unspendable, they do not enter the UTXO set that every full node must keep readily accessible — the data rides in the transaction without leaving a permanent entry behind. A transfer moves tokens and settles balances in a single ordinary transaction, instead of the multi-step inscribe-then-transfer choreography BRC-20 requires. The protocol needs no consensus change, no sidechain, and no new opcode; it leans entirely on mechanisms Bitcoin has supported for years.

What it means for miners

Token activity on the base chain remains contested ground. Proponents value Bitcoin's permissionless settlement for any use the fee market will bear; critics worry about block-space competition with monetary transactions. D-Central does not advocate for or against issuing tokens, but the operational fact is worth internalizing: minting events, like inscription waves before them, can raise fees sharply and reshape the mempool with bursts of small, high-fee-rate transactions. The launch at the 2024 halving produced exactly that — a short-lived surge in fee revenue arriving in the same blocks that cut the subsidy in half. For anyone mining, fee-market volatility driven by metaprotocol fashion is now part of revenue reality, however one feels about its source.

Where Runes sits

Runes belongs to the same family of base-layer metaprotocols as Ordinals and Inscriptions — conventions layered on top of Bitcoin data that consenting indexers agree to interpret, invisible to nodes that ignore them. That is both its elegance and its caveat: your tokens are as real as the indexers' consensus about them. For the canonical rules, consult the protocol's own documentation rather than any secondary description, this one included.