Runes Protocol

What are Bitcoin Runes?

All you need to know about Bitcoin Runes | The Ultimate Bitcoin Ecosystem Map

The Ultimate Bitcoin Ecosystem Map/All you need to know about Bitcoin RunesAll you need to know about Bitcoin RunesDecoding Bitcoin Runes: Bridging Historical Artifacts with Blockchain InnovationIn t

https://www.diadata.org/bitcoin-ecosystem-map/all-you-need-to-know-about-bitcoin-runes/

Key Features of Runes Protocol

• UTXO-Based Design: The Runes Protocol leverages Bitcoin's Unspent Transaction Output (UTXO) model, which is the fundamental mechanism Bitcoin uses to handle transactions. This design choice allows Runes to create fungible tokens with minimal impact on the blockchain, ensuring that the process is both efficient and scalable.

• Efficient Token Creation: By utilizing the UTXO model, Runes enables a streamlined process for issuing and managing tokens, reducing the complexity and footprint typically associated with token creation on Bitcoin. This makes it easier for users to create various types of fungible tokens, such as loyalty points, community currencies, or fractional ownership of assets.

• Compatibility with Bitcoin’s Security: Since Runes operates within Bitcoin’s existing infrastructure, it benefits from the network’s robust security measures. This ensures that tokens created using the Runes Protocol are secure and reliable, maintaining Bitcoin's high standard of trust.

• Alternative to BRC-20: The Runes Protocol is positioned as a more efficient alternative to the BRC-20 token standard, which was also developed for Bitcoin but is considered more resource-intensive. Runes focuses on simplifying the process and reducing the blockchain footprint, making it a preferable option for certain use cases.

• Development Background: Created by Casey Rodarmor in September 2023, the Runes Protocol reflects Rodarmor's ongoing efforts to expand the functionality of the Bitcoin network. His previous work on the Ordinals Protocol, which allows for the inscription of unique digital artifacts onto individual Satoshis, laid the foundation for further innovations like Runes.

Use Cases

• Loyalty Programs: Tokens representing customer loyalty points that can be easily managed and exchanged.

• Community Currencies: Local or community-based currencies that can be created and circulated.

• Fractional Ownership: Tokens that represent fractional ownership of real-world assets, allowing for easier investment and transfer of ownership.

How does the Runes Protocol work?

UTXO Model

• Unspent Transaction Outputs (UTXOs):
• In Bitcoin, UTXOs represent the digital assets that you have received but not yet spent. Each Bitcoin transaction consumes some UTXOs and generates new ones, which the recipient can spend later.
• The BRC-20 token standard, previously used on Bitcoin, led to the creation of excess UTXOs, often referred to as "junk" UTXOs. These excess UTXOs could congest the network, making it less efficient and hindering the user experience.
• The Runes Protocol addresses this issue by streamlining the use of UTXOs, enabling the creation of fungible tokens without generating unnecessary network congestion.

OP_RETURN Opcode

• Adding Data to Bitcoin Transactions:
• The OP_RETURN opcode allows users to attach extra data (up to 80 bytes) to a Bitcoin transaction. This data is stored in a special output within the transaction.
• In the context of the Runes Protocol, this extra data, called a Runestone, contains essential information about the token being transacted. This includes the token’s name, ID, symbol, commands, and other relevant details.

Token Transfers

• Multiple Tokens Per Transaction:
• Unlike the BRC-20 standard, which allows only one type of token per transaction, the Runes Protocol supports the transfer of multiple types of tokens within a single transaction. This flexibility makes the protocol more efficient and versatile.
• During a token transfer, the protocol processes the instructions embedded in the OP_RETURN data, splitting the original UTXO into several new UTXOs. Each new UTXO represents a different amount of the token, which is sent to the respective recipients specified in the transaction.

Error Handling

• Burning Runes: If a transaction involving Runes fails due to an invalid protocol message (e.g., incorrect data in the OP_RETURN field), the Runes associated with that transaction are burned. This mechanism ensures that no accidental creation of new Runes occurs, maintaining the integrity of the token supply.

The Runes Protocol Landscape