Ledger Nano S Plus

On April 20, 2024 — the day of Bitcoin's fourth halving — something else was born alongside the halved block reward: the Runes Protocol. Designed by Casey Rodarmor, the same developer behind Ordinals, Runes was built to replace the inefficient BRC-20 standard. It introduces a UTXO-native approach to fungible tokens on Bitcoin, reducing blockchain bloat and opening a new era of Bitcoin-native tokenomics.

What is Runes Protocol

Runes Protocol is a standard for creating fungible tokens directly on Bitcoin. It was designed by Casey Rodarmor — the same developer behind Ordinals — and officially launched at block #840,000, coinciding with Bitcoin's fourth halving on April 20, 2024.


What sets Runes apart from BRC-20 is its native use of Bitcoin's UTXO (Unspent Transaction Output) model. Instead of inscribing data onto individual satoshis, Runes stores token data in the OP_RETURN output of a Bitcoin transaction — a prunable data field that does not create bloat in the UTXO set.

💡 Runes was designed to work with Bitcoin's architecture rather than against it, eliminating the "junk UTXO" problem created by BRC-20.

Why Runes is Better than BRC-20

BRC-20 had a critical flaw: it created enormous numbers of UTXOs on the Bitcoin blockchain, burdening full nodes that must store all UTXO data indefinitely.


Runes solves this with several improvements:


• OP_RETURN storage — token data lives in a prunable output that doesn't bloat the UTXO set
• UTXO-native — each UTXO can hold Rune balances directly, making transfers more efficient
• Less blockchain bloat — significantly reduces UTXO set growth
• Human-readable names — Rune names use uppercase letters separated by dots, e.g. DOG•GO•TO•THE•MOON

How Runes Protocol Works

Runes operates through three core operations:


1. Etching — the creator defines the Rune's name, total supply, divisibility, and symbol. This metadata is written into an OP_RETURN output in a Bitcoin transaction.


2. Minting — if the Rune is open for public minting, anyone can create new units by broadcasting a Bitcoin transaction with a mint instruction.


3. Transferring — Rune balances are transferred via normal Bitcoin transactions, with OP_RETURN specifying how many Runes move from which inputs to which outputs.


All operations happen on Bitcoin L1 directly — no sidechains or Layer 2 required.

Since launch, thousands of Runes have been etched. The most prominent include:


• UNCOMMON•GOODS — Rune #0, created by Casey Rodarmor himself, claimable for free via coinbase transactions
• DOG•GO•TO•THE•MOON — one of the most popular Runes by community size and trading volume
• BILLION•DOLLAR•CAT — top Rune by market cap
• SATOSHI•NAKAMOTO — a tribute Rune named after Bitcoin's pseudonymous creator


You can explore all Runes on ord.io or luminex.io.

Wallets and Exchanges Supporting Runes

Using Runes requires a Bitcoin wallet with Ordinals and Runes support:


• Xverse Wallet — supports Runes, Ordinals, and BRC-20
• Unisat Wallet — popular browser extension for the Bitcoin ecosystem
• OKX Wallet — multi-chain wallet with Runes support
• Leather Wallet — built by the Hiro team for the Bitcoin ecosystem


For trading, look to Magic Eden (Bitcoin), OKX DEX, and Unisat Exchange.

⚠️ Warning: Never send Bitcoin containing Runes to a regular exchange address — you will permanently lose the Runes locked in that UTXO.

Risks and Considerations

Despite being more efficient than BRC-20, Runes still carries significant risks:


• No smart contracts — Runes lack programmable logic, limiting complex DeFi applications
• High speculation — most Runes have no real utility beyond trading
• Variable fees — Rune transactions require Bitcoin transaction fees, which spike during network congestion
• Experimental ecosystem — the tooling and infrastructure are still maturing
• Rug pull risk — many projects lack transparent teams or roadmaps

Runes vs BRC-20 vs Ordinals

To clarify the relationship between these Bitcoin protocols:


• Ordinals — a numbering system for individual satoshis, used to create Bitcoin NFTs
• BRC-20 — a fungible token standard built on Ordinals using JSON inscriptions, but creates UTXO bloat
• Runes — a new fungible token standard using OP_RETURN instead, UTXO-native, more efficient


All three operate on Bitcoin L1, but Runes was specifically designed to fix BRC-20's architectural shortcomings.

Frequently Asked Questions

How is Runes Protocol different from BRC-20?
BRC-20 uses Ordinals inscriptions on individual satoshis, creating large numbers of junk UTXOs. Runes uses OP_RETURN, which is smaller and prunable, resulting in no UTXO bloat and significantly better efficiency.
Do I need a special wallet to hold Runes?
Yes. You need a Runes-compatible wallet such as Xverse, Unisat, or OKX Wallet. Never send Runes to a regular exchange deposit address, as this will permanently destroy them.
How are Rune token prices determined?
Rune prices are determined by market supply and demand on platforms like Magic Eden and Unisat Exchange. There is no fixed pricing mechanism.
Can Runes be used in DeFi?
Only in limited ways. Since Runes lack smart contract functionality, complex DeFi applications like AMMs or lending protocols are difficult to build directly on Bitcoin L1 using Runes alone.
Who is Casey Rodarmor?
Casey Rodarmor is the software developer who created Ordinals Protocol in 2023 and later developed Runes Protocol to replace BRC-20. He is a key figure in the Bitcoin ecosystem.

Stay Updated on Crypto News

Get daily Bitcoin and Altcoin analysis from blockvoy.com

View All Articles

Conclusion

Bitcoin Runes Protocol represents a meaningful step forward in Bitcoin's evolution beyond a simple value transfer network. By solving the UTXO bloat problem of BRC-20 with a more elegant OP_RETURN-based design, Runes opens a more Bitcoin-native path for fungible tokens. However, the space remains highly speculative and experimental. Anyone exploring Runes should do thorough research and only invest what they can afford to lose.

This article is for educational purposes only and does not constitute financial advice.