Definition: RGB Protocol on Bitcoin (usually called RGB) is a protocol for issuing and transferring digital assets using client-side validation: participants check the relevant contract history in their own software, while Bitcoin transactions anchor compact commitments and UTXO-based single-use seals. The protocol keeps most asset rules and transfer data off Bitcoin’s public ledger, but Bitcoin nodes still validate the anchor transactions under Bitcoin’s rules.23
| Mainnet status | The RGB team announced v0.11.1 on Bitcoin mainnet in July 2025. Its October 2026 update identified v0.11.1 as stable and v0.11.2-rc.1 as a release candidate.19 |
|---|---|
| Validation model | Client-side validation with Bitcoin UTXO-based seals and compact transaction commitments.23 |
| Lightning | RGB asset transfers over Lightning are described in the protocol documentation; wallet and channel support depends on the implementation.5 |
| External links | |
| Directories | Bitcoin Technology & Infrastructure |
How RGB works
RGB changes where contract rules and asset history are checked. Bitcoin’s consensus rules verify Bitcoin transactions, including that inputs spend available outputs and that scripts are satisfied. They do not execute an RGB asset’s schema. Instead, the people receiving or holding an RGB asset validate the relevant contract state and its history with compatible software. Each client checks the transitions that matter to that contract rather than asking every Bitcoin node to process the same asset data.27
This design does not create a second public blockchain. Bitcoin acts as the publication and ordering layer for compact commitments, while contract data is carried separately. The recipient needs the appropriate data package, called a consignment, and checks it before accepting the state transition. RGB documentation describes the package as containing the contract information and history needed for validation; how participants deliver that data is handled separately from Bitcoin’s block relay.4
UTXOs, seals, and commitments
RGB ties an asset allocation to a Bitcoin unspent transaction output (UTXO). Its documentation identifies the TxO2 single-use-seal design: a particular output defines the seal, and spending that output closes it. Bitcoin’s rule against spending the same UTXO twice supplies the one-time-use property; RGB clients check the associated asset history and rules.3
| Part | Role |
|---|---|
| RGB state transition | Applies an operation allowed by the contract’s schema, such as assigning an asset to a new owner. |
| Bitcoin UTXO seal | Connects an owned RGB state to a Bitcoin output; spending the output closes the single-use seal. |
| Commitment | Anchors a compact cryptographic commitment to a Bitcoin transaction. The documentation describes OP_RETURN-based Opret and Taproot-based Tapret commitment methods. |
| Consignment | Carries the off-chain contract data and relevant history that a recipient imports and validates. |
A commitment is not the asset data itself. Bitcoin nodes can check the Bitcoin transaction and preserve its public commitment without reconstructing the RGB contract or validating the asset’s full state history.234
Asset schemas and transfers
An RGB schema is a template that defines a contract’s data and permitted operations. The documentation describes several schema families, including non-inflatable fungible assets (NIA), unique digital assets (UDA), and collectible fungible assets (CFA). Other documented schemas include inflation-capable and permissioned asset designs; their presence in technical documentation does not by itself mean they are ready for production or supported by every wallet.612
For a transfer, the recipient provides an invoice that specifies where the asset should be assigned. The sender constructs the transition and the related Bitcoin transaction, then gives the recipient the consignment needed to verify the contract history. The recipient’s wallet checks that package against the schema and prior transitions before treating the asset as received. This puts a real data-management responsibility on participants: an on-chain Bitcoin record does not contain every off-chain file needed by an RGB wallet.4
RGB can also move through compatible Lightning Network channels. The technical design associates RGB state updates with channel commitment transactions, so channel and wallet software must support the relevant RGB behavior. Bitcoin satoshis are still needed for the channel’s Bitcoin outputs and transaction constraints. “Works over Lightning” therefore describes protocol compatibility, not universal support in every Lightning wallet.5
Privacy, data availability, and limitations
Client-side validation can keep much contract and transfer information out of Bitcoin’s public transaction data. It does not make Bitcoin activity anonymous: the anchoring transactions and their timing remain public, and observers may infer connections from other information. Some contract information can also be global or publicly shared, depending on the schema and operation; privacy depends on what is disclosed and how the software handles it.27
Because a recipient validates data supplied outside the blockchain, participants need to receive and retain the right consignments and use compatible software. Loss of local data, unavailable counterparties, incompatible schema versions, or wallet limitations can affect recovery and verification. Mainnet availability is not a guarantee that every asset is legitimate, liquid, audited, or supported by a particular wallet. Check the issuer, contract, wallet, and software version independently before relying on an asset.
RGB and RGB++ are different designs
RGB++ is related by name and draws on concepts such as UTXO seals, but it should not be treated as another name for RGB Protocol on Bitcoin. Nervos documentation describes RGB++ as an extension of RGB and explains that it maps Bitcoin UTXOs to cells on the Nervos CKB blockchain. The RGB Protocol project’s GitHub describes RGB++ as a separate protocol with a different architecture. The concrete distinction is that RGB’s asset state is validated client-side and anchored to Bitcoin, while RGB++ pairs Bitcoin activity with CKB state and transactions.1011
| Topic | RGB Protocol on Bitcoin | RGB++ |
|---|---|---|
| State model | Clients validate relevant RGB contract history and consignments. | Uses isomorphic bindings between Bitcoin UTXOs and CKB cells. |
| Chain role | Bitcoin transactions anchor commitments and close UTXO seals. | A design pairs Bitcoin transactions with CKB transactions and state. |
| How to distinguish | Search for RGB Protocol on Bitcoin and its client-side validation documentation. | Check whether the page describes CKB cells and the RGB++ protocol. |
History and software status
- 2016: RGB’s FAQ traces the underlying client-side-validation and single-use-seal research to work presented by Peter Todd at Scaling Bitcoin Milan. This is an intellectual-history milestone, not the launch date of the current RGB software line.12
- July 16, 2025: The RGB team announced v0.11.1 as live on Bitcoin mainnet.1
- September 16, 2026: Five core libraries received plain v0.11.1 tags after their release-candidate cycle, according to a later project update.8
- October 9, 2026: Five core libraries tagged v0.11.2-rc.1, the first release candidate of v0.11.2. In its October 15 update, the RGB team said v0.11.1 remained the latest stable release; higher-level wallet tools may follow their own version schedules.9
Release status changes over time. Check the project’s current release notes and the versions supported by a wallet before installing software or moving assets.
Last updated: November 12, 2026.
Related Terms
Related Articles
These articles provide adjacent background on Bitcoin, asset issuance, and crypto token economics.
- Bitcoin as Collateral: Bank Loans, Mortgages, and DeFi Explained
- What the 2024 U.S. Spot Bitcoin ETP Launch Changed — and What It Didn’t
- What Happens to Bitcoin Mining Rewards After New BTC Issuance Ends?
- Can Tokenomics Tell Whether a Crypto Project Is Sustainable?
See Also
Sources
- RGB Team, “RGB v0.11.1 Is Live on Bitcoin Mainnet,” July 16, 2025, https://rgb.info/rgb-v0-11-1-bitcoin-mainnet-launch/ (accessed November 12, 2026).
- RGB Protocol Documentation, “Client-side Validation,” https://docs.rgb.info/distributed-computing-concepts/client-side-validation (accessed November 12, 2026).
- RGB Protocol Documentation, “Bitcoin Single-use Seals,” https://docs.rgb.info/annexes/single-use-seals-bitcoin (accessed November 12, 2026).
- RGB Protocol Documentation, “Contract Transfers,” https://docs.rgb.info/annexes/contract-transfers (accessed November 12, 2026).
- RGB Protocol Documentation, “Lightning Network Compatibility,” https://docs.rgb.info/rgb-over-lightning-network/lightning-network-compatibility (accessed November 12, 2026).
- RGB Protocol Documentation, “Supported Schemas,” https://docs.rgb.info/rgb-contract-implementation/schema/supported-schemas (accessed November 12, 2026).
- RGB Protocol Documentation, “Components of a Contract Operation,” https://docs.rgb.info/rgb-state-and-operations/components-of-a-contract-operation (accessed November 12, 2026).
- RGB Team, “RGB Protocol v0.11.1: Core Libraries Drop the RC Tag,” September 23, 2026, https://rgb.info/rgb-protocol-v0-11-1-core-libraries-update/ (accessed November 12, 2026).
- RGB Team, “RGB Protocol v0.11.2-rc.1: First Release Candidate After v0.11.1,” October 15, 2026, https://rgb.info/rgb-protocol-v0-11-2-rc1-update/ (accessed November 12, 2026).
- Nervos CKB, “RGB++ Protocol,” https://docs.nervos.org/docs/assets-token-standards/rgbpp (accessed November 12, 2026).
- RGB Protocol, “RGB Protocol on Bitcoin,” GitHub, https://github.com/rgb-protocol (accessed November 12, 2026).
- RGB Protocol, “Frequently Asked Questions,” https://rgb.info/rgb-faq/ (accessed November 12, 2026).