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
As discussed in https://github.com/raiden-network/spec/issues/46#issuecomment-377721214 and mentioned in: https://github.com/raiden-network/spec/pull/54#discussion_r182723889, https://github.com/raiden-network/spec/pull/54#discussion_r182726565, https://github.com/raiden-network/spec/pull/54#discussion_r182811048
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