Skip to content
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

Specify and implement MR-Messages for raiden client #34

Closed
3 of 4 tasks
karlb opened this issue Jan 21, 2019 · 3 comments
Closed
3 of 4 tasks

Specify and implement MR-Messages for raiden client #34

karlb opened this issue Jan 21, 2019 · 3 comments
Assignees
Labels
Client ⚡ Requires Client changes MS 👀 Related to the Monitoring Service

Comments

@karlb
Copy link
Contributor

karlb commented Jan 21, 2019

  • specify message format
  • get massage format accepted by client team
  • generate message on the client (actual sending will be done in #3273)
  • deserialize message on MS (actual matrix listening will be done in Monitoring Service listens to MR posts #14)

Relies on Raiden issue

8 SP

@Dominik1999
Copy link
Contributor

Dominik1999 commented Jan 22, 2019

  • to check, when UDC needs to query participant data from TokenNetwork Contact (data might be erased after settle)
  • may add necessary waiting period to monitor request - to be checked by UDC (or in UDC constant)
  • additional todo define "User Policy" (how to configure a channel to be monitored)

@Dominik1999
Copy link
Contributor

@konradkonrad will take up this issue (specific client issue #3273, see above)

@palango palango added MS 👀 Related to the Monitoring Service Client ⚡ Requires Client changes labels Feb 5, 2019
@palango
Copy link
Contributor

palango commented Feb 12, 2019

The MS will use the Raiden message for decoding as well. Remaining work will be tracked in #14

@palango palango closed this as completed Feb 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client ⚡ Requires Client changes MS 👀 Related to the Monitoring Service
Projects
None yet
Development

No branches or pull requests

3 participants