With 207 lines of non-backwards-incompatible code, Blockstream’s sidechain becomes a third venue for RGB assets after Bitcoin and Lightning, opening RGB seals to Simplicity spending conditions for the first time.
The engineering team at KaleidoSwap has demonstrated that assets from the RGB protocol can run natively on Liquid Network, the Bitcoin federated sidechain operated by Blockstream, without bridges, wrapped tokens, or a parallel protocol. The result, laid out in a deep dive published on 13 July, is an open-source proof of concept, not a production-ready product.
The obstacle turned out to be smaller than expected. RGB conceals its commitment – the fingerprint that ties a transfer to the chain – inside a standard Taproot output, whose format is identical on Bitcoin and Liquid because both follow BIP-341. Standard RGB verifiers accepted, without modification, a Liquid transaction output as a valid commitment. The only missing code was the logic that reads a Liquid transaction instead of a Bitcoin one: 207 lines across seven files, a small trait abstracting three verification calls. None of the 45 tests in the suite required changes; the four downstream production libraries recompiled without a single source modification.
On that basis, the team issued a real RGB20 asset on Liquid – with a real contract, a transfer with change, and end-to-end verified anchoring – and demonstrated an atomic swap between an RGB asset on Bitcoin and one on Liquid without a custodian. The two legs of the transaction are bound by a shared secret: either the exchange completes for both parties, or it does not happen at all, and at no point can either party hold both assets simultaneously.
The reason Liquid interests RGB – beyond the speed of confidential transactions – is Simplicity, Blockstream’s formally verifiable smart contract language, live on Liquid mainnet since July 2025 and already used in production for post-quantum signatures and collateralised loan contracts. Because an RGB seal is nothing more than a coin, the chain’s spending conditions become spending conditions on the asset. KaleidoSwap wrote a covenant in Simplicity that consensus enforces on every seal spend: it must carry an RGB commitment. Without the anchor, the transaction is rejected.
Whether RGB maintainers will accept the patch remains to be seen: the proposal has already been submitted as an RFC in the official repository. KaleidoSwap, a founding member of the RGB Protocol Association alongside Bitfinex and Tether, already operates on RGB and Lightning; RGB on Liquid, the team writes, is the natural candidate to become the next scenario supported by its market-maker network.
