Ordinals, Inscriptions, and BRC-20
How Casey Rodarmor's 2023 Ordinals protocol brought NFTs and tokens to Bitcoin via inscriptions, what BRC-20 means in practice, and how Runes evolved the model.
The basics
What Ordinals Did to Bitcoin
In January 2023, Casey Rodarmor released the Ordinals protocol — a system for numbering individual satoshis (the 100,000,000th of a Bitcoin) and 'inscribing' arbitrary data (images, text, JSON) onto them. Each inscribed satoshi becomes a unique digital artifact that can be traded like an NFT. The protocol uses Bitcoin's witness data (added in the SegWit upgrade) plus Taproot script-path spends to embed substantial data economically. Within months, Ordinals had reshaped Bitcoin culture.
How It Differs from Ethereum NFTs
Ethereum NFTs are smart contracts: token IDs that point to off-chain metadata (typically on IPFS). Ordinals are different: the actual content (image, text, even small video) is embedded directly in Bitcoin's blockchain. There's no external metadata reference — the artifact is the Bitcoin transaction itself. This makes Ordinals more cryptographically permanent (Bitcoin's blockchain is the storage layer) but also bloats Bitcoin's blocks substantially during inscription waves.
BRC-20 — Fungible Tokens via Inscriptions
BRC-20, introduced March 2023, is a token standard built on top of Ordinals. Tokens are 'deployed' by inscribing a specific JSON format declaring the ticker and supply. Users 'mint' tokens by inscribing 'mint' instructions; 'transfers' inscribe 'transfer' instructions. The state of who owns what tokens is computed by indexers reading these inscriptions in order. The standard is intentionally simple, almost to a fault — there's no transfer-with-approval, no batch transfers, no on-chain validation.
- Ordinals number individual satoshis and inscribe arbitrary data onto them
- Inscription data is stored directly in Bitcoin blockchain, not off-chain
- BRC-20 uses inscriptions to implement fungible tokens via JSON instructions
- Runes (April 2024) is a more efficient token-on-Bitcoin alternative
Key Takeaways
- Ordinals brought NFT-like artifacts to Bitcoin in early 2023
- Content is embedded directly in Bitcoin blockchain — different from Ethereum's pointer model
- BRC-20 enables fungible tokens via inscriptions; computationally simple but limited
- The protocol has been one of the most culturally significant Bitcoin developments since SegWit
Going deeper
How Ordinals Numbering Works
Ordinals assigns serial numbers to satoshis based on mint order — the first satoshi mined gets number 0, the second gets 1, etc. The protocol is purely a convention; nothing in Bitcoin core enforces it. Indexers track which satoshi has which inscription. Special satoshis (the first satoshi of each block is 'uncommon' and the first of each halving epoch is 'epic', among others) acquire collector value beyond their inscription. The numbering itself is widely accepted because the convention is computationally well-defined.
Inscription Mechanics
Inscribing content requires a two-transaction process. First a 'commit' transaction creates a Taproot output containing the inscription data; second a 'reveal' transaction spends that output and the inscription is officially 'inscribed' on the satoshi. The data lives in the transaction witness, which Bitcoin treats as discounted (4x lower per-byte fee than non-witness data) thanks to SegWit. This is why Ordinals are economically feasible — without SegWit's witness discount, the costs would be prohibitive.
Runes — The Successor
Runes (launched April 2024 at the Bitcoin halving) is a more efficient fungible-token protocol on Bitcoin. Designed by the same Casey Rodarmor, Runes uses OP_RETURN outputs instead of inscriptions, which is more efficient and cleaner. State is similarly computed by indexers but with better economic properties. Runes is generally considered the better fungible-token implementation on Bitcoin.
Block Space Impact
Inscription waves significantly increase Bitcoin block fullness and fee pressure. During major BRC-20 mints, Bitcoin fees have spiked to hundreds of sats/vB (block median fee rates averaged about 435 sats/vB on 8 May 2023, per mempool.space) — making ordinary Bitcoin transfers expensive. This has been controversial: ordinary Bitcoin users complain about fees; Ordinals proponents argue the fees support Bitcoin's security budget as block subsidies decrease. The debate continues.
Key Takeaways
- Ordinals numbers satoshis by mint order; the numbering is convention, not protocol-enforced
- Inscription mechanics use commit + reveal Taproot transactions with witness data
- Runes (April 2024) uses OP_RETURN for cleaner, more efficient fungible tokens
- Inscription waves dramatically affect Bitcoin fee markets — a major source of controversy
Under the hood
Indexer Reliance
Both Ordinals and BRC-20 depend on indexers to determine state. Different indexers can have different views of the same on-chain data because the protocol rules are conventions, not consensus rules. Ordinals indexers (the reference ord implementation and third-party services) generally agree, but edge cases produce divergent views. This is a meaningfully different trust model from Ethereum NFTs — there's no on-chain canonical answer to 'who owns this Ordinal,' just whichever indexer you trust.
Ordinals Marketplaces and Liquidity
Trading Ordinals requires marketplaces that handle the unique transaction patterns. Bitcoin's lack of smart contracts means marketplaces must use Bitcoin-script-level patterns (atomic swaps, partially signed Bitcoin transactions) rather than smart-contract escrow.
Stamps and Other Bitcoin Asset Protocols
Beyond Ordinals/BRC-20/Runes, several other Bitcoin asset protocols exist. Stamps: similar to Ordinals but stores data in transaction outputs rather than witness, so the data is never pruned. STAMPS uses Counterparty (a 2014-era Bitcoin meta-protocol) for asset issuance. Atomicals offers a different inscription mechanism with different trade-offs. The Bitcoin asset protocols landscape is fragmented and evolving rapidly.
Cultural and Strategic Implications
Ordinals represent a major cultural shift in Bitcoin's developer community. Bitcoin core developers were historically focused exclusively on Bitcoin-as-money use cases; Ordinals' explosion forced engagement with NFTs and tokens. Some core developers oppose Ordinals (arguing they're an abuse of block space); others see them as legitimate use of Bitcoin's properties. Bitcoin Core 30.0 (October 2025) raised the default OP_RETURN relay limit (-datacarriersize) from 83 to 100,000, which effectively uncaps it, and now permits multiple OP_RETURN outputs per transaction. The debate ties into broader questions about Bitcoin's long-term security model and what 'legitimate' Bitcoin use cases are.
Bitcoin L2s and Asset Protocols
Several Bitcoin L2s (Stacks, Rootstock, the emerging BitVM-based rollups) offer smart-contract platforms that could subsume some Ordinals use cases with better UX. Whether Bitcoin's asset future runs primarily through Ordinals-like inscriptions, through L2s, or through some combination is one of the central open questions in Bitcoin development. Investors and developers in this space should track both directions.
Key Takeaways
- Indexer-dependent state is structurally different from Ethereum's on-chain canonical state
- Marketplace patterns use atomic swaps and PSBTs rather than smart-contract escrow
- Multiple competing protocols (Ordinals, Stamps, Atomicals) fragment the Bitcoin asset landscape
- Cultural tension within Bitcoin core developers about whether asset protocols are legitimate use
- Bitcoin L2s with smart contracts may subsume some asset use cases with better UX
Related Content
Related Coins
Related Topics
More Topics
Browse all 189 topicsNEAR Contract Model
How NEAR's sharded execution, async cross-contract calls, and storage staking model differ from Ethereum and Solana — and what writing production NEAR contracts looks like.
ICP Canister Model
How Internet Computer (ICP)'s canisters fundamentally differ from Ethereum-style smart contracts — combining compute, storage, and HTTP-server-like functionality in a single on-chain primitive.
ERC-721A and Compressed NFTs
How gas-optimised NFT standards like ERC-721A made batch mints affordable, and how Solana state compression takes the same idea further by committing compressed NFTs to a Merkle tree instead of storing each one in its own account.
ERC-6551 Token-Bound Accounts
How ERC-6551 lets NFTs own smart contract wallets that can in turn own other assets — enabling 'NFTs that own NFTs,' character-bound inventories, and new composability patterns.
Algorithmic Stablecoin Failures — Deep Catalogue
How Terra UST, Iron Finance, USDR, and various other algorithmic stablecoins failed — the specific mechanisms in each case, and why all unbacked algorithmic stablecoins face the same structural risk.
Delta-Neutral Stablecoins (Ethena sUSDe)
How Ethena's sUSDe captures perpetual funding rates by hedging spot crypto with short perpetuals, what makes it different from algorithmic stablecoins, and the structural risks beneath the surface.
Liquid Staking Tokens and Restaking
How stETH/rETH liquid staking tokens work, why EigenLayer's restaking model created a new economic primitive, and what AVS economics mean for the broader Ethereum ecosystem.
Options Greeks On-Chain
How delta, gamma, vega, and theta translate from traditional options markets to on-chain protocols like Derive (formerly Lyra), Aevo, and Premia — and what's structurally different about decentralised options markets.
References & further reading
- primary
- secondary
- primaryOrdinals Documentation - Runes
Runestones in OP_RETURN outputs; protocol activation.
- primaryBitcoin Core - Release notes 30.0 (OP_RETURN / datacarrier policy)
Default datacarriersize raised to 100,000 and multiple OP_RETURN outputs permitted.
- primaryLayer1 Foundation - BRC-20
BRC-20 documentation and proposals.