RGB++ is an asset protocol that connects Bitcoin UTXOs with Nervos CKB Cells through what its documentation calls isomorphic bindings. It combines Bitcoin-side ownership references with CKB-side state and validation, so it is better understood as a two-chain design than as a change to Bitcoin itself. [1]
| Protocol documentation | Open documentation |
|---|---|
| Directories | Nervos Ecosystem Directory |
How the binding works
A Bitcoin UTXO can serve as a single-use seal: once spent, it cannot be reused to authorize the same state transition. RGB++ maps that UTXO to a corresponding Cell on CKB, where the Cell’s data and scripts can represent additional asset or application state. Transactions on the two networks are coordinated so that the Bitcoin ownership reference and the CKB representation remain connected. [1]
The design uses client-side validation for relevant state. A user’s software checks the state information needed to confirm that a proposed change follows the protocol rules, rather than asking Bitcoin consensus to execute arbitrary CKB-style scripts. CKB adds programmable state and execution, while Bitcoin UTXOs provide the anchoring relationship described by the protocol. [1]
What it enables—and what it does not
This architecture can support assets and application logic associated with Bitcoin UTXOs while using CKB for richer state transitions. It does not make Bitcoin blocks execute CKB scripts, and it does not mean that every Bitcoin wallet or marketplace automatically recognizes an RGB++ asset. Users need compatible software, correct state data, and an understanding of which network a given step uses.
Security depends on the whole flow
The word isomorphic describes how the protocol maps related state; it is not a guarantee that all operational risks disappear. Users and applications must handle client-side validation, transaction ordering, network confirmations, software correctness, and the availability of the data needed to reconstruct state. A security analysis published by the project discusses Bitcoin reorganizations, CKB-side state, and additional locking conditions as design considerations. That analysis is project-authored material, not an independent audit. [2]
When evaluating an RGB++ application, check which asset standard it uses, how the wallet validates state, what confirmation policy is recommended, how recovery works if a transaction is delayed or reorganized, and whether the implementation has an independent review. A protocol design can reduce reliance on some intermediaries without removing the need to understand the specific application and user flow.
See Also
Sources
Last updated: November 4, 2026.