Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Discuss Monitoring Services priority enforcement #58

Open
loredanacirstea opened this issue Apr 19, 2018 · 1 comment
Open

Discuss Monitoring Services priority enforcement #58

loredanacirstea opened this issue Apr 19, 2018 · 1 comment
Assignees
Labels
monitoring service ms:smart contracts Smart Contracts for Monitoring Service
Milestone

Comments

@loredanacirstea
Copy link
Contributor

As discussed in
#46 (comment)
and mentioned in:
#54 (comment), #54 (comment), #54 (comment)

We need to specify how Monitoring Services are prioritized when they will try to send the participants' balance proofs to the smart contract. The scope is to avoid them spamming the chain and losing gas on failed transactions.

We need rules to queue them and decide on how to enforce these rules

  • in the Raiden client
  • on-chain, in the Monitoring Service smart contract
@pirapira
Copy link
Contributor

This has been implemented. But is the priority enforcement documented in this spec repository?

@pirapira pirapira modified the milestones: Ithaca, Alderaan Aug 13, 2019
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
monitoring service ms:smart contracts Smart Contracts for Monitoring Service
Projects
None yet
Development

No branches or pull requests

4 participants