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

Client-Side-Validation

The concept of client-side-validation, introduced by Peter Todd in 2016, revolves around the principle that in a distributed system, validating a state doesn't require the involvement of all participants in a decentralized protocol. Rather, only the parties directly involved in a particular state transition are required to perform this validation.In this method, instead of broadcasting the state transition across a global network, it is condensed into a short cryptographic commitment, such as through the use of cryptographic hash functions. This commitment must then be integrated into a specific "proof-of-publication" medium that embodies three primary characteristics:

  • Proof of Receipt: The capacity to demonstrate that every member of a particular audience has received a message, such as a commitment.

  • Proof of Non-Publication: The ability to verify that some specific message has not been published.

  • Proof of Membership: The capability to confirm that some specific member is indeed part of some certain audience.

RGB protocol adopts the client-side validation model. This involves maintaining all transaction-specific data off the blockchain, allowing only the transaction's sender and receiver to exchange this data. The Bitcoin blockchain is utilized solely for commitment purposes. This method enhances scalability, privacy, and extensibility compared to other protocols that operate with all their logic on-chain.

PreviousQuick QuestionNextIntroduction of RGB Contract

Last updated 1 year ago