Vernacular interpretation of the RGB++ protocol and the latest progress in the ecosystem

Original Author: DaPangDun (X:@DaPangDunCrypto)

Editor’s note: Encryption researcher DaPangDun published an article on X to sort out the key points about the RGB++ protocol and ecology to help users better understand the latest progress of the RGB++ protocol and ecology. Odaily is compiled as follows:

FAQ: protocol aspects

1. What is isomorphic binding?

A: Isomorphic binding provides a native way to map layer 1 assets on BTC (currently limited to RGB++ assets) to layer 2 (currently limited to ckb) network, which is not achieved through bridges, so that assets “layer 1-2 transfer” to enjoy layer 1 security and layer 2 scalability.

2. After Leap, how are the assets of Layer 1 locked?

Answer: The assets on the first floor are not locked, after Leap, the assets are on the second floor, not on the first floor, and only when Leap goes back, the assets are rebound. We can compare binding to the “dyeing” of dyed coins, where Leap to the second layer corresponds to “decolorization” and Leap back to the first layer corresponds to “re-dyeing”.

3. What happens when RGB++ assets are transferred at the first layer?

Answer: When RGB++ assets are created in Layer 1, Layer 2 is isomorphic to a shadow asset, and when Layer 1 is transferred, the shadow assets will be transferred in the same structure, and the assets in Layer 2 can only be operated when the user leaps to Layer 2.

4. Why is the Tier 1 asset GAS consumption so high?

A: In fact, the reason for the high consumption of Layer 1 assets is not entirely due to GAS. Consumption of first-layer assets = GAS + CKB fees occupied by layer-2 homogeneous CELL + others.

Among them: GAS is the network fees for user participation, except for Mint, which is generally not very high. The occupancy cost of CKB may be a large head, for example, a CELL occupies 144 ckb, according to the price of 0.025 is 3.6 U, if it occupies 300 ckb is 7.5 U. Others refer to the service fees of some platforms, etc.

5. What are the advantages of the RGB++ protocol over other inscription protocols?

A: long people don’t have a proper understanding of RGB++ protocol and look at the protocol in terms of current consumption.

Inscription class protocol you can only operate on the mainnet all the time, so its scalability is very limited, and the continuous consumption is very large;

The RGB++ protocol is only expensive when you have been playing on the mainnet, but its core is that you can leap to layer 2 and play on ckb, at this time the gas is basically negligible, its scalability is only limited by the ckb network, and the continuous consumption is only in the two processes of leap in and leap out.

6. Why don’t you play on the second floor now, or on the first floor?

A: Because the infra on the second floor is very weak now, there is already a market on the first floor, there is more than one, and the second layer is not yet, then you can only play “transfer” on the second floor, which is why I suggest that the CKB project party and the community should develop infra as soon as possible; of course, here I am looking forward to developing infra based on smart contracts capabilities, such as if it is just imitating the P2P of the first layer Market, I don’t think it’s attractive enough, and it doesn’t reflect the superiority, but it would be interesting to develop an AMM/DEX based on the cell model.

7. Why is the distribution method centralized?

Answer: It is completely possible to distribute without using a centralized way, but this requires users to build this layer 2 mapping process by themselves, including splicing transactions, issuing and broadcasting transactions, and also need to prepare CKB to complete such operations, which is basically impossible for ordinary people, so the launch platform handles such a process in the background. However, I understand that there are people in the specific script community doing it, and Decentralization distribution will be realized in the future, and it will be easier if it is a layer 2 distribution.

The reason can be referred to this post: cryptowizard/status/1780112123567428060 …

8. What is the development idea of the protocol?

A: My personal guess is that the Cipher team is mainly responsible for maintaining the operation, improvement and updating of the protocol, while the community or other teams develop their own infra projects based on the RGB++ protocol, on the one hand, it is to let more long devs in, and on the other hand, they can quickly promote the development of the ecosystem long the line. Dev comes in because their project is likely to succeed in this ecosystem, and if they are bullish on this ecosystem, the success of the place represents a possible “success” in the future.

From the perspective of development, it should be the first and second floors go hand in hand, that is, the first and second floors of the ecological project should be done, the first layer is the first step, and the second layer is the second step (the logical relationship in this is not necessary, but it is easier to understand), so that the first and second layers of INFRA will be gradually improved in this process.

FAQ: Ecological aspects

1. Why Does It Take That Long After Huehub Is Deployed To Mint?

Answer: The problem of the protocol mechanism, after the protocol is deployed, it requires 6 blocks of security confirmation, so it takes time to wait.

2. Why doesn’t Huehub review asset issuance?

A: I think it’s a matter of choice. ++ is a Open Source protocol, anyone can make a launch pad based on the protocol, Huehub’s positioning may be to provide such a functional module as an infra under the ecosystem, so there is no audit requirement; at the same time, the audit also represents a responsibility issue to a certain extent, this piece may not be willing to touch for the time being, after all, the platform has no ability to guarantee anything. Of course, I can understand that people don’t want to have assets that are too long and have no wealth effect, but we may need to think about this from the perspective and positioning of Huehub.

3. What are the precautions for participating in Huehub with unisat/okx Wallet?

Answer: In fact, the official recommendation has been specifically introduced, and the following points can be summarized.

• Try to use a new Wallet to prevent other assets in the Wallet from being burned
• Currently supports mint, Maker, cancel Maker, buy and sell, and do not support transfer
• Do not transfer all BTC assets within the Wallet individually

4. What are the current infras in the ecosystem?

For:

• Trading platform - Huehub, there are a few other platforms that I haven’t researched in depth
• Asset Manager – Haste, which manages RGB++ assets within different Wallets
• Wallet – Joyid Wallet Neuron Wallet
• Domain Name System ——.bit (ready to access++)
• DOBS market - the joyid Wallet has a built-in unicorn market, but I understand that there are teams doing DOBS market (DOBS, simply understood as the concept of NFT, of course, there is actually an extension)
• Inscription platform – Omiga

5. What assets are worth investing in in the ecosystem?

A: I am personally not very good at investment, I have always emphasized that my secondary ability is quite weak, so I will generally look for very early opportunities with a certain degree of certainty and participate in them, about the specific target and investment you can refer to longing

@0x CryptoWizard’s tweet

Finally, a few words about my personal thoughts:

For new protocols, there will always be problems of one kind or another, especially when the early superimposed INFRA is relatively weak, so I hope that everyone will try to be “tolerant”, have problems and feedback problems, and be less angry; In fact, the development speed of these teams is already very fast, and the development based on the UTXO model is difficult, and the attitude of the teams that I have encountered so far is not bad. Of course, from the perspective of ordinary users, I hope that these teams can have a bigger picture and work together with users to achieve a win-win situation.