Client to client communications

To complete an RGB transfer, the involved parties must exchange certain data. Specifically, the sender is required to provide the recipient(s) with the consignment, a data structure that encompasses all the necessary details to validate the transfer. This includes the entire history of prior state transitions leading back to the genesis contract.

RGB is indifferent to the method of communication used for sharing this data, allowing for a variety of approaches. At present, there are two primary methods for data sharing in RGB:

  • Storm: This is a peer-to-peer messaging and storage system that operates on the Lightning Network.

  • RGB Proxy Server: This is a standardized HTTP JSON-RPC server where clients can upload and download data. Users have the option to operate their own proxy server or use a third-party server. While using a third-party server may raise concerns regarding privacy and censorship, it does not pose security risks.

The decision regarding which communication channel to use is facilitated through an invoice protocol. In this protocol, the receiver specifies one or more endpoints to which the sender can upload the consignment data.

In the future, the XRGB Wallet will facilitate the sharing of consignment data between the sender and recipient by supporting decentralized communication protocols.

Last updated