Runes Handbook
  • 1. Introduction
  • 2. Origins
    • Segregated Witness (SegWit) Upgrade
    • Taproot Upgrade
    • Inscriptions
    • Ordinal Theory (Ordinals)
      • Rarity
      • Supply of Rare Satoshis
      • Names
    • BRC-20
    • Why Runes?
  • 3. Runes
    • Bitcoin’s UTXO Model
    • The Runes Protocol
    • OP_Return
    • Motivation for Runes
    • Bitcoin Runes vs BRC-20
    • Launch
      • The First Runes
    • What are Bitcoin Runes For?
      • Memecoins
      • DeFi
  • 4. How Do Bitcoin Runes Work?
    • Etching (Creating a Rune)
      • Name
      • Symbol
      • Divisibility
      • Premine
      • Terms
    • Minting
    • Transfering
    • Runestone
    • Rune Seasons
    • Ecosystem
      • Launchpads
      • Marketplaces
      • Wallets
      • Data / Analysis
      • Explorers
    • Storing Bitcoin Runes
  • 5. Terminology
Powered by GitBook
On this page
  1. 3. Runes

OP_Return

PreviousThe Runes ProtocolNextMotivation for Runes

Last updated 11 months ago

The data representing Runes is stored within the OP_RETURN field of a Bitcoin transaction.

OP_RETURN is an operation code (opcode) from Bitcoin’s scripting language that enables users to embed arbitrary data onto the blockchain. The official limit for data stored in an OP_RETURN field is 80 bytes, providing a dedicated space for storing information related to Runes.

The provides detailed explanations and guidelines on the specific usage and formatting of OP_RETURN outputs for representing Runes data. This documentation serves as a valuable resource for developers and users interested in understanding and implementing the Runes Protocol within the Bitcoin ecosystem.

By utilizing the OP_RETURN field, the Runes Protocol can seamlessly integrate token data into regular Bitcoin transactions, without modifying the core Bitcoin protocol or introducing external dependencies.

This approach aligns with the ethos of Bitcoin's decentralized and open-source nature, allowing for innovative applications and use cases to be built on top of the existing infrastructure.

official Runes documentation
fungible