The RGB article was a part of the notes I wrote at the time, which I used to organize myself What is RGB? 1. The smart contract framework is used to manage rich states 2. CSV client verification, you hold assets and have the right, not other users 3. Utilize BTC/Lighting TXN graph without using blockchain (not a chain, BTC's UTXO ledger is his "chain") 2. Benefits of RGB 1. No need for software upgrade 2. Do not return to congestion 3. Privacy 3. RGB proposals 1. No on chain monitoring 2. Data/Quantity All Privacy 3. Partial revision (only partial will be revealed) If the holder doesn't tell you, you won't know anything (even on LN/Bitcoin) and won't see any data like TXN If an issur issues two tokens, they will never know each other But what if you want two tokens to be exchanged—— Specturm protocol does not belong to the RGB framework What can RGB do? 1. Token/DU 2. Options and contracts 3. Anonymous fundraising, collection, centralization, government issued assets 4. Voting, decentralized identity, key management RGB is a set of standards Strict encoding is used to standardize the data consensus mechanism Single use seals: It is an encrypted promise Cryptocurrency commitment: commit state data(ownership strutcture) into a TXN RGB is the paradigms applied to Bitcoin Multi contract commitments (used for sharding and contract modularization) stach：all the data related Client validation hold by specific party RGB Schema (Script It seems like this translation shouldn't be done Define standards schea (define schema) RGB & Bitcoin Multidimensional relations How to understand deterministic commitment and single use of seal Assuming you have multiple RGB assets linked in different UTXO outputs and want to transfer them, without a deterministic commitment, your assets will be transferred together But if you have a deterministic commitment, you can define a transfer anchors： Linking UTXO and removing some seals is different from state transition Stash： Contract/Data History. Usually, the wallet is kept in custody. If this stash is lost, all RGB assets will be lost Transferring does not require using a stash, and sending a state transition during the transfer is not enough. The other party needs all of your history. At this point, you need to separate some historical data (mostly hidden, such as quantity and balance) from your stash These partial data are placed in the consideration and then sent to the other party. The other party uses encryption rules to verify a portion of your data, but does not need all of your data. Therefore, they will keep your stash data in their copy