Tools/Explorers

Ordinals vs Runes: Bitcoin Token Standards Compared

Compare Bitcoin Ordinals inscriptions and Runes fungible tokens across technical architecture, fees, UTXO impact, marketplace ecosystem, and adoption.

Spark Team

Ordinals vs Runes Overview

Bitcoin now supports two distinct token standards created by the same developer, Casey Rodarmor. Ordinals inscribe arbitrary data onto individual satoshis to create NFT-like assets directly on the Bitcoin base layer. Runes, launched at block 840,000 on April 20, 2024, provide a UTXO-native protocol for issuing fungible tokens. While both protocols operate on Bitcoin's base layer, they serve fundamentally different purposes and use different technical mechanisms to embed token data into transactions.

The following table summarizes the core differences between the two protocols.

AttributeOrdinalsRunes
CreatorCasey RodarmorCasey Rodarmor
LaunchJanuary 2023April 2024 (block 840,000)
Token typeNon-fungible (unique inscriptions)Fungible (interchangeable units)
Data storageWitness data (Taproot transactions)OP_RETURN outputs
Balance trackingOrdinal theory (satoshi numbering)UTXO-native (balances on UTXOs)
Indexer requiredYes (ord indexer)Yes (Runes-aware indexer)
Max data per inscription~4 MB (block weight limit)Small metadata only
UTXO set impactModerate (tracked satoshis)Minimal (OP_RETURN is prunable)
Wallet requirementTaproot (P2TR) walletAny Bitcoin wallet
Primary use caseDigital art, collectibles, mediaMemecoins, fungible tokens
Cumulative inscriptions/etchings107M+ inscriptions (early 2026)~100,000+ etched Runes

How Ordinals Work

Ordinals combine two concepts: ordinal theory, which assigns a unique serial number to every satoshi based on the order it was mined, and inscriptions, which attach data to those numbered satoshis. The inscription payload is embedded in the witness field of a Taproot (P2TR) transaction, wrapped inside an OP_FALSE OP_IF ... OP_ENDIF envelope that nodes store but never execute.

Because inscriptions use witness data, they benefit from the SegWit discount: witness bytes cost one weight unit each, compared to four weight units for non-witness bytes. This means a 400 KB inscription uses roughly 400,000 weight units rather than the 1,600,000 it would cost as standard transaction data. The theoretical maximum inscription size is approximately 4 MB, limited by the block weight cap of 4,000,000 weight units.

Each inscription is permanently bound to a specific satoshi. Transferring the inscribed satoshi transfers ownership of the inscription. This creates NFT-like behavior without smart contracts: the inscribed data is immutable, on-chain, and tied to a bearer asset. Content types range from images and text to HTML, SVG, and even recursive inscriptions that reference other inscriptions.

How Runes Work

Runes take a different approach. Instead of inscribing data in the witness, Runes encode token operations in OP_RETURN outputs. These outputs are provably unspendable, so nodes can safely prune them from the UTXO set. The protocol messages, called "runestones," specify token deployments (etching), minting, and transfers in a compact binary format.

Token balances are stored directly on standard Bitcoin UTXOs. A single UTXO can carry balances of multiple different Runes simultaneously. When a transaction spends a UTXO holding Runes, the runestone in the transaction's OP_RETURN output specifies how those balances are distributed across the new outputs. Any Runes balances not explicitly assigned are sent to a designated change output or burned.

Runes operations are efficient: a single transaction can deploy, mint, or transfer tokens to multiple recipients. This contrasts with BRC-20, which required two or three separate transactions per operation and left the UTXO set bloated with unspendable outputs. For a detailed comparison, see our Runes vs BRC-20 comparison.

BRC-20: The Predecessor Runes Was Built to Replace

BRC-20, launched in March 2023, was the first widely adopted fungible token standard on Bitcoin. It piggybacks on Ordinals by inscribing JSON metadata into witness data. A deploy inscription defines a token's name, supply, and mint limit. A mint inscription creates tokens. A transfer inscription moves them. The Bitcoin protocol has no awareness of BRC-20 balances: an off-chain indexer must scan every block, parse the JSON inscriptions, and maintain a separate ledger.

This architecture created several problems. Each BRC-20 transfer required at least two on-chain transactions: one to inscribe the transfer intent and another to execute it. Every mint created a new UTXO that held the inscription but was too small to spend economically, effectively adding permanent entries to the UTXO set that every full node must store in memory. During peak BRC-20 activity in 2023, the UTXO set grew by millions of entries, and transaction fees spiked above $30 for simple transfers.

Rodarmor created Runes explicitly to address these issues. By using OP_RETURN for metadata (prunable by nodes) and storing balances on standard UTXOs (spendable and consolidatable), Runes avoids the UTXO bloat problem entirely. The protocol requires no Taproot wallet and supports batch operations in a single transaction.

Block Space and Fee Impact

Both Ordinals and Runes compete for block space, but they consume it differently. Ordinals inscriptions can be large: a single image inscription might consume 200-400 KB of witness data. During peak inscription activity in late 2023, Ordinals-related transactions dominated block space, pushing average transaction fees above $30 and generating nearly $10 million in daily miner fee revenue.

Runes transactions are smaller individually but can be voluminous in aggregate. On the launch day (April 20, 2024), Runes accounted for 57.7% of all Bitcoin transactions and consumed over 90% of network fees within the first hours. This surge drove fees to over $100 per transaction for several hours. Activity normalized quickly: within a week, Runes settled to roughly 30% of daily transactions before declining further.

For miners, both protocols represent significant fee revenue. Ordinals and Runes have collectively contributed over $500 million in miner fees since 2023, making miners strong advocates for keeping these protocols accessible. This dynamic has shaped the governance debate around Bitcoin Core's relay policies.

UTXO Set Impact

The UTXO set is the database of all unspent transaction outputs that every full node must keep in memory. Protocols that inflate the UTXO set increase the hardware requirements for running a node, which can affect decentralization.

ProtocolData locationUTXO set impactNode pruning
OrdinalsWitness field (Taproot)Moderate: inscribed satoshis tracked as UTXOsWitness data prunable after validation
BRC-20Witness field (JSON inscriptions)High: millions of small unspendable UTXOsUTXOs persist permanently in node memory
RunesOP_RETURN outputMinimal: OP_RETURN is provably unspendableNodes discard OP_RETURN data immediately

Runes was designed with UTXO hygiene as a first-class concern. OP_RETURN outputs are excluded from the UTXO set because they can never be spent. Token balances attached to standard UTXOs can be consolidated just like regular bitcoin, preventing the accumulation of dust outputs. Ordinals have a more moderate impact: the inscribed satoshis are standard UTXOs, but their value makes them unlikely to be consolidated or spent. BRC-20 had the worst impact, creating millions of small, economically unspendable UTXOs during its peak activity.

Marketplace and Ecosystem

Both Ordinals and Runes share an overlapping marketplace ecosystem. Magic Eden is the largest venue by volume for both protocols, followed by OKX and Unisat. Unisat covers Ordinals, BRC-20, and Runes from a single interface, while Magic Eden integrated Runes support immediately at protocol activation. For a deeper look at inscription marketplaces, see our Ordinals marketplace comparison.

Ordinals trading volume peaked in late 2023 and early 2024, driven by collections like Bitcoin Puppets, NodeMonkes, and Quantum Cats. By March 2026, monthly Ordinals sales volume was approximately $47 million. The Runes market is dominated by memecoin-style tokens: DOG (the largest Runes token, which peaked at roughly $767 million market cap with over 95,000 holders) leads a category that also includes PUPS, RSIC, and various community tokens.

Runes daily fee revenue has been volatile, ranging from approximately $3,000 to $537,000 per day through 2025, reflecting the speculative nature of the market. This is well below the December 2023 Ordinals fee peak. For guidance on inscribing and managing Ordinals, see our Ordinals inscriptions guide.

The Base Layer Debate

Whether Ordinals and Runes belong on Bitcoin's base layer remains one of the most contested questions in the Bitcoin community. Critics, including Adam Back of Blockstream and developer Jimmy Song, argue that data-heavy inscriptions displace legitimate financial transactions and amount to a denial-of-service attack on the network. Song has criticized the Taproot upgrade itself for creating a "social attack surface" that enabled inscription activity.

Proponents counter that Bitcoin's fee market is permissionless: anyone willing to pay market-rate fees can use block space for any purpose the consensus rules allow. They point to the $500+ million in cumulative miner fees as evidence that these protocols strengthen Bitcoin's security budget as block subsidies decline with each halving.

This debate shaped Bitcoin Core's v30.0 release (October 2025), which removed the longstanding 80-byte default limit on OP_RETURN data. The change was a relay policy adjustment, not a consensus rule change: node operators can still configure their own limits via the -datacarriersize flag. Bitcoin Knots, an alternative node implementation that restricts inscription relay, has grown to approximately 18% of reachable nodes. For more on this topic, see our research on Ordinals and BRC-20 evolution and the Runes protocol deep dive.

When to Use Ordinals vs Runes

Choosing between the two protocols depends on what you are building. Ordinals are the right choice for unique, media-rich digital artifacts: art, collectibles, PFPs, on-chain documents, or any asset where individual identity matters. The inscription is permanently stored on Bitcoin with no external dependencies.

Runes are the right choice for fungible tokens: community currencies, memecoins, loyalty points, or any asset where units are interchangeable. Runes' UTXO-native design makes transfers cheaper and more efficient than BRC-20, and the protocol's batch capabilities reduce the number of on-chain transactions needed.

For projects that need programmable token logic, smart contracts, or off-chain scalability, neither protocol is sufficient on its own. Bitcoin Layer 2 solutions like Spark and the Taproot Assets protocol offer complementary approaches for issuing and transferring tokens with lower fees and higher throughput. The Taproot Assets vs Runes comparison covers these tradeoffs in detail.

Frequently Asked Questions

What is the difference between Bitcoin Ordinals and Runes?

Ordinals create non-fungible tokens by inscribing data onto individual satoshis using witness data in Taproot transactions. Runes create fungible tokens by encoding token metadata in OP_RETURN outputs and storing balances directly on UTXOs. Ordinals are for unique digital artifacts (similar to NFTs), while Runes are for interchangeable tokens (similar to ERC-20 tokens on Ethereum).

Did Runes replace BRC-20 tokens?

Runes was designed as a more efficient alternative to BRC-20, not a direct replacement. BRC-20 tokens still exist and trade on marketplaces, but Runes addressed BRC-20's main problems: UTXO set bloat, multi-transaction transfers, and reliance on off-chain indexers. Many new fungible token projects on Bitcoin have launched using Runes rather than BRC-20 since April 2024.

Do Ordinals and Runes increase Bitcoin transaction fees?

Yes. Both protocols compete for block space alongside regular transactions. During peak activity, they can significantly increase fees. Runes consumed over 90% of network fees within hours of launch. Ordinals-driven fee spikes exceeded $30 per transaction in late 2023. However, these fees also strengthen Bitcoin's security budget by supplementing the declining block subsidy.

Which Bitcoin wallets support Ordinals and Runes?

Ordinals require a Taproot-capable wallet. Dedicated Ordinals wallets include Xverse, Unisat, and Leather. Runes can work with any Bitcoin wallet in principle, but trading and managing Runes typically requires a wallet with Runes indexer integration. Xverse, Unisat, and Magic Eden wallet support both protocols.

Are Ordinals bad for Bitcoin?

Opinions are sharply divided. Critics argue inscriptions waste block space and raise fees for financial transactions. Supporters point to over $500 million in cumulative miner fees as direct evidence that Ordinals strengthen Bitcoin's economic security model. The debate led to policy changes in Bitcoin Core v30.0 (October 2025), which removed the default OP_RETURN size limit, and the growth of Bitcoin Knots to approximately 18% of nodes as an alternative that restricts inscription relay.

DOG is the largest Runes token by market capitalization, peaking at roughly $767 million with over 95,000 holders. Other notable Runes include PUPS and RSIC. The overall Runes market is heavily concentrated, with DOG accounting for approximately 79% of total Runes market capitalization.

How many Ordinals inscriptions exist?

By early 2026, the cumulative count of Ordinals inscriptions had surpassed 107 million. Inscription activity has varied significantly over time, with peaks in late 2023 and mid-2024 followed by more modest but consistent activity through 2025 and 2026.

This tool is for informational purposes only and does not constitute financial advice. Data is approximate and based on publicly available information as of October 2026. Market data for Ordinals and Runes changes rapidly. Always verify current figures before making decisions.

Build with Spark

Integrate bitcoin, Lightning, and stablecoins into your app with a few lines of code.

Read the docs →