You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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
and makes it hard to debug and fix issues.
Solution
The text was updated successfully, but these errors were encountered: