If you want a simple explanation of #RGB to share with your friends, I've put one together. Feedback appreciated.
--
RGB is a generalized smart contract system built on #Bitcoin and #Lightning.
It's scalable and private because it keeps contracts off the blockchain, and the parts of a contract that can change are anchored to a little piece of a bitcoin called an Unspent Transaction Output (UTXO).
When this piece of a coin is spent, it can never be spent in the same way again, so we know, that part of the contract has changed. This is similar to a tamper-evident single use seal, like a bag with a zipper that can only be zipped once.
Even better, only the person who owns the bag with a single use seal can zip it. And like a bag, it can contain multiple items.
Multiple tokens can be anchored to a single UTXO, and when they're spent, the ones you're not spending are sent back to yourself, to another UTXO you own.
Because contract data is kept off-chain, decentralized storage protocols like Storm and Carbonado are used to keep and communicate contracts reliably.
This is then used by wallets to do things like mint, transfer, accept, and verify on token contracts. There's not really a need for an RGB node, even in web browsers, since the code needed to validate contracts can be built to run in browsers.
This is what is meant when we say client-side validation (CSV); only the wallet needs to know about the contracts, and only peers that interact with each other need to know the contract data.
This allows for privacy and scale in a number of ways:
- Contracts are not put on-chain
- Contracts are not executed on nodes
- Multiple contracts can anchor to a single UTXO
- The UTXOs are very small and look like ordinary Taproot payments
If you request a payment from someone, nobody can see what other tokens you have, even if they have the contract. This is because a really big number is added to the UTXO to make a blinded payment.
Nobody can know which UTXOs have tokens by scanning the chain on an explorer, and there's no way to send someone tokens if they don't request and accept them.
--
I hope this is a good start towards understanding RGB! A great way to understand it even better is to actually try it out on any of these wallets:
https://mycitadel.io
https://iriswallet.com (not to be confused with iris.to, or IRS wallet)
https://beta.bitmask.app
HunterBeast / Hunter ₿eaṩt
npub1qq…clxwk
2023-06-12 19:02:47 UTC
Author Public Key
npub1qqqqqqqrxtrcx8vut2vlrqa0c2qn5mmf59hdmflkls8dsyg9vmnqsclxwkPublished at
2023-06-12 19:02:47 UTCEvent JSON
{
"id": "0000000d63f55c97f2d1498dae8049794387d32a170d65e15a76c0b89f6836d9",
"pubkey": "000000000332c7831d9c5a99f183afc2813a6f69a16edda7f6fc0ed8110566e6",
"created_at": 1686596567,
"kind": 1,
"tags": [
[
"client",
"gossip"
],
[
"nonce",
"15564440312194884401",
"24"
]
],
"content": "If you want a simple explanation of #RGB to share with your friends, I've put one together. Feedback appreciated.\n--\nRGB is a generalized smart contract system built on #Bitcoin and #Lightning.\n\nIt's scalable and private because it keeps contracts off the blockchain, and the parts of a contract that can change are anchored to a little piece of a bitcoin called an Unspent Transaction Output (UTXO).\n\nWhen this piece of a coin is spent, it can never be spent in the same way again, so we know, that part of the contract has changed. This is similar to a tamper-evident single use seal, like a bag with a zipper that can only be zipped once.\n\nEven better, only the person who owns the bag with a single use seal can zip it. And like a bag, it can contain multiple items.\n\nMultiple tokens can be anchored to a single UTXO, and when they're spent, the ones you're not spending are sent back to yourself, to another UTXO you own.\n\nBecause contract data is kept off-chain, decentralized storage protocols like Storm and Carbonado are used to keep and communicate contracts reliably.\n\nThis is then used by wallets to do things like mint, transfer, accept, and verify on token contracts. There's not really a need for an RGB node, even in web browsers, since the code needed to validate contracts can be built to run in browsers.\n\nThis is what is meant when we say client-side validation (CSV); only the wallet needs to know about the contracts, and only peers that interact with each other need to know the contract data.\n\nThis allows for privacy and scale in a number of ways:\n- Contracts are not put on-chain\n- Contracts are not executed on nodes\n- Multiple contracts can anchor to a single UTXO\n- The UTXOs are very small and look like ordinary Taproot payments\n\nIf you request a payment from someone, nobody can see what other tokens you have, even if they have the contract. This is because a really big number is added to the UTXO to make a blinded payment.\n\nNobody can know which UTXOs have tokens by scanning the chain on an explorer, and there's no way to send someone tokens if they don't request and accept them.\n--\nI hope this is a good start towards understanding RGB! A great way to understand it even better is to actually try it out on any of these wallets:\n\nhttps://mycitadel.io\nhttps://iriswallet.com (not to be confused with iris.to, or IRS wallet)\nhttps://beta.bitmask.app",
"sig": "ead23bab30c9464d57b71ae66ace953d6fd138f42bc69a4b38cba2fabb6966ae075158a7c8a0b973ae2580ff98af17cfeb9d2fc8238995111d7c2169bc64ceb8"
}