Original Title: "Leading the Mass Adoption of Crypto: RGB Protocol Lights up the Future of Bitcoin"
Original Authors: Bill, Waterdrip Capital; Marvin & Neo, Infinitas
About 4.5 billion years ago, the Earth was formed.
About 3.5 billion years ago, single-celled organisms began to wriggle.
About 300,000 years ago, Homo sapiens, as modern humans, began to appear.
About 150 years ago, the underlying code of modern computers began to operate rapidly.
About 14 years ago, the first block of the Bitcoin blockchain, known as the "Genesis Block", was created, marking the beginning of the entire Bitcoin network.
A few months ago, GPT 4.0 was released, and at the same time, many core technologies behind Bitcoin collectively made substantial breakthroughs.
At this moment, as you read these words, you may be curious and confused about RGB.
……
In the world of cryptocurrency, Bitcoin is undoubtedly the most well-known existence. However, when people talk about Bitcoin, they often only focus on its price, market value, and trading volume, but ignore the technological innovation and application potential behind it. Many core technologies mentioned in our "DeFi Research on Bitcoin Lightning Network" released last year have made substantial breakthroughs in the first half of this year, such as:
Lightning Labs has launched the Taproot Assets v0.2 (formerly known as Taro) testnet;
OmniBOLT has launched its Mainnet and enabled the sending, receiving, and transferring of USDT via the Lightning Network.
RGB protocol has released a more powerful, flexible, and secure version of RGB v0.10.
……
Speaking of the RGB protocol, people may be both familiar and unfamiliar with it. The familiarity comes from the concept of RGB being proposed as early as 2016, and many people know of the existence of the RGB protocol. However, after several years of development, it has not received widespread attention and application, and people seem to be unable to find specific use cases for the RGB protocol.
After conducting research and analysis, we believe that the main reason for this phenomenon is that in the early versions of the RGB protocol, its functionality was relatively limited. Additionally, the RGB protocol's ideas are highly original and unique, and the technology stack is quite extensive. Developers need to have a deep understanding of the principles of Bitcoin and smart contracts before they can easily use it. However, as the RGB protocol continues to evolve and improve, this situation is changing.
RGB is a scalable and confidential Bitcoin and Lightning Network smart contract system developed by the LNP/BP Standards Association. It adopts the concept of private and co-ownership and is a Turing-complete, trustless distributed computing form that does not require the introduction of non-blockchain decentralized protocols with tokens.
The design purpose of RGB is to run scalable, robust, and private smart contracts on UTXO blockchains (such as Bitcoin) to achieve all possibilities. With RGB, developers can execute complex multi-category smart contracts such as token issuance, NFT minting, DeFi, DAO, and more.
The RGB protocol is based on the concepts of client-side validation and single-use seals proposed by Peter Todd in 2016. It is a client-side state validation and smart contract system that operates on the second and third layers (off-chain) of the Bitcoin ecosystem. (Below is a brief introduction to these two concepts. Interested readers can refer to Peter Todd's original paper: https://petertodd.org/2017/scalable-single-use-seal-asset-transfer)
客户端验证(client-side validation):
Client-side validation refers to the process of validating user input on the client side, typically using JavaScript or other scripting languages. This type of validation is performed before the data is sent to the server, and is used to ensure that the data is in the correct format and meets any other requirements specified by the application. Client-side validation can help to improve the user experience by providing immediate feedback to the user when input errors are detected.
Client-side validation is a paradigm proposed by Peter Todd in 2016. The core idea is that in a distributed system, state validation does not require all parties participating in the decentralized protocol to execute globally. Instead, only the parties involved in specific state transitions need to be validated. By adopting this approach, state transitions are not published to the global network, but are transformed into a short cryptographic commitment through the use of cryptographic hash functions, which needs to be part of some form of "Proof-of-Publication" medium and has three main features: receipt proof, non-publication proof, and membership proof. The first client-side validation system is the OpenTimeStamps protocol, also proposed and developed by Peter Todd between 2014 and 2016.
Single-use-seals:
Can be analogized to a one-time seal used in the real world to protect cargo containers. The primitive of one-time sealing is a unique object that can only be used once to package a message, ensuring that this message can only be used once and once used, it is permanently opened and cannot be closed again. In short, one-time sealing is an abstract mechanism used to prevent double spending.
RGB's initial concept can be traced back to 2016, when Giacomo Zucco (BHB Network) proposed it based on Peter Todd's early ideas about client validation and one-time sealing. It was implemented in the original MVP by BHB Network in 2017 and received support from Poseidon Group.
In 2019, Maxim Orlovsk and Giacomo Zucco jointly established the LNP/BP Standards Association (https://www.lnp-bp.org) to promote the RGB from concept to practical application. The association is supported by Fulgur Ventures, Bitfinex, Hojo Foundation, Pandora Prime, and DIBA.
(Maxim Orlovsk)
Starting from 2019, Dr. Maxim Orlovsky has been serving as the main designer and chief contributor of the RGB protocol in the encryption industry. He has designed and implemented the current form of the RGB protocol. Since 2019, RGB has been rethought and redesigned in terms of design and protocol peer review, becoming a universal computing and confidential smart contract system.
In 2021, the LNP/BP Standards Association successfully demonstrated that RGB has a Turing-complete virtual machine (AluVM) onboard, and RGB has also started running on the Lightning Network, using a Rust reimplementation of the complete Lightning protocol conducted by Dr. Maxim Orlovsky at the Association (LNP Node).
In 2022, the LNP/BP Standards Association launched a new website (contractum.org) dedicated to the Contractum language, a new high-level language designed for developing smart contracts using RGB technology on Bitcoin and Lightning Network. Contractum is a functional declarative programming language specifically designed for smart contract development on Bitcoin and Lightning Network using RGB technology.
This year, in April 2023, the LNP/BP Association announced the release of RGB v0.10, which is another important milestone in the development of the RGB protocol, bringing full support for smart contracts to Bitcoin and the Lightning Network. This is the result of long-term cross-industry collaboration among these Bitcoin developers, contributors, and related companies, as well as more than four years of extensive development work. (RGB v0.10 can be downloaded and installed at https://rgb.tech, which also contains many user and developer guides. The RGB source code can be found at https://github.com/RGB-WG.)
For many years, some projects and teams have been researching protocols for issuing tokens on Bitcoin and trying to break through to make them compatible with the Lightning Network. Representatives include OmniBOLT, Taproot, and RGB.
The protocol we are familiar with that issues tokens on Bitcoin, such as OmniLayer, works by inserting metadata into Bitcoin transactions to "color" them and indicate that the transaction should be understood as a token transfer. USDT (Tether) in the Omni protocol can be seen as a form of colored coin. In the Omni protocol, USDT exists in the form of Tether tokens, which are represented by using a specific transaction type in the Bitcoin transaction on the Omni protocol. Specifically, when a user initiates a USDT transaction on the Omni protocol, they add a special data field from OmniLayer to the Bitcoin transaction to indicate that the transaction involves the transfer of USDT tokens. This allows Bitcoin transactions to represent the transfer of USDT tokens, and USDT holders can use Bitcoin addresses to receive, send, and store USDT tokens.
Such signaling mechanisms are usually implemented using the OP_RETURN opcode. Outputs with this opcode are ignored by regular Bitcoin nodes, but can be interpreted by nodes that are able to perceive these token protocols. These nodes will enforce the validation rules of the token protocol.
Although this design is very efficient, it also has certain limitations:
1) The amount of information related to token transfers is limited to the number of bytes that can be accommodated in the OP_RETURN output, which is generally 80 bytes. This space is sufficient for encoding ordinary transaction data, but more complex use cases may not be satisfied.
2) Token protocol nodes need to scan the entire blockchain and search for token transfers that may be related to users in the OP_RETURN output. The entire process will consume more resources due to the growth of the Bitcoin blockchain volume.
3) In terms of user privacy, all transaction data is visible to everyone.
With the aim of optimizing this design, the RGB protocol has proposed a more scalable, more private, and more future-oriented solution. Its cornerstone is the concept of client-side validation and single-use seals, which was proposed by Peter Todd in 2016.
The core concept of the RGB protocol is to only call the Bitcoin blockchain when necessary, using proof of work and network decentralization to achieve double-spending protection and censorship resistance. All token transfer validation work is removed from the global consensus layer and placed off-chain, only to be verified by the client of the receiving payment party.
Working principle:
In a certain RGB contract, the genesis tokens belong to a Bitcoin UTXO (whether it already exists or is temporarily created), and to transfer the tokens, you need to spend this UTXO. When spending this UTXO, an additional output must be added to the Bitcoin transaction, which includes a commitment to a message. The content of this message is the payment information of RGB, which defines the inputs, where these tokens will be sent to, the asset ID, quantity, the transaction spent, and other additional data.
If you have tokens belonging to the #1 output of a Bitcoin transaction A, to transfer these tokens you need to create an RGB transaction and a Bitcoin transaction spending the #1 output of transaction A, with the Bitcoin transaction committing to the RGB transaction. As you can see, the RGB transaction transfers the tokens from the #1 output of Bitcoin transaction A to the #2 output of Bitcoin transaction C (not shown in the diagram), rather than transferring them to Bitcoin transaction B. In most cases, we can expect the #0 output of transaction B to be the change address, in order to send the remaining funds back to the original owner after deducting the miner's fee; while the #1 output is to commit to the RGB transaction to avoid double spending.
Privacy Protection:
In order to transfer ownership of RGB tokens associated with a Bitcoin transaction, a Bitcoin transaction must be initiated. However, the output of the RGB transfer does not need to match the output of the Bitcoin transaction. Just like in the example above, the output of the RGB transaction (Bitcoin transaction C #2 output) can be unrelated to the Bitcoin transaction (transaction B) that commits to the RGB transaction. This means that RGB tokens can be "sent" from one UTXO to another without leaving any trace in the Bitcoin transaction graph, greatly enhancing privacy.
In this design, the role of Bitcoin's UTXO is to serve as a one-time container for loading RGB assets. To transfer assets, you only need to open a new container and close the old one.
The specific payment information of the RGB token is transmitted off-chain through a dedicated communication channel, from the payer's client to the receiver's client, and verified by the latter to ensure compliance with the rules of the RGB protocol. As a result, blockchain observers will not be able to obtain any information about RGB user activity.
Verification Loop:
However, verifying the payment information sent is not enough to ensure that the sender truly owns the assets they want to send to you. Therefore, in order to ensure the finality of the transaction, you must also receive all transaction history about these tokens from the payer, from the current transaction all the way back to the initial issuance. Once all transaction history has been verified, you can ensure that the assets have not been inflated and that all spending conditions attached to the assets have been met.
This design is also beneficial for scalability, as you do not need to validate the entire history of this asset, only the part that is relevant to you. Additionally, the design does not broadcast transactions to the global ledger, which enhances privacy as fewer people are aware of the existence of your transactions.
Blinding secret value:
In order to further enhance privacy, RGB also supports blinding of outputs, which means that when you send a payment request to the payer, you do not need to publicly disclose the UTXO used to receive the tokens. Instead, you only need to ask the payer to send the tokens to a hash value, which is generated by concatenating the target UTXO with a randomly blinded secret value. In this way, the payer cannot know which UTXO the tokens will be sent to, so exchanges and other service providers cannot know whether users are withdrawing to UTXOs on some regulatory "blacklist", nor can they know how these tokens will be spent in the future. It should be noted that when the tokens are spent, the blinding secret value must be disclosed to the recipient so that the latter can verify the part of the transaction history related to Bitcoin transactions. This means that when using RGB, you have complete privacy at present, but future token holders will be able to see all UTXOs in the transfer history of the tokens in their possession. Therefore, although you can obtain perfect privacy when receiving and holding RGB tokens, the confidentiality of users' past financial activities will be gradually downgraded as the tokens are continuously transferred, ultimately tending towards the same privacy level as our Bitcoin transaction history.
Through the understanding of the above content, we can summarize that RGB has the following main characteristics:
1. High confidentiality, security, and scalability.
2. There is no congestion in the Bitcoin time chain because transactions only retain homomorphic commitments that require additional storage.
3. Can be upgraded in the future without the need for a hard fork.
4. Has higher resistance to censorship than Bitcoin: Miners cannot see the flow of assets in transactions.
5. There is no concept of blocks and chains.
It is worth noting that when we mention blockchain, it generally involves the concepts of blocks and chains. However, in RGB, there are no concepts of blocks and chains because it is a client-side validation technology and a non-block decentralized protocol.
RGB v0.10 marks a major breakthrough for the encryption industry, pushing RGB into the system stage that is about to be put into commercial use. It introduces the last change that breaks consensus, aiming to maintain full backward compatibility for future versions of RGB. In addition, it also unlocks the last batch of features for implementing fully functional smart contracts, which can be customized by contract developers at will.
The release of RGB v0.10 includes the consensus layer, standard library (used for wallet/exchange integration, etc.), and command line tools. The table below summarizes the main differences between the new and old versions based on official RGB materials. Readers who want to learn more detailed information can refer to the official RGB documentation and video introductions:
https://rgb.tech/blog/release-v0-10/ https://www.youtube.com/@LNPBP/videos
Overall, version 0.10 of the RGB protocol has addressed many issues present in previous versions, including limitations in smart contract development, consensus layer accessibility, encoding format restrictions, dependency issues with Rust Bitcoin, lack of WASM compatibility, global state and context management issues, integration with Lightning Network, inflexibility in backup processes, and inadequate support for mobile wallets. These improvements make the RGB protocol more powerful, flexible, and secure, and lay a solid foundation for future development. Specifically, RGB version 0.10 introduces the following feature support for RGB:
Global State in RGB Contracts
RGB has introduced the concept of Global State, which is a brand new feature that is very important for building complex applications on RGB (such as synthetic assets, algorithmic stablecoins, etc.). Now, each RGB contract has a global state that can be accessed by virtual machines and clients (such as wallets).
Contract Interface
The interface introduced in this version represents a standardized way of passing various smart contracts through a clearly defined API. The interfaces can be compared to the contract ABI and ERC in the Ethereum world, but unlike Ethereum, they do not require mandatory standardization (such as ERC) or separate distribution, but are always packaged with the contract. By using interfaces, wallets and other software can provide users with a semantically aware user interface for handling contracts - contract developers can also add more interfaces to their existing contracts over time without updating the immutable contracts themselves.
The basic components of RGB smart contracts: RGB smart contracts consist of three parts: Genesis, State, and Transitions. Genesis defines the basic properties and rules of the contract, State is the current state of the contract, and Transitions are the transitions between states. RGB v0.10 introduces a new smart contract model that is more flexible and powerful, and can support various complex application scenarios.
Strict type system
The new encoding format refers to the "strict types" system, which is a new functional data type system used for representing and introspecting RGB contract states. It allows for size guarantees of any data at compile time, simplifying RGB operations on low-end and limited memory devices such as hardware wallets. The entire RGB consensus layer is now compiled as strict types, which allows for formal proof of binary compatibility between releases.
In other words, this new encoding format will make the use of RGB simpler and more secure, while also allowing asset issuers and contract developers to use additional metadata to sign their assets or contracts. This will help to verify the identity of assets or contracts.
In Rust, writing contracts.
You can use Rust to write and compile RGB smart contracts. Thanks to the existence of strict types, Rust data types can now be directly compiled into RGB contracts.
State introspection.
The contract can introspect its own state in the verification code that can be used in the virtual machine, which opens up possibilities for writing complex contract forms that interact with Bitcoin transactions, DLC, and other complex data.
Based on URL invoice format.
Previously, invoices encoded in Bech32m were used for RGB. These invoices were very long, difficult to read, and most software could not be automatically opened. The new format is shorter, easier for users to verify, and can be automatically opened as a link for pre-configured software.
WASM Support
RGB standard library can run without I/O and file system access, which means it can run in web pages or browser plugins.
Tapret Descriptors and Custom Derivatives
The translation of the content is:
Simplified Dependency Relationship.
RGB consensus layer now has fewer dependencies, which improves the stability of the API. LNP/BP has abandoned the dependency on the custom bulletproofs implementation from the Grin project.
Simplified Integration.
Many operations that previously required multiple API calls and complex data structures across different languages can now be completed with a single API call. The RGB contract state is represented as a JSON object, which can be serialized between different languages without the need for cumbersome operations.
Streamlined user experience
Previously, when using RGB, wallets or users had to run RGB nodes and interact with the interface through RPC (or cli tools) - and use many other libraries and command line tools to perform most PSBT operations. In the new version, this complex stack is replaced by a single API library and the rgb command line tool.
As mentioned earlier, we believe that the main reason for the lack of widespread attention and application of RGB despite several years of development is due to various factors. However, after studying the RGB v0.10 version, we have reason to believe that this phenomenon is about to change, and may even be changing as we speak.
Before version RGB v0.10, independent developers faced some challenges when developing complex smart contracts. This was mainly due to the following reasons:
1) Protocol instability: In early versions, the RGB protocol may undergo significant changes, which may cause smart contracts that have already been developed to fail to run on the new version of the protocol. This instability may hinder developers from complex smart contract development.
3) Complexity of the protocol: The design and implementation of the RGB protocol may be quite complex, which could pose a challenge for independent developers. For example, the RGB protocol uses a novel validation mechanism called "client-side validation", which may require developers to have a deep understanding and expertise to undertake complex smart contract development.
However, with the development of the RGB protocol, these issues are being addressed. For example, a new type system called "strict types" was introduced in version 0.10 of RGB, which can help developers more easily develop complex smart contracts. In addition, this version also provides more tools and resources to help developers understand and use the RGB protocol.
And now, with the release of version 0.10 of RGB, the LNP/BP Association has announced its future focus, which is to complete support for Lightning Network in the coming months, allowing RGB assets to be transferred via Lightning Network.
If Lightning Network compatibility and support are achieved, it can improve the liquidity and availability of RGB assets. Through Lightning Network, users can transfer RGB assets quickly and cheaply without waiting for confirmation on the Bitcoin mainnet. This is very useful for users who need to frequently trade RGB assets.
More importantly, RGB may bring full support for smart contracts to the Lightning Network.
The Lightning Network has amazing speed, extremely low costs, and excellent security. However, because Bitcoin itself does not support complex smart contracts, the Lightning Network is somewhat limited in terms of smart contracts.
This unparalleled combination has the potential to make the Lightning Network shine as a bright star and leave other blockchains in the shade. With more and more funds and developers pouring into the development of Bitcoin's Lightning Network and RGB, there is hope that the ecosystem of Bitcoin and Lightning Network will reach new heights.
Liquid is a Bitcoin sidechain that offers some interesting features, such as native asset support and confidential transactions (which can hide the ID of transferred assets and the amount paid). However, the consortium model also has issues with low decentralization and weaker resistance to censorship.
The choice of OmniBOLT is very similar to RGB, but the difference is that these two protocols have different design goals. Compared with RGB, OmniBOLT is relatively weak in terms of privacy because, like Bitcoin, token-related data is stored on the chain. However, OmniBOLT has a unique advantage in stablecoin payment business and has been tested over time. In June of this year, the Mainnet has been launched and has implemented the function of sending and receiving USDT through the Lightning Network.
At the Bitcoin 2022 Miami conference, Taro was released. Taro is developed by the Lightning Labs team and aims to bring assets onto the Lightning Network. According to the released technical specifications, the entire design is very similar to RGB, with similar features and trade-offs.
The main difference between RGB and Taro seems to be:
1) RGB, which was announced earlier, has released auditable code, but lacks funding and operational personnel.
2) Taro is currently just a specification, but on the other hand, behind Taro is Lightning Labs, a team that raised $70 million in funding in April of last year and launched the Taproot Assets v0.2 (formerly known as Taro) testnet in May of this year.
If Taro and RGB can ultimately interact with each other, it is currently unclear whether there are incentives for this interoperability to occur.
Official website: https://www.iftas.tech/
Infinitas is one of the earliest projects to open up the Turing-complete smart contract track based on Bitcoin. As a Bitcoin application ecosystem network that integrates the RGB protocol and Lightning Network, it aims to achieve higher privacy protection, excellent throughput, and outstanding low-latency transaction processing. As an innovative blockchain solution, Infinitas has been solidifying the idea of Bitcoin Turing-complete smart contracts based on RGB since 2021, fully leveraging the security and consensus mechanism of Bitcoin, allowing for the creation of more complex applications and smart contracts on the Bitcoin network, and hoping to bring users an excellent trading experience. The project's technical core is led by a team of top-level blockchain scientists who are the builders of the underlying part of the Bitcoin code, and who were the earliest to focus on the RGB protocol and carry out related translation work. Infinitas will prioritize providing Online IDE, data browser, and access to mainstream wallets to allow developers and users to participate in the ecosystem, truly supporting the landing of large-scale commercial applications such as RWA and full-chain games.
Project features:
全网哈希算力保护: Inherits the high security of the Bitcoin blockchain, ensuring the protection of Infinitas assets in the Bitcoin blockchain with full network hash power, enhancing asset security.
Higher level privacy protection: Achieved higher level privacy protection for Infinitas assets and introduced a trustless Bitcoin anchoring mechanism to further enhance user privacy.
Adapter technology: Through Infinitas adapter technology, users can achieve a better understanding of the complete state of Bitcoin, enhancing their awareness of asset status.
Enriching Global State: By improving and expanding the Global State of RGB, access interfaces are provided for virtual machines and clients (such as wallets, etc.). Special emphasis is placed on trust in smart contract addresses, which crucially supports the construction of complex applications in the RGB ecosystem. This measure also enables different systems to understand and interpret each other's states, further promoting the development of the entire ecosystem.
Optimizing Lightning Network: By improving the Lightning Network with technologies such as light block technology, automatic node scaling, and offline autonomy, higher transaction throughput has been achieved while maintaining low latency transaction confirmation times.
Developer-friendly: Using the Rust language and Schema layer as the development infrastructure, even ordinary people can participate in development.
It is reported that Infinitas will have its native economy incentive plan, which will be initially produced through mining in the market to promote the long-term development of the ecosystem. As a leading project in the industry to build a Turing-complete Bitcoin application ecosystem, it may become a phenomenon-level ignition point for Bitcoin asset applications and a major leap forward in promoting the large-scale adoption of Crypto. The testnet is currently not online, but stay tuned for updates.
COSMINMART is a new Bitcoin application ecosystem based on lightning network, compatible with protocols such as RGB, and supports smart contracts.
COSM Wallet: COSMINMART's core product, has wide applicability in the entire Bitcoin ecosystem network. It now supports Bitcoin mainnet and Lightning Network transfers, RGB protocol asset transfers, and will gradually be compatible with ecosystems such as Stacks and Rootstock.
COSM Market: It is one of the earlier platforms that support the aggregation trading of Bitcoin derivative assets. It will gradually expand its support range to provide convenience for various Bitcoin derivative asset transactions.
COSM Lanuchpad: Aims to screen Bitcoin ecological projects with high potential and is committed to the sustainable development of the Bitcoin ecosystem.
COSMINMART is leading the definition of the Web4 concept, actively promoting the establishment of the RGB new protocol standard, issuing stablecoins on the Lightning Network, and combining the advantages of protocols such as Nostr and Lightning Network trading to deeply integrate traditional apps with the Lightning Network. They hope to lead the new era of Lightning Applications.
It is reported that COSMINMART plans to launch its beta product by the end of this year. Please stay tuned for updates.
https://pandoraprime.ch/
Pandora Prime is a Swiss company headquartered in Verify Valley, Nastael State, and is also a founding member of LNP/BP.
Pandora Prime is committed to pioneering Bitcoin Finance using the combination of RGB smart contracts and the Lightning Network. They start with programmable assets on Bitcoin (RGBTC and CHFN), which can be scaled to VISA/MasterCard levels in terms of transaction throughput through the Lightning Network. In addition, they provide convenient facilities for exchanging these assets, allowing transactions of up to 1,000 Swiss francs without the need for cumbersome KYC procedures (in compliance with Swiss law). Currently, their products include MyCitadel (wallet), RGB Explorer (browser), and Pandora Network, among others.
MyCitadel
MyCitadel is a brand of Pandora Prime. MyCitadel is the first graphical user interface wallet that supports RGB, created by RGB developers in 2021. It provides cross-platform desktop wallets and iOS/iPad wallets. The mobile wallet can handle fungible RGB assets.
RGB Explorer
https://rgbex.io/
RGB Explorer is the first browser developed by Pandora Prime that provides RGB asset registration and smart contracts. Currently, it supports RGB20, RGB21, and RGB25, and can display four types of assets: LNPBP, RGBTC, dCHF, and RGBEX.
DIBA(DIGIT ALBITCOIN ART)
https://diba.io/
DIBA is committed to enhancing the development of the community by helping people understand, own, and use non-custodial digital assets built on top of Bitcoin. It aims to shape the digital art and asset economy with decentralized and inclusive empowerment principles.
DIBA is the first market to trade Bitcoin NFTs using the RGB smart contract protocol and Lightning Network (referred to as DIBA). Currently, DIBA BETA is running on the Bitcoin testnet and will soon be launched on the Bitcoin mainnet. Stay tuned for updates.
Bitmask
This wallet was created by DIBA and is the first NFT wallet in the RGB ecosystem. It can run in a web browser and interact with RGB contracts, similar to MetaMask on Ethereum.
https://play.google.com/store/apps/details?id=com.iriswallet.testnet&pli=1
IRIS Waller is the first Android wallet developed by the Bitfinex team, dedicated to RGB integration and RGB-related tools. It supports both fungible and non-fungible assets. Iris Wallet supports RGB asset operations from issuance to spending and receiving, wrapping all functions in a familiar wallet application and abstracting technical details as much as possible. Currently, this is an experimental application and it is recommended to only use it for small amounts of Bitcoin and low-value assets.
https://github.com/BitSwap-BiFi/Bitswap-core
Currently, the RGB ecosystem is actively exploring DEX solutions to address the liquidity issues of RGB assets. The demonstration and conceptual verification of Bitswap showed how to introduce "SWAPS" into DEX, but there is currently no AMM or LP. It is still in the verification stage and is very early, but it is also worth paying attention to.
The RGB protocol has gone through nearly 6 years of evolution since its inception. Although the protocol has not yet received widespread attention and application, historical experience tells us that people often overestimate the rapid popularity of new ideas while underestimating the disruptive impact and speed that these ideas may eventually be widely accepted. In fact, with the release of RGB protocol v0.10, we are standing at a new starting point, witnessing a future with unlimited possibilities, much like Bitcoin.
The new version of the RGB protocol introduces a series of important updates, which enable the RGB protocol to not only issue and transfer multiple assets on the Bitcoin network and Lightning network, but also have the ability to support more complex smart contracts. Although the RGB protocol is not yet fully compatible with the Lightning network, we believe that in the coming months, the LNP/BP Association and related development teams are expected to make more significant progress. With the expectation of the perfect integration of the RGB protocol and the Lightning network, this will be a manifestation of another important milestone for the RGB protocol and Bitcoin.
The new features and improvements brought by the RGB protocol, especially its full compatibility with the Lightning Network, have lit a beacon for the future of Bitcoin. These changes have opened the door to unknown territories, allowing us to see the infinite potential of Bitcoin. In this unknown territory, Bitcoin is no longer just a simple means of payment, but a powerful platform capable of carrying complex applications. The RGB protocol has become the cornerstone of building this platform, and may lead us towards a brand new Crypto world.
Note: References:
https://rgb.tech
https://rgbfaq.com
https://lnp-bp.org
https://twitter.com/lnp_bp
https://www.youtube.com/@LNPBP/videos
https://blueprint.rgb.network
https://www.youtube.com/watch?v=DtkTE6m0zio
https://petertodd.org/2017/scalable-single-use-seal-asset-transfer
https://medium.com/@FedericoTenga/understanding-rgb-protocol-7dc7819d3059
https://www.contractum.org/
Welcome to join the official BlockBeats community:
Telegram Subscription Group: https://t.me/theblockbeats
Telegram Discussion Group: https://t.me/BlockBeats_App
Official Twitter Account: https://twitter.com/BlockBeatsAsia