Tools/Explorers

RGB Protocol vs Liquid Network: Bitcoin Tokenization Compared

Compare RGB and Liquid for issuing tokens on Bitcoin across privacy, scalability, trust model, and tooling. Technical comparison for developers.

Spark TeamInvalid Date

Overview

Bitcoin tokenization has split into two distinct architectures: RGB Protocol's client-side validated smart contracts and the Liquid Network's federated sidechain with native Issued Assets. Both enable fungible tokens, NFTs, and securities on Bitcoin, but they make fundamentally different tradeoffs around privacy, trust, tooling maturity, and developer experience.

RGB keeps all contract state off-chain and uses Bitcoin solely as a commitment layer, producing a trust-minimized system with inherent privacy. Liquid runs a parallel blockchain operated by a federation of 15 functionaries, offering Confidential Transactions and 1-minute block times at the cost of a federated trust model. The table below summarizes the core differences.

DimensionRGB ProtocolLiquid Network
ArchitectureClient-side validation (off-chain state)Federated sidechain (on-chain state)
Trust modelTrust-minimized (anchored to Bitcoin PoW)Federated (11-of-15 functionary multisig)
PrivacyInherent: no on-chain data, no transaction graphConfidential Transactions: hidden amounts and asset types
SettlementBitcoin block time (~10 min) or Lightning (seconds)~2 minutes (1-minute blocks, 2-confirmation finality)
Token standardsRGB-20 (fungible), RGB-21 (NFTs), RGB-25 (collectibles)Issued Assets (native, no smart contract deployment)
Lightning integrationNative via Bifrost protocolSeparate (requires swap or bridge)
Consensus code size (v0.12)~3,200 linesFull Elements codebase (Bitcoin Core fork)
Mainnet statusv0.11.1 mainnet (July 2025), v0.12 with zk-STARKsProduction since 2018
TVL / adoptionEarly stage~$5B TVL, 1.16M txns in Q1 2026

For a broader view of token protocols on Bitcoin including Ordinals, BRC-20, Runes, and Taproot Assets, see our Bitcoin second-layer token comparison.

Privacy: Client-Side Data vs Confidential Transactions

RGB and Liquid approach privacy from opposite directions. RGB achieves privacy structurally: contract state never touches a public ledger. Only cryptographic commitments are anchored to Bitcoin transactions, and only the parties involved in a contract can validate its state. There is no transaction graph to analyze, no amounts to hide, and no metadata leakage. Chain analysis tools have nothing to work with because the data simply does not exist on any public chain.

Liquid uses Pedersen commitments and Bulletproofs to implement Confidential Transactions. Amounts and asset types are encrypted so that only the sender and receiver can see them. Even Liquid's federation functionaries cannot view transaction amounts. However, the transaction graph itself remains visible on the Liquid blockchain: an observer can see that address A sent something to address B, just not what or how much.

For use cases like securities issuance where investor privacy is critical, both approaches offer meaningful improvements over transparent blockchains. RGB provides stronger theoretical guarantees because the data is never published. Liquid provides practical privacy that is already battle-tested across years of production use.

Trust Model: Trust-Minimized vs Federated

RGB's trust model is anchored directly to Bitcoin's proof-of-work consensus. State transitions are committed to Bitcoin transactions using single-use seals, which means an RGB asset can only be spent once, enforced by Bitcoin's own double-spend protection. No federation, no validators, and no separate consensus mechanism stands between the user and Bitcoin's security.

Liquid relies on a federation of 15 functionaries operated by companies like Blockstream, Bitfinex, and other member organizations. These functionaries run custom hardware security modules to sign blocks and manage the Bitcoin peg wallet. An 11-of-15 threshold is required to sign blocks and process peg-outs. As of Q1 2026, the broader Liquid Federation includes 87 member organizations, though only the 15 functionaries hold signing authority. The Dynamic Federations (DynaFed) upgrade allows adding or removing functionaries without a hard fork.

The tradeoff is clear: RGB inherits Bitcoin's security properties directly but requires both parties to be online for transfers. Liquid provides asynchronous transfers and fast settlement but requires users to trust that at least 5 of 15 functionaries will not collude to steal the federation's Bitcoin reserves.

Scalability and Performance

RGB scales horizontally by design. Each contract operates in its own "shard" with independent history and state, so the system does not suffer from shared-state bottleneck problems. Adding more contracts does not slow down existing ones. On-chain footprint is minimal: a single commitment in an OP_RETURN output can anchor multiple state transitions. When combined with Lightning via the Bifrost protocol, RGB asset transfers settle in seconds with negligible fees.

Liquid blocks share the same maximum weight as Bitcoin blocks but are produced every minute instead of every ten. This gives Liquid roughly 10x Bitcoin's base-layer throughput. Final settlement takes approximately two minutes (two block confirmations). Transaction fees on Liquid are typically a fraction of a cent. However, Confidential Transactions are larger than standard Bitcoin transactions due to the range proofs attached to each output, which partially offsets the throughput gain.

RGB's interactivity requirement is its primary scalability constraint: the receiver must be online to accept a transfer and validate the contract history. This makes RGB less suited for use cases like airdrops or batch distributions where recipients may be offline.

Developer Tooling and Ecosystem

Liquid has a significant head start in developer tooling maturity. Built on Elements, a fork of Bitcoin Core, Liquid inherits most of Bitcoin's RPC interface and tooling ecosystem. Developers familiar with Bitcoin development can issue assets on Liquid with minimal additional learning. The Liquid Developer Documentation covers asset issuance, Confidential Transactions, and peg management with production-ready examples.

RGB's tooling is newer but maturing rapidly. The core libraries include RGB Core, RGB Std, and RGB Lib, with the v0.12 release reducing consensus code from 8,610 lines to 3,198 while achieving over 90% test coverage. Wallet support spans three independent implementations: Iris Wallet (desktop and mobile), BitMask (browser extension by DIBA), and MyCitadel (desktop). The RGB Protocol Association, formed in July 2025 with members including Bitfinex, Fulgur Ventures, and DIBA, coordinates ecosystem development.

ToolingRGB ProtocolLiquid Network
Core languageRustC++ (Bitcoin Core fork)
Client librariesRGB Lib (Rust, with FFI bindings)Elements RPC, Liquid SDK
WalletsIris Wallet, BitMask, MyCitadelBlockstream Green, SideSwap, Aqua
Asset issuanceSchema-based (RGB-20, RGB-21, RGB-25)Native CLI or API (rawissueasset)
ExplorerNo public explorer (by design)Blockstream.info/liquid
TestnetRGB SandboxLiquid Testnet
Documentation maturityImproving (protocol-focused)Comprehensive (developer-focused)
NFT marketplaceDIBA (P2P, non-custodial)Raretoshi (community-driven)

For a deeper look at RGB's technical architecture including single-use seals, schema definitions, and Bifrost integration, see our RGB Protocol research article.

Real-World Asset Issuance

Securities tokenization, stablecoins, and collectibles each play to different strengths of the two platforms.

Securities and Tokenized Bonds

Liquid currently leads in regulated securities issuance. Bitfinex Securities has issued over $250 million in tokenized assets on Liquid, including bonds, equity, and the first regulated public offering of tokenized US Treasury bills on a Bitcoin sidechain. STOKR crossed $1.5 billion in tokenized asset volume by end of 2025, with its Blockstream Mining Note 2 (BMN2) valued at $790 million. Confidential Transactions are a key feature for institutional adoption: investor holdings and trade sizes remain private while compliance tools can selectively verify balances.

RGB does not yet have comparable securities issuance activity, but its privacy model is architecturally well-suited for regulated instruments. The schema-based contract system supports programmable transfer restrictions, and the absence of a public transaction graph eliminates front-running and copycat trading risks.

Stablecoins

Tether (USDT) is live on Liquid with approximately $97 million in circulation as of mid-2026, making L-USDT the most liquid stablecoin on any Bitcoin sidechain. In August 2025, Tether also announced plans to launch USDT natively on Bitcoin via the RGB protocol, signaling that both platforms will host the same stablecoin. BitMask went mainnet in November 2025 with RGB-20 support, establishing the wallet infrastructure needed for stablecoin transfers.

For Bitcoin-native stablecoin payments, platforms like Spark offer an alternative path with instant settlement and near-zero fees, supporting stablecoins like USDB directly on Bitcoin without requiring a sidechain or client-side validation.

Collectibles and NFTs

RGB-21 defines a non-fungible token standard with support for engravings (custom metadata attached by the owner). DIBA's marketplace provides non-custodial P2P trading of RGB-based digital art using atomic swaps. Liquid supports NFTs through its Issued Assets feature, with Raretoshi serving as a community marketplace. Neither platform has achieved the NFT volume seen on Ethereum or Ordinals, though both offer stronger privacy guarantees for collectors.

For broader context on how tokenization is evolving across Bitcoin and other networks, see our RWA tokenization on Bitcoin research article.

How to Choose Between RGB and Liquid

The right platform depends on your specific requirements. Here is a decision framework based on common use cases:

If privacy is the top priority: RGB's client-side validation means no data ever reaches a public chain. This is the strongest privacy model available for Bitcoin tokenization. Liquid's Confidential Transactions hide amounts but not the transaction graph.

If you need production-ready securities issuance today: Liquid has years of production history, proven regulatory pathways through Bitfinex Securities and STOKR, and mature developer tooling. RGB is approaching production readiness but has fewer deployed use cases.

If trust minimization matters most: RGB anchors directly to Bitcoin's proof-of-work security with no federation or separate consensus layer. Liquid requires trust in the functionary federation.

If you want Lightning Network integration: RGB tokens can flow through Lightning channels natively via Bifrost, enabling instant settlement with Bitcoin-level security. Liquid operates as a separate network from Lightning.

If developer experience is the priority: Liquid is easier to adopt for teams already familiar with Bitcoin Core. Asset issuance is a single RPC call. RGB requires learning a new validation paradigm and working with newer, less documented libraries.

The two protocols are also increasingly complementary. RGB v0.11 introduced native bridging with Liquid's Confidential Assets, allowing RGB smart contracts to operate on both Bitcoin and Liquid.

Frequently Asked Questions

What is the difference between RGB and Liquid for Bitcoin tokens?

RGB is a client-side validation protocol where all token state lives off-chain and only cryptographic commitments are anchored to Bitcoin. Liquid is a federated sidechain that runs its own blockchain with 1-minute blocks, Confidential Transactions, and native asset issuance. RGB prioritizes privacy and trust minimization. Liquid prioritizes speed, tooling maturity, and production readiness for financial instruments.

Is RGB more private than Liquid?

Yes, at the architectural level. RGB stores no data on any public chain, so there is no transaction graph, no amounts, and no metadata to analyze. Liquid's Confidential Transactions hide amounts and asset types using Pedersen commitments and Bulletproofs, but the transaction graph (who transacted with whom) remains visible on the Liquid blockchain.

Can you issue stablecoins on both RGB and Liquid?

Yes. Tether (USDT) is already live on Liquid with approximately $97 million in circulation and has announced plans to launch USDT on RGB as well. Both platforms support fungible token standards suitable for stablecoin issuance: RGB-20 on RGB and Issued Assets on Liquid.

Is Liquid centralized?

Liquid uses a federated model rather than a fully decentralized one. Fifteen functionaries operated by different companies sign blocks and manage the Bitcoin peg wallet using a multisig threshold of 11-of-15. The broader Federation includes 87 member organizations as of Q1 2026. This is more centralized than Bitcoin's open mining but more distributed than a single custodian. The Dynamic Federations upgrade allows changing functionaries without a hard fork.

Does RGB work with the Lightning Network?

Yes. RGB integrates with Lightning through the Bifrost protocol, allowing RGB tokens to flow through payment channels alongside regular Bitcoin payments. This enables near-instant settlement with negligible fees for RGB asset transfers. Liquid does not natively integrate with Lightning, though atomic swaps between the two networks are possible.

Which platform is better for tokenized securities?

As of mid-2026, Liquid has the stronger track record for securities issuance. Bitfinex Securities and STOKR have collectively issued billions of dollars in tokenized bonds, equity, and Treasury bill products on Liquid. RGB's privacy model is architecturally compelling for securities (no public transaction graph), but the ecosystem lacks comparable regulatory pathways and issuance infrastructure at this stage.

Can RGB and Liquid work together?

Yes. RGB v0.11 introduced native bridging with Liquid's Confidential Assets, enabling RGB contracts to function on both Bitcoin and Liquid. This allows developers to use Liquid for fast settlement and Confidential Transactions while leveraging RGB's client-side validation for off-chain state management. The two protocols are increasingly designed as complementary layers rather than direct competitors.

This tool is for informational purposes only and does not constitute financial advice. Data is approximate and based on publicly available information as of mid-2026. Protocol specifications, adoption metrics, and ecosystem tooling change frequently. Always verify current data on official project documentation before making technical or investment decisions.

Build with Spark

Integrate bitcoin, Lightning, and stablecoins into your app with a few lines of code.

Read the docs →