XRGB
  • XRGB
    • XRGB Introduciton
    • XRGB-404
    • XRGB Token
    • Roadmaps
    • XRGB L2 Chain
    • X404 Protocol
    • How to Use the XRGB Bridge on Lynex
  • XRGB WALLET
    • Overview
    • Social Login
    • XRGB Web Wallet
    • XRGB Mobile Wallet
    • XRGB Extension Wallet
    • Assets Supported
      • BRC20
        • Technical implementation
        • User Tutorial
      • RGB20
        • Overview
        • User Tutorial
    • Address type
  • XRGB STAKING
    • Babylon Staking
    • Lorenzo Staking
    • Other Staking Protocols
  • XRGB USB
    • Tech Implementation
    • USB Design
    • USB Tutorial
    • Musig2 Introduction
  • X404 NFT Hub
    • Get started
    • Mint X404 Tutorial
    • Buy X404 Tutorial
    • Bridge X404 Tutorial
    • Redeem or claim X404 Tutorial
    • Send & Receive X404 Tutorial
  • FAQs
    • XRGB Wallet
      • Quick Question
      • Executing a payment using RGB
      • What are the benefits of MPC wallets with Social Login?
      • MPC Wallet Use Cases
    • RGB
      • Quick Question
      • Client-Side-Validation
      • Introduction of RGB Contract
      • Introduction of Single-Use Seals
      • Client to client communications
      • RGB state transitions
      • RGB state transition commitments
      • RGB Privacy Protection
    • BRC20
      • Quick Question
      • Pros of BRC-20 Tokens
      • Cons of BRC-20 Tokens
  • 📖User Tutorials
    • Get started
      • Usage conditions
      • Create a new account
      • Social Login
      • Import Wallet
    • BRC20 Tutorial
      • View BRC20 tokens and balances
      • View BRC20 token detail
      • Inscribe transfer
      • Send BRC20
      • Receive BRC20
    • RGB20 Tutorial
      • View RGB20 assets and balance (Testnet)
      • Mint RGB20 assets (Testnet)
      • Send and receive RGB20 tokens (Testnet)
    • ERC20 Tutorial
      • View ERC20 assets
      • Send and receive ERC20
    • BTC Token
    • BRC20 - ERC404 Bridge
Powered by GitBook
On this page
  1. FAQs
  2. RGB

RGB state transition commitments

Multiple state transitions involving issuance and transfer of RGB can be incorporated into a single commitment. There are two ways to put the commitment into the Bitcoin transaction:

  • Taproot commitment: an OP_RETURN script containing the LNPBP-4 message is involved in the top right leaf of the TapTree associated with the first Taproot output in the Bitcoin transaction. This information is disclosed exclusively off-chain to the recipient of the RGB transfer. Consequently, the Bitcoin transaction can include just one taproot output, serving dual purposes: sending the Bitcoin change back to the sender and embedding the commitment. This is achieved without any additional byte and without any indication that the Bitcoin transaction contains an RGB commitment.

  • OP_RETURN commitment: the LNPBP-4 message is directly integrated into the first OP_RETURN output of the Bitcoin transaction. This adds an extra 46 bytes to the transaction. However, it does not disclose any details about the RGB transfer to blockchain observers, appearing merely as an OP_RETURN with a hash, like open timestamp transactions. The benefit of this method over the Taproot-based approach lies in its simplicity and the ease of implementation for wallet developers.

If a Bitcoin transaction contains several commitments, only the first one is pertinent to the RGB validation rules. Any additional commitments will be disregarded. This approach renders any efforts to double-spend ineffective.

PreviousRGB state transitionsNextRGB Privacy Protection

Last updated 1 year ago