In the previous article “The Cornerstone of RGB and RGB++ Protocols: One-Time Sealing and Client Verification”, we briefly introduced the differences in verification methods between RGB and RGB++ protocols: RGB requires users to run the client for verification, while RGB++ achieves asset verification using a Turing-complete UTXO blockchain (such as Nervos CKB) through isomorphic binding (of course, users can still choose to verify themselves), thereby simplifying user operations.
For asset issuance protocols, security is always the primary consideration. In today’s article, we will continue to introduce RGB++, detailing what isomorphic binding is and why the RGB++ protocol is considered extremely secure.
What is Isomorphic Binding?#
The use of isomorphic binding technology is predicated on isomorphism. The Cell model of the CKB blockchain is an advanced version of the Bitcoin UTXO model, both of which share the same root. This similarity allows us to use isomorphic binding technology to bind or map UTXOs from one blockchain to UTXOs on another blockchain. Taking the RGB++ protocol as an example, since RGB assets essentially parasitize Bitcoin UTXOs, the RGB++ protocol can utilize isomorphic binding technology to map Bitcoin UTXOs to Cells on the CKB blockchain, allowing us to use the CKB blockchain to replace the client verification of the RGB protocol.
To better understand isomorphic binding technology, we can use land and land deeds as an analogy:
- If we compare the Bitcoin mainnet to land, and Zhang San issues an asset through the RGB++ protocol, this asset is a paper land deed corresponding to 100 acres of land. The paper land deed is stored on the Bitcoin blockchain (i.e., in UTXO, which Zhang San owns), and the isomorphic binding technology is equivalent to issuing a corresponding electronic land deed on the CKB blockchain (stored in a Cell).
- Zhang San transfers 40 acres of land to his relative Li Si, thus the original 100 acres paper land deed is destroyed, generating a new paper land deed, one for 40 acres and another for 60 acres, still stored on the Bitcoin blockchain. The difference is that the 40 acres deed is stored in a UTXO controlled by Li Si, while the 60 acres deed is stored in a UTXO controlled by Zhang San. It should be noted that the role of the Bitcoin blockchain here is to prevent Zhang San from using the 100 acres paper land deed multiple times (i.e., double spending), rather than verifying whether the new land deeds add up to exactly 100 acres. In other words, under the original RGB protocol, whether the deed Li Si receives states 40 acres needs to be verified by Li Si himself, and he also needs to verify the land provenance proof provided by Zhang San (the original RGB protocol requires client verification, and this client verification needs to be performed by the user).
- The Bitcoin light client deployed on the CKB blockchain verifies the event of “destroying the 100 acres paper land deed, generating a 40 acres paper land deed and a 60 acres paper land deed” that occurred on the Bitcoin blockchain, confirming whether it really happened.
- After verification, the 100 acres electronic land deed on the CKB blockchain is destroyed, generating a 40 acres electronic land deed and a 60 acres electronic land deed. It is important to note that since the CKB blockchain is Turing-complete, it can verify and ensure that the areas of the two newly generated electronic land deeds add up to exactly 100 acres, and Li Si can see at a glance that his deed states 40 acres (because the data on the CKB blockchain is publicly visible). Therefore, the RGB++ protocol can replace the client verification of the RGB protocol, omitting Li Si's verification in step 2 (including land provenance verification).
The above four steps correspond exactly to the four operational processes of isomorphic binding technology: mapping UTXOs to Cells, verifying transactions, cross-chain verification, and state changes on CKB.
Security Analysis#
Through the analogy of land and land deeds, we can clearly see that the security and prevention of double spending of the paper land deed stored in Bitcoin UTXOs mainly rely on the security of the Bitcoin blockchain. And Bitcoin, as the longest-running and most secure PoW chain, has its security tested by time.
The security and prevention of double spending of the electronic land deed generated through isomorphic binding technology mainly rely on the security of the CKB blockchain. From the beginning, CKB adopted the same, time-tested PoW consensus mechanism as Bitcoin, maximizing security and decentralization. Currently, the mining equipment for CKB is produced by Bitmain, the largest ASIC miner manufacturer in the world, and the current total network hash rate of CKB has surpassed 440 PH/s, setting a historical high. It is extremely difficult to forge or reconstruct a PoW chain, as this requires recalculating the hash power of each block, akin to attempting to rebuild a pyramid overnight, which is nearly impossible. Therefore, we can fully trust the security of the CKB blockchain.
Of course, if you still have doubts, you can choose to verify it yourself, just like in step two of the previous example, to confirm whether the deed really states 40 acres and whether the land provenance proof provided by Zhang San is authentic and valid. This is also the practice of the RGB protocol, where users need to complete client verification themselves; the RGB++ protocol merely provides an additional option, allowing users to either complete client verification themselves or trust the verification of the CKB blockchain, which here serves only as a DA layer and state disclosure, with the security of the paper land deed transaction even having no direct relation to CKB.
The charm of the RGB++ protocol lies not only in allowing the CKB blockchain to act as a DA layer but also in supporting Leap operations, enabling RGB++ assets on the Bitcoin blockchain to freely traverse the CKB blockchain (of course, reverse operations are also possible, and in the future, it can be expanded to other Turing-complete UTXO blockchains). Since the CKB blockchain is Turing-complete, developers can build various complex DeFi applications on it, such as lending platforms, decentralized exchanges, etc. This means that RGB++ assets transferred to the CKB blockchain through Leap operations can participate in a wide variety of financial activities, such as collateralized lending, staking for interest, trading, and more.
When you hold RGB++ assets transferred to the CKB chain through Leap operations and participate in various financial activities, the security of these operations mainly relies on the security of the CKB blockchain. As we discussed earlier, the CKB blockchain itself has high security. However, if you still have concerns about the security of the CKB blockchain, you can always choose to transfer the RGB++ assets on the CKB chain back to the Bitcoin blockchain through Leap operations, turning them back into RGB++ assets on the Bitcoin blockchain.
When discussing the Leap feature, we must mention the risks it may face — block reorganization. However, this risk can be effectively mitigated by waiting for more block confirmations. In the Bitcoin network, transactions are generally considered irreversible after six block confirmations. It is worth noting that the number of confirmations in PoW does not have a linear relationship with security; the difficulty of overturning PoW blocks increases exponentially with the number of blocks. Therefore, to achieve the same level of security as six block confirmations in Bitcoin on the CKB blockchain, it has been calculated that approximately 24 CKB block confirmations are needed. Considering that the average block time for CKB is about 10 seconds, the time required for 24 block confirmations is actually much shorter than that required for six block confirmations in Bitcoin.
Figure: A diagram of PoW security; Source: https://talk.nervos.org/t/rgb-1/7798
So, if you want to achieve higher security assurance, you just need to wait for a few more block confirmations.
Conclusion#
The isomorphic binding technology used by RGB++ cleverly binds Bitcoin's UTXO with CKB's Cell, not only simplifying user verification operations but also maintaining high security. At the same time, the Leap operation provides users with broader application scenarios, opening new avenues for cross-chain interoperability.
As more and more applications choose to build on the foundation of RGB++, we have reason to believe that it will play an increasingly important role in the future Bitcoin ecosystem.