-
Notifications
You must be signed in to change notification settings - Fork 378
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Monitor Requests (blinded balance proofs) must be published into a global matrix room #3273
Comments
@palango anything to add? |
Tagging @ulope for the transport team to plan accordingly. |
related #1432 |
Additionally, for that issue to be finished, we would need the client to join the matrix room for Monitor Requests. We will be able to create the room next week, when #3291 is finished. Does that make sense to you? |
With #3374 and #3393 in review let's plan the next steps (client side) here. From my understanding the following steps are necessary.
@rakanalh @LefterisJP @konradkonrad @andrevmatos Does this make sense and did I forget anything? |
@palango I think that should be mostly it. I'd suggest adding a simple |
@andrevmatos Can you take care of that? |
@palango Yes, I'll add the method and make a PR, and you can take from there to finish the PR with the handler bits |
Matrix functions and methods ready and merged. You can now use |
Closing issue as #3452 was done. Follow up issues will be created if needed. |
Monitor Requests must be published to be picked up by Monitoring services
As described in the Raiden Spec Monitor Requests will be published into a global Matrix room, see here for Monitoring services to be picked up. Therefore, the Raiden client needs to publish every balance update of its channels in case they should be monitored.
Every new balance update will be published as a Monitor Request
Monitor Requests are defined in the Raiden Spec. These messages will be published and picked up by the Monitoring Services.
Specification
For every balance update of a channel the user wants to be monitored, a Monitor Request needs to be published.
General issue, see #28
Detailed Specification tbd
Backwards Compatibility tbd
It is probably backwards compatible.
Timeline to be met in order to make MS / PFS team happy
The text was updated successfully, but these errors were encountered: