The statement 'RGB assets are distributed from the main network' is incorrect The statement 'RGB assets are distributed from the main network' is incorrect The statement 'RGB assets are distributed from the main network' is incorrect RGB assets will never be "distributed" from the main network or even the future Lightning Network from start to finish!!!! The RGB protocol is an open-source P2P (peer-to-peer) "plugin" protocol with the concept of offchain programmability, aimed at helping BTC fulfill the properties of smart contracts ⬇️⬇️⬇️ The transfer process for RGB assets is as follows: the receiver gives the sender a "payment code" ->the sender sends money ->the BTC mainnet on the voucher ->the receiver "scans the chain" and receives the voucher ->the off chain asset is transferred to the other party ->a "receipt" is given on the chain ->the transaction is completed ok， This is the most basic process for transferring RGB assets, and there is a question here. As a P2P protocol, can ordinary users have the ability to manage their RGB assets themselves? What if they lose them? This is the function of RGB wallet, there are two factions here 1. Centralized hosting representative: bihelix 2. Try decentralized asset custody (using sharded storage) with bitmast/bitlight Firstly, let's talk about the benefits of centralized custody. If we use Nodes as the form of asset custody storage, we can quickly connect to third-party wallet institutions, so you can see that Bihelix can access TP wallets or more wallets. I am not opposed to centralized custody, which is an inevitable choice for expanding commercial applications Essentially, RGB assets are a row of data 📊， So, if there is a potential risk of asset loss in my custody, why don't I put all this data on the chain? This is something similar to what @ BitMask-App @ Bitlightw_wallet is considering This is the second faction, which attempts to decentralize the custody of user assets. The disadvantage is that it is not easy to collaborate with other wallets (although they may also have better technical solutions) If my understanding of Bitlight is correct, in the process of testing assets this time, it is not the so-called "RGB asset distribution" that occurs through the main chain, but rather a "receipt" that determines the status. For specific details, please refer to the RGB asset transfer process I wrote above This is not an asset, but it is certain that you do not have any rights to the asset In other words, what was distributed to me through the main chain is something like a 'vault security key' And this' safe key to the vault 'is the asset that Bitlight stores data in the distributed storage vault as' mine' Understood, welcome to discuss and exchange ideas