Not? using the JSONRPC-Client from the Raiden client to interact with the blockchain

[christianbrb]

Analysis

Current State

Currently, the scenario player is using the JSONRPC-Client from the Raiden client to interact with the blockchain. For all other operations, it is using the Raiden API and CLI.

Problem

The JSONRPC-client is a "private" Raiden client feature.

This leads to several problems

• eg. Add proper condition checks to the interation with the blockchain (using Raiden proxies) #315
• Using "Wait" tasks for synchronization
• Maintainability, if Raiden client is getting refactored
• Seperation of concerns
• ... please extend ...

and makes it hard to debug and fix issues.

Solution

• Analyse which features/tasks are using the JSONRPC-client
• Decide on next steps

[deepbrook]

Generally speaking, any operation that requires sending a transaction, makes use of the JSONRPCClient class.

An issue I see, which is closely related to maintainabilty mentioned above, is that due to tight coupling of the SP with the raiden contracts, changes in those repositories are guaranteed to almost always result in errors/bugs in the SP.

[konradkonrad]

After a conversation with client devs, I believe the proper way is using the raiden client proxies: https://github.com/raiden-network/raiden/tree/develop/raiden/network/proxies

This also relates to #349 -- using the proxies, all transactions will be logged.

[konradkonrad]

See also #315

[palango]

Starting with #511 we will use the proxies Raiden uses.