HomeBlogServicesAboutContact Contact Us →
Article

What Is RGB? How Stablecoins and Tokens Can Use Bitcoin

July 13, 2026 · Proofoftech Blogger

RGB is a protocol for issuing and transferring digital assets whose ownership is connected to Bitcoin transactions. It keeps most contract data with the people using the asset, while Bitcoin supplies transaction ordering, UTXO double-spend protection and cryptographic commitments.

That design could support stablecoins, fungible tokens and other digital rights without placing a complete public token ledger inside Bitcoin blocks. A fiat-backed stablecoin would still depend on its issuer for reserves and redemption. Bitcoin can help secure the transfer history. It cannot prove that dollars exist in a bank account.

RGB is a smart contract protocol designed for Bitcoin and Lightning, with contract data kept off Bitcoin's public ledger.
RGB is a smart contract protocol designed for Bitcoin and Lightning, with contract data kept off Bitcoin’s public ledger.

What is the RGB protocol?

RGB is a client-side-validated smart contract protocol that uses Bitcoin as its commitment and ownership foundation.

“Client-side validation” means the recipient checks the contract history needed to confirm an asset transfer. The entire Bitcoin network does not execute every RGB contract, and every RGB user does not need a copy of every RGB asset’s complete history.

The holder’s wallet keeps or receives the data needed to validate that particular asset. Bitcoin records commitments associated with the relevant transactions and prevents the same Bitcoin output from being spent twice.

This division of work is central to RGB:

  • Bitcoin secures and orders the UTXOs used to control RGB rights.
  • RGB software checks whether a contract transition follows its rules.
  • The parties exchange the relevant contract data outside Bitcoin’s global ledger.

The result is a different model from an ERC-20 token on Ethereum. Ethereum nodes execute and maintain a shared smart contract state. RGB recipients validate the history that matters to the asset they are receiving.

Are RGB tokens stored on Bitcoin?

RGB tokens are controlled through Bitcoin-related commitments and UTXOs, while their detailed contract state is stored and transferred client-side.

The phrase “tokens on Bitcoin” can therefore cause confusion. It may suggest that every balance, transfer and piece of metadata appears in Bitcoin blocks. RGB was designed to avoid that global public record.

Bitcoin still performs an important job. An RGB state transition is tied to a Bitcoin transaction through a cryptographic commitment. The Bitcoin transaction spends the output that controlled the previous asset state. Bitcoin’s consensus rules prevent that output from being spent again in a conflicting transaction.

RGB clients handle the contract-specific work. They check the genesis, ownership assignments, state transitions, Bitcoin witnesses and the rules defined by the contract’s schema.

A useful description is:

RGB anchors asset ownership transitions to Bitcoin while keeping the contract history with the relevant participants.

How does an RGB asset begin?

An RGB asset begins with a contract genesis that defines its initial state and issuance rules.

Depending on the asset, the genesis may define:

  • The asset name and ticker.
  • Decimal precision.
  • Initial supply.
  • Ownership assignments.
  • Rights to issue additional units.
  • The schema that determines valid state transitions.

The schema matters because an RGB recipient needs a clear set of rules for validation. A wallet cannot simply accept a file that claims someone owns one million tokens. It must be able to trace the relevant history back to a valid genesis and confirm that each transition followed the contract rules.

RGB documentation describes fungible asset models for different supply policies. A non-inflatable asset can have a fixed supply. An inflatable fungible asset can retain controlled secondary issuance rights. The second model is the more natural fit for a conventional fiat-backed stablecoin because the issuer may need to create units when customers deposit money and remove units when customers redeem them.

RGB separates Bitcoin and Lightning commitments from off-chain contract data, schema, interfaces and state transitions.
RGB separates Bitcoin and Lightning commitments from off-chain contract data, schema, interfaces and state transitions.

How does an RGB transfer work?

An RGB transfer combines a Bitcoin transaction, an RGB state transition and an off-chain data package called a consignment.

The exact user experience will depend on the wallet and RGB version, but the basic sequence works as follows.

  1. The receiver creates an RGB invoice or provides the information needed for a new assignment.
  2. The sender constructs a state transition that consumes the existing asset assignment and creates a new one for the receiver.
  3. A Bitcoin transaction spends the UTXO connected to the previous assignment.
  4. A cryptographic commitment to the RGB transition is associated with that Bitcoin transaction.
  5. The sender delivers a consignment containing the history and proof data needed by the receiver.
  6. The receiver validates the consignment before accepting the asset.

The receiver’s wallet should check that the asset came from a valid genesis, that each relevant transition followed the schema and that the Bitcoin outputs were spent as claimed. It also checks whether the sender had the rights being transferred.

This local verification reduces the amount of asset data published globally. It also places more responsibility on wallets and users. Consignments must arrive. Wallet state needs reliable backups. Software must manage RGB-related UTXOs correctly.

What are single-use seals?

Single-use seals connect an RGB ownership right to something that can be closed only once. Bitcoin UTXOs fit that purpose because a valid UTXO can only be spent once.

An RGB assignment may be controlled by a particular Bitcoin output. Spending that output closes the current seal. The state transition then assigns rights to one or more new outputs.

Bitcoin’s double-spend protection helps establish which closure is valid. RGB software still checks whether the asset transition itself obeyed the contract.

This distinction matters. Bitcoin nodes can reject an invalid Bitcoin spend. They do not automatically understand the name, supply rules or business meaning of an RGB stablecoin.

How can RGB support a stablecoin?

RGB can represent stablecoin units through a fungible asset contract with controlled issuance and transfer rules.

A conventional fiat-backed model could work like this:

  1. A customer deposits dollars with an issuer.
  2. The issuer creates or releases the corresponding RGB stablecoin units.
  3. The units are assigned to the customer’s wallet.
  4. The customer transfers them through RGB transactions.
  5. A later holder returns units to the issuer for redemption.
  6. The issuer pays out fiat and retires or accounts for the redeemed supply.

RGB can help recipients verify whether token issuance and transfers followed the digital contract’s rules. The issuer still controls the relationship between those units and the money held in reserve.

For a dollar-backed token, the peg usually depends on reserve quality, redemption access, market liquidity and confidence in the issuer. A simple redeemable stablecoin may not need an oracle merely to represent one dollar. An oracle becomes relevant when contract rules depend on outside information such as an exchange rate, collateral value or liquidation threshold.

RGB can represent assets such as stablecoins while using Bitcoin transactions as the commitment and settlement anchor.
RGB can represent assets such as stablecoins while using Bitcoin transactions as the commitment and settlement anchor.

Does Bitcoin make an RGB stablecoin trustless?

A fiat-backed RGB stablecoin retains issuer trust because the issuer holds or manages the reserves and promises redemption.

Bitcoin can contribute:

  • UTXO double-spend prevention.
  • Transaction ordering and confirmation.
  • A durable record of commitments.
  • Censorship resistance for valid Bitcoin transactions.

Bitcoin cannot confirm:

  • Whether the issuer has enough dollars.
  • Whether reserve reports are accurate.
  • Whether a bank will release the money.
  • Whether the issuer will process a redemption.
  • Whether regulators will restrict an account or service.
  • Whether one token will continue trading near one dollar.

This is why the phrase “trustless stablecoin” needs care. RGB can reduce dependence on a bridge, sidechain federation or separate global validator set for token transfers. The issuer remains part of the economic trust model.

Self-custody also has a specific meaning here. A user may control the token’s private keys without controlling the dollars that back it. Those are two different forms of custody.

What can other RGB tokens represent?

RGB contracts can represent fungible assets, unique assets and other programmable rights.

Possible uses include:

  • Fixed-supply community or loyalty tokens.
  • Securities with defined transfer restrictions.
  • Collectibles and unique digital items.
  • Tokenized claims on real-world assets.
  • Membership, identity or access rights.
  • Other contract-controlled digital property.

Each use case brings its own off-chain assumptions. A tokenized security depends on an issuer and applicable law. A tokenized claim on gold depends on the custodian holding the gold. A membership token depends on an organization honoring the membership.

The protocol can help establish which wallet controls a valid digital assignment. It cannot force an outside company, court, warehouse or bank to honor a real-world promise.

Why use client-side validation?

Client-side validation can improve privacy and reduce the need for global blockchain storage.

An ordinary public token ledger exposes balances and transfers to anyone who can read the chain. RGB keeps much of the contract state within the group of people who need it. An outside observer may see a Bitcoin transaction without seeing a complete public record of the RGB asset involved.

Privacy still depends on wallet behavior and implementation details. Bitcoin transaction analysis may connect UTXOs. A counterparty sees information needed for the transfer. An issuer or regulated exchange may maintain customer records. Indexers, proxy servers and other services can also learn something about user activity.

The scaling advantage comes from selective validation. A person receiving one RGB asset does not need to process every unrelated RGB contract. Bitcoin block space is used for commitments and settlement transactions instead of carrying every detail of a global token ledger.

The trade-off is local responsibility. Users need dependable software, state backups and access to the relevant consignments. The data burden moves away from a global blockchain and toward wallets and counterparties.

Can RGB stablecoins move over the Lightning Network?

RGB is being developed for Lightning-compatible transfers, but the public implementation remains early-stage.

The intended design allows RGB assets to be assigned within Lightning channels and updated as payments move through compatible nodes. That could eventually provide fast, small stablecoin payments while Bitcoin and Lightning handle the channel structure.

The current rgb-lightning-node repository describes the software as early alpha and limits RGB functionality to regtest or testnet by default. Its published roadmap still includes work on fee management, reorganization handling, audits, privacy, databases and penalty-transaction testing.

A careful description is that RGB supports a path toward stablecoins over compatible Lightning infrastructure. General-purpose production use through ordinary Lightning wallets has not yet reached the maturity implied by some promotional material.

Is Tether’s USDT available on RGB?

Tether announced in August 2025 that it planned to launch USDT on RGB. The announcement described future support for holding and transferring USDT alongside Bitcoin in compatible wallets.

RGB ecosystem companies have since described infrastructure and commercial rollout work. A newer primary Tether announcement confirming broad public availability was not found during preparation of this draft.

For that reason, Proof of Tech should describe Tether’s RGB integration as announced and under development or rollout. We should wait for clear first-party confirmation before telling readers that USDt on RGB is generally available.

Which RGB version should developers and users follow?

RGB currently has competing version and implementation narratives, so version numbers need to be stated carefully.

The Core Concepts documentation promotes RGB v0.12 and describes major changes to contracts, commitments and Lightning support. The RGB Protocol Association and the active wallet ecosystem recommend v0.11.1 as the practical production baseline. The Association says existing mainnet applications use v0.11.1 and argues that v0.12 has not completed the integration testing needed for its production claims.

These versions are not a routine patch difference. The v0.12 documentation describes consensus-breaking changes and says older contracts require reissuance.

A beginner does not need to choose a software stack after reading one article. Developers and advanced users do need to verify which RGB branch, wallet and contract version they are using. Instructions written for one version may not work with another.

What are the main RGB risks and trade-offs?

RGB’s main trade-offs involve data availability, wallet maturity, version compatibility and trust outside the protocol.

Consider the following before using an RGB asset:

  • Can the wallet preserve the contract history and consignments needed for recovery?
  • Does the wallet support the same RGB version as the sender and issuer?
  • What happens if a required proxy, indexer or counterparty is unavailable?
  • Who controls additional issuance rights?
  • Can the issuer freeze, refuse or delay redemption through its legal and banking systems?
  • Has the software been audited and tested with real funds?

The rgb-lib project warns that it remains work in progress and in a testing phase. Its documentation also warns against using the same wallet on more than one device because incorrect UTXO management may cause asset loss.

That warning deserves more attention than a polished demonstration video. RGB has a serious technical design and active development. Its user experience and operational safeguards still need to mature.

Is RGB good for Bitcoin?

RGB gives developers a way to build richer asset contracts while keeping Bitcoin’s base layer focused on Bitcoin transactions and commitments.

People who want Bitcoin to remain simple may prefer that approach over placing a large public token state directly on-chain. People who want globally visible asset data may find client-side validation and consignment management harder to work with.

The better question is whether RGB’s privacy and scaling benefits are worth the extra wallet and data-management responsibility for a particular use case.

For stablecoins, RGB offers a credible technical path to self-custodied token transfers anchored to Bitcoin. The backing remains an issuer promise. For other tokens, the same rule applies: RGB can secure the digital ownership history, while any real-world claim depends on the organization standing behind it.

If you are still learning how Bitcoin establishes a shared transaction history, read Proof of Tech’s guide to blockchain consensus. It will make the difference between Bitcoin consensus and RGB client-side validation much easier to understand.

FAQ

Does RGB have its own blockchain?

No. RGB uses Bitcoin transactions and commitments while keeping contract data and validation client-side. It does not require a separate RGB blockchain with its own global transaction ledger.

Does an RGB transfer require a Bitcoin transaction?

A settled ownership transition uses a Bitcoin transaction to close the previous UTXO-based seal and commit to the new state. Future Lightning-based flows may update RGB state within compatible channels before final settlement.

Can an RGB stablecoin lose its peg?

Yes. The peg depends on the issuer, reserves, redemption access and market liquidity. Bitcoin anchoring does not guarantee a one-dollar market price.

Are RGB transfers private?

RGB avoids publishing a complete public token ledger, which can provide stronger privacy than transparent global token systems. Bitcoin analysis, counterparties, issuers and supporting services may still reveal information.

Can I recover RGB assets with a seed phrase alone?

Recovery depends on the wallet implementation and the availability of RGB state data. Users should follow the wallet’s documented backup process rather than assume a seed phrase preserves every required consignment and contract record.

Is RGB ready for beginners?

RGB can be used through supported wallets, but the version split, backup requirements and early-stage Lightning tooling make it more demanding than mature mainstream wallet systems. Beginners should use small amounts and verify the exact wallet, version and recovery procedure.

What should you remember about RGB?

RGB lets people issue and transfer digital assets whose ownership transitions are anchored to Bitcoin and validated by the recipient. Its design may offer better privacy and less global data than public token ledgers.

Stablecoins show both the promise and the limit of the model. RGB can help verify the digital token’s history. The issuer must still hold the reserves and honor redemption.

Ask yourself what protection you expect from the protocol and what protection still depends on a company. That question will help you judge RGB stablecoins, tokenized assets and most other forms of crypto-backed promises.

Disclaimer: The content on this blog is provided for general informational and educational purposes only and does not constitute financial, investment, legal, or tax advice. Cryptocurrency and Bitcoin-related technologies are experimental and may involve substantial risk. Always conduct your own research, verify software and contract versions, and consult a qualified professional before making financial decisions. The author and blog assume no responsibility for losses arising from reliance on this content.

Sources

Continue with these related Proof of Tech guides: