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

Introduction of RGB Contract

RGB contracts are structured to specify mainly three aspects: (i) the associated rights of the contract, such as the ability to transfer an asset, (ii) the validity rules associated with transferring these rights, and (iii) the contract's metadata, like the name of the asset.

Unlike other smart contract systems, in RGB, the rules for transferring rights are established in the original contract and cannot be altered by subsequent owners. This is in contrast to Bitcoin where custom scripts allow any user to lock bitcoins. This design in RGB helps to reduce complexity and the costs associated with validation. Additionally, the contract issuer sets a genesis state, identifying the first owner(s) of each right provided in the contract.

To facilitate the issuance of contracts, issuers can use RGB schemas, which act as templates of contracts that can be used to target specific use cases. Some example of RGB schemas are:

To simplify the creation of contracts, issuers have the option to utilize RGB schemas. These schemas function as contract templates, and can be used to target particular use cases. Examples of such RGB schemas include:

  • RGB20 fungible assets issuance.

  • RGB21 non fungible assets issuance.

  • RGB22 decentralized digital identities.

  • RGB23 verifiable-unique history log for auditable data.

  • RGB24 decentralized global domain name system.

  • RGB25 collectible assets issuance.

Individuals are free to design their own schemas for various applications without needing approval from RGB developers. Nonetheless, it is anticipated that few primary schemas will suffice to address the majority of use cases.

XRBG Wallet will support all the user cases of RGB20, RGB21, RGB22 and RGB24 schemas at the early stage.

PreviousClient-Side-ValidationNextIntroduction of Single-Use Seals

Last updated 1 year ago