The introduction of Raiden Services, namely monitoring and pathfinding services, aims to enhance the overall user experience of the Raiden Network by
a) finding short or cheap routes through the network and
b) allowing users to go offline safely by watching open payment channels.
In this context, the Raiden Service Bundle (RSB) registry is planned to list all service providers, which are offering monitoring and/or pathfinding services.
This blog post gives an update on the first set of Raiden Service implementations, elaborates on the envisaged design and function of the RSB Registry and explains how the Raiden Services will interact with the RSB Registry.
Development update on the Raiden Services
Monitoring Service (MS)
Monitoring services can watch open payment channels when the user is not online. In case one channel partner closes a channel while the counterparty is offline (or doesn’t react for 80% of the settlement timeout after close has been called), the monitoring service sends the latest balance proof to the channel smart contract and thus ensures correct settlement of the channel.
How does the first implementation of an MS work step-by-step?
- Whenever Alice wants to have one of her channels monitored, Alice deposits RDN tokens to the UserDeposit contract.
- She then starts sending balance proofs (including the token network, channel ID, nonce and hashed balance value, as well as reward for the monitoring service) to a public chat room, where the MS can read them.
- Updates should be sent to the MS whenever the state of the channel changes, while the sent balance proof does not expose the actual balance values, as it is hashed.
- The MS picks up the messages and listens to on-chain events regarding this particular channel. The MS can choose to only pick up requests above a certain minimum reward.
- Whenever the channel is closed, the MS gives the channel participants ...
To keep reading, please go to the original article at:
Stories by Raiden Network on Medium