This week, the RGB protocol, which allows to issue tokens and smart contracts on Bitcoin through the Lightning Network, had several important launches demonstrating the enormous progress that this interesting project has achieved.
On Monday, March 15, the first version of Bitcoin Pro was launched, a tool to issue tokens in the RGB protocol. On the other hand, last Thursday, March 18, the explorer of this protocol was also launched, called RGBex .
Both tools were presented by the Dr. Maxim Orlovsky , main developer of this protocol proposed 3 years ago by the developer Giacomo Zucco.
As you can read in his code repository. , Bitcoin Pro is an «account manager and smart contracts», an application that, they clarify, «is not a wallet«, as it does not need to access private keys nor does it create no type of signature.
What Bitcoin Pro does is the creation and export of Partially Signed Bitcoin Transactions ( PSBT , in English) , so these must be published on the main Bitcoin network, its blockchain, outside the application.
Although the application can be used for several purposes, its main use case would be the management of RGB-20 tokens, the native tabs of this protocol. In this sense, can be created, issued, renamed, burned and replaced fungible tokens of this standard.
At the moment, It is not yet possible to issue non-fungible tokens (NFT), but it is a feature that is planned to be implemented, as read. Notably, Bitcoin Pro v. 0.1 is the first version of this software, so its developers advise to use it at your own risk, preferably on the testnet or testnet of Bitcoin.
RGBex, the RGB protocol browser
RGBex is not a block explorer, does not browse the Bitcoin blockchain. RGBex is an index or list of fungible and non-fungible assets (NFT) that are broadcast in the RGB protocol. On the other hand, in Bitcoin Pro it is planned to integrate a block explorer as the most conventional ones.
Anyone can upload the genesis of an RGB-20 (fungible) and RGB-21 (non-fungible) token using a SECP256k1 Bitcoin key. It can be optionally signed and loaded with metadata, such as the issuer’s name and their website. The asset could then be unlisted by the creator using a signature generated from the same key created to list the token.