Core Concepts
Master the fundamental concepts of RGB++ Protocol including single-use seals, blockchain-enhanced state validation, and key differences from the RGB protocol.
As the name suggests, RGB++ protocol is inspired by the RGB protocol. RGB++ inherits the core concepts from it, while leveraging CKB's unique advantages to enhance and extend these concepts.
The following are the core concepts of the RGB++ protocol and key differences from the RGB protocol.
Single-use seals are a cryptographic mechanism that locks a seal on a message, ensuring that the message can only be read or used once. The RGB++ protocol leverages Bitcoin UTXOs' inherent single-use property to implement this sealing mechanism.
How RGB++ Implements Single-Use Seals
Through the use of single-use seals, the RGB++ protocol creates assets that are cryptographically bound to specific Bitcoin UTXOs. The ownership of these corresponding UTXOs directly establishes ownership of the RGB++ issued assets. To transfer a RGB++ asset, the holder must spend their corresponding UTXO, which effectively consumes the single-use seal and ensures the asset can only be transferred once.
Key Properties
Cryptographic Binding
Assets are cryptographically bound to specific Bitcoin UTXOs
Direct Ownership
UTXO ownership directly establishes RGB++ asset ownership
Single-Use Guarantee
Assets can only be transferred once per UTXO consumption
Bitcoin Security
Inherits Bitcoin's consensus security model
Learn More
For a comprehensive explanation of single-use seals, please refer to this technical article by Peter Todd.
The concept of creating and managing assets on Bitcoin has been a long-standing pursuit in the cryptocurrency space. While Bitcoin's UTXO model provides a robust foundation for value transfer, its intentionally limited scripting system falls short in implementing the sophisticated security validations required for complex asset management, thus creating a need for complementary off-chain smart contract solutions.
RGB Protocol Approach
Client-Side Validation
The RGB protocol employs client-side validation, where transaction verification doesn't require scanning the entire blockchain to collect contract state changes. Instead, it only needs a series of relevant Bitcoin transactions, the RGB transactions committed by these Bitcoin transactions, and their block inclusion proofs (based on Merkle proofs from block headers).
Benefits
Significantly reduces the cost of verifying a specific state of a contract
Challenges
Ordinary users often lack capability to maintain complete transaction histories and provide transaction proofs
RGB++ Enhanced Approach
On-Chain Validation with CKB
RGB++ takes a different approach by leveraging CKB's Turing-complete script system to implement asset security checks. This design offers a more straightforward and accessible verification process for all users.
Key Advantages
Eliminates complex client-side validation - No need for users to maintain transaction histories
Maintains system transparency - All validation happens on-chain with public verification
Reduces user burden - Users only need to verify relevant CKB transactions
Straightforward verification - Simple process to confirm RGB++ transaction state calculations
RGB vs RGB++ Validation
RGB Protocol
- • Client-side validation required
- • Users maintain transaction histories
- • Complex proof generation
- • Higher technical barrier for users
RGB++ Protocol
- • On-chain validation with CKB
- • No local state maintenance needed
- • Simplified verification process
- • Lower barrier for end users
Continue Learning
Now that you understand the core concepts, explore the typical transaction flow and learn how to build with RGB++.