Definition
Runes is a fungible token protocol created by Casey Rodarmor, the same developer behind Bitcoin Ordinals, designed to enable the creation and management of fungible tokens directly on the Bitcoin blockchain. Launched on April 20, 2024, coinciding with the Bitcoin halving block (block 840,000), Runes was specifically designed as a more efficient and Bitcoin-native alternative to the BRC-20 token standard, which had been criticized for creating excessive “junk” UTXOs (Unspent Transaction Outputs) that bloated the Bitcoin blockchain. Unlike BRC-20 tokens which use Ordinals inscriptions to store token data, Runes leverages Bitcoin’s OP_RETURN field to store token information in a compact, UTXO-based model that aligns with Bitcoin’s native architecture. Each Rune token is represented by UTXO balances rather than inscription-based accounting, making transfers, splits, and merges of token balances more efficient and less wasteful of block space. The Runes protocol supports custom token names (with an innovative time-release naming system where shorter names become available over time), configurable divisibility, and optional open or closed minting. Upon launch, Runes generated enormous transaction activity, with Rune-related transactions dominating Bitcoin block space for weeks and driving miner fee revenue to record levels. The protocol represents a significant evolution in Bitcoin’s expanding utility beyond simple value transfer, contributing to the broader movement to bring programmable asset functionality to the world’s most secure and decentralized blockchain.
Origin & History
| Date | Event |
| January 2023 | Casey Rodarmor launches Ordinals protocol, enabling inscriptions (including images) on Bitcoin |
| March 2023 | BRC-20 token standard created by “domo,” using Ordinals inscriptions for fungible tokens on Bitcoin |
| May 2023 | BRC-20 tokens explode in popularity but create massive UTXO bloat, drawing criticism from Bitcoin developers |
| September 2023 | Casey Rodarmor announces the Runes protocol concept as a “less-bad” fungible token standard for Bitcoin |
| January 2024 | Runes specification finalized; community anticipation builds ahead of the Bitcoin halving |
| April 20, 2024 | Runes protocol launches at Bitcoin block 840,000 (the halving block); transaction fees spike dramatically |
| April 2024 | First week: Rune transactions consume over 50% of Bitcoin block space; miners earn record fees |
| May 2024 | Hundreds of Rune tokens launched; early “blue chip” Runes like UNCOMMON·GOODS and DOG·GO·TO·THE·MOON gain traction |
| June 2024 | Runes activity normalizes; dedicated marketplaces (Magic Eden, OKX) add full Runes trading support |
| Late 2024 | Runes ecosystem matures with improved tooling, wallet support, and secondary market infrastructure |
“Runes is a simple fungible token protocol for Bitcoin. 99.9% of fungible tokens are memes and scams, but they create demand for block space, which is good for miners. So I figured: if people are going to do this anyway, at least make it not crap.” — Casey Rodarmor, Creator of Runes and Ordinals
How It Works
“` ┌─────────────────────────────────────────────────────────────┐ │ BRC-20 vs RUNES ARCHITECTURE │ │ │ │ BRC-20 (Inscription-Based): │ │ ┌─────────────────────────────────────────────┐ │ │ │ Each token operation = Ordinals inscription │ │ │ │ “deploy” inscription + “mint” inscription │ │ │ │ + “transfer” inscription │ │ │ │ Creates many small, unusable UTXOs (bloat) │ │ │ │ Off-chain indexer needed to track balances │ │ │ └─────────────────────────────────────────────┘ │ │ │ │ RUNES (UTXO-Based): │ │ ┌─────────────────────────────────────────────┐ │ │ │ Token data stored in OP_RETURN (prunable) │ │ │ │ Balances live ON UTXOs natively │ │ │ │ Transfer = standard Bitcoin transaction │ │ │ │ No junk UTXOs created │ │ │ │ Compatible with Bitcoin’s UTXO model │ │ │ └─────────────────────────────────────────────┘ │ └─────────────────────────────────────────────────────────────┘
RUNE TRANSACTION STRUCTURE: ═══════════════════════════
┌─────────────────────────────────────────────────────────────┐ │ Bitcoin Transaction │ │ │ │ INPUTS: OUTPUTS: │ │ ┌──────────────────┐ ┌──────────────────────┐ │ │ │ UTXO: 0.01 BTC │ │ Output 0: 0.005 BTC │ │ │ │ + 1000 RUNE_A │ ───► │ + 600 RUNE_A │ │ │ └──────────────────┘ │ (to recipient) │ │ │ ├──────────────────────┤ │ │ │ Output 1: 0.004 BTC │ │ │ │ + 400 RUNE_A │ │ │ │ (change back) │ │ │ ├──────────────────────┤ │ │ │ OP_RETURN: │ │ │ │ Rune protocol data │ │ │ │ (edicts: transfer │ │ │ │ instructions) │ │ │ └──────────────────────┘ │ └─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐ │ RUNE NAMING SYSTEM │ │ │ │ Block 840,000 (launch): Only names 13+ characters allowed │ │ Every ~17,000 blocks: Minimum character count decreases │ │ │ │ Timeline: │ │ 2024 ──── 13-26 char names: UNCOMMONGOODS │ │ 2025 ──── 10-12 char names available │ │ 2026 ──── 8-9 char names available │ │ … │ │ 2028+ ─── 1 char names (single letters/symbols) │ │ │ │ Special: UNCOMMON·GOODS = block 0 rune (etched at launch) │ │ Separators: Middle dots (·) allowed but not required │ └─────────────────────────────────────────────────────────────┘ “`
| Feature | Runes | BRC-20 | ERC-20 (Ethereum) |
| Blockchain | Bitcoin | Bitcoin | Ethereum |
| Data Storage | OP_RETURN field | Ordinals inscriptions | Smart contract state |
| Token Model | UTXO-based | Inscription-based | Account-based |
| UTXO Impact | Minimal (clean) | Creates junk UTXOs (bloat) | N/A (account model) |
| Transaction Efficiency | High (native UTXO) | Low (multiple inscriptions) | High (single contract call) |
| Smart Contracts | No | No | Yes (full programmability) |
| Minting Options | Open mint, closed mint, premine | Open mint only | Fully programmable |
| Naming | Time-release character system | First-come ticker names | Any string |
| DeFi Composability | Limited | Very limited | Extensive |
| Security Model | Bitcoin’s full security | Bitcoin’s full security | Ethereum’s security |
In Simple Terms
- Tokens on Bitcoin, done right — Runes lets people create fungible tokens (like memecoins or community tokens) directly on the Bitcoin blockchain, but in a way that is cleaner and more efficient than the earlier BRC-20 standard that was clogging up Bitcoin.
- UTXO-native design — Bitcoin uses a UTXO model where each “coin” is like a specific bill in your wallet. Runes tokens attach themselves to these UTXOs naturally, so sending Rune tokens works just like sending Bitcoin — no special workarounds or hacks needed.
- OP_RETURN for data — Instead of inscribing data onto satoshis (as BRC-20 does), Runes stores its protocol information in the OP_RETURN field of Bitcoin transactions — a small data area specifically designed for embedding information without bloating the blockchain.
- The naming game — Runes uses a clever system where only long names (13+ characters) were available at launch, with shorter names unlocking over time. This prevents a land-grab for short, valuable names and creates an ongoing discovery process over years.
- Bitcoin block space demand — Whether or not you believe in memecoins, Runes creates real demand for Bitcoin block space, which directly benefits Bitcoin miners through increased transaction fees — especially important after each halving reduces block rewards.
Real-World Examples
| Scenario | Implementation | Outcome |
| Launch day fee spike | Runes launched at the halving block; users rushed to etch (create) and mint the first Rune tokens | Bitcoin transaction fees spiked to over $100 per transaction; miners earned record daily revenue exceeding $80M |
| DOG·GO·TO·THE·MOON | One of the first major Rune tokens, airdropped to Ordinals NFT (Runestone) holders | Became the largest “blue chip” Rune token with significant market cap and trading volume on Magic Eden |
| UNCOMMON·GOODS | The genesis Rune (Rune 0) minted for free in the coinbase transaction of every block after launch | Created an ongoing, fair distribution mechanism that any Bitcoin miner could participate in |
| Magic Eden Runes marketplace | Magic Eden, the leading multi-chain NFT marketplace, launched a dedicated Runes trading interface | Provided institutional-grade trading infrastructure for Rune tokens, legitimizing the ecosystem |
Advantages
| Advantage | Description |
| UTXO Efficiency | Runes aligns with Bitcoin’s native UTXO model, avoiding the junk UTXO bloat that plagued BRC-20 tokens |
| Bitcoin Security | Rune tokens inherit Bitcoin’s unmatched security and decentralization — the most secure settlement layer in existence |
| Miner Revenue | Increased demand for block space generates higher transaction fees for miners, strengthening Bitcoin’s long-term security budget |
| Simple Protocol | Runes is intentionally minimalist — no smart contracts, no complex state — reducing attack surface and keeping the protocol auditable |
| Fair Launch Options | Open minting allows anyone to mint tokens (similar to fair launches), preventing insider allocations and VC-backed pre-sales |
Disadvantages & Risks
| Risk | Description |
| Limited Programmability | Without smart contracts, Runes tokens cannot natively support DeFi functionality like lending, automated swaps, or complex logic |
| Speculative Nature | The vast majority of Rune tokens are memecoins with no utility beyond speculation — most will lose all value over time |
| High Fees During Congestion | During periods of high Runes activity, Bitcoin transaction fees spike significantly, pricing out regular BTC users |
| Ecosystem Immaturity | Runes tooling, wallets, and marketplace infrastructure are still developing compared to Ethereum’s mature ERC-20 ecosystem |
| Bitcoin Community Division | Some Bitcoin maximalists view Runes (and all token standards on Bitcoin) as spam that distracts from Bitcoin’s core mission as sound money |
Risk Management Tips:
- Treat Rune token investments as highly speculative — never invest more than you can afford to lose entirely
- Use established Runes marketplaces (Magic Eden, OKX) with verified collections to avoid counterfeit or scam tokens
- Be aware of Bitcoin network fee conditions before minting or trading Runes; fees can spike 10-100x during peak activity
- Secure Rune holdings in wallets that properly support the Runes protocol (Xverse, Leather) to avoid accidental loss
- Research the specific Rune’s distribution mechanism, total supply, and community before purchasing — most Runes will go to zero
FAQ
Q: What is the difference between Runes and BRC-20?
A: Both enable fungible tokens on Bitcoin, but they use fundamentally different approaches. BRC-20 uses Ordinals inscriptions to store token data, creating many small unusable UTXOs that bloat the blockchain. Runes uses the OP_RETURN field and stores balances natively on UTXOs, making it cleaner and more efficient. Casey Rodarmor created Runes specifically to address BRC-20’s shortcomings.
Q: Are Runes the same as Ordinals?
A: No. Ordinals is a protocol for inscribing data (including images, text, and applications) onto individual satoshis, primarily used for non-fungible content like NFTs. Runes is a separate protocol for fungible tokens. Both were created by Casey Rodarmor, and they coexist on Bitcoin, but they serve different purposes.
Q: Can Rune tokens be used in DeFi?
A: Currently, DeFi functionality for Runes is limited compared to ERC-20 tokens on Ethereum. However, the ecosystem is developing: decentralized exchanges for Runes are emerging (using atomic swaps and PSBTs — Partially Signed Bitcoin Transactions), and cross-chain bridges may eventually bring Runes tokens to DeFi-capable chains.
Q: How do I buy or trade Rune tokens?
A: Rune tokens can be traded on specialized marketplaces like Magic Eden (Bitcoin section), OKX Web3 Wallet, and UniSat. You need a Bitcoin wallet that supports the Runes protocol (such as Xverse, Leather, or UniSat Wallet). Trading occurs through the Bitcoin network, so you will need BTC to cover transaction fees.
Q: Why was the naming system designed with time-released character lengths?
A: The time-release naming system prevents a “land grab” where speculators would immediately claim all short, desirable names at launch. By starting with long names (13+ characters) and gradually allowing shorter ones over several years, the system ensures that short, premium names become available when the protocol is more mature and there is broader community participation in name allocation.
Sources
- Casey Rodarmor — Runes Protocol Specification (docs.ordinals.com/runes)
- Bitcoin Magazine — “Runes: A New Fungible Token Standard for Bitcoin”
- Messari — “Bitcoin Runes: The Next Evolution of BTC Tokenization” Research Report
- Magic Eden — Runes Marketplace Documentation
- Dune Analytics — Runes Transaction Activity and Fee Dashboards
UPay Tip: If you are exploring Runes, focus on understanding the protocol mechanics before speculating on individual tokens. The vast majority of Rune tokens are memecoins that will not retain value — treat them as high-risk, high-volatility experiments. If you do participate, use a dedicated Bitcoin wallet with Runes support (Xverse or Leather are well-regarded), always check Bitcoin network fee levels before transacting, and never mint or buy Runes with money you cannot afford to lose. The most interesting long-term opportunity in Runes may be the infrastructure and tooling being built around it, rather than the tokens themselves.
Disclaimer: This content is for educational purposes only and does not constitute financial advice. Always conduct your own research (DYOR) and consult qualified financial advisors before making investment decisions.
UPay — Making Crypto Encyclopedic
