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
Raiden must not assume that the running blockchain client is always connected to the same network. Raiden can handle different networks by:
notifying the user about the mismatch and quitting
using different database paths for different networks
The first option is a bit problematic because it makes unecessarily annoying to use different networks, so I propose the use of option 2 with a message on the command line about the current used network.
The text was updated successfully, but these errors were encountered:
You connect to the ethereum client at the specified eth-rpc-endpoint and then you get the network id with the net_version RPC call and thus you know the network id and the directory for the DB to read/write to.
No extra arguments needed from the user, just keeping separate DB directories.
If the above as I understand it are the requirements I will just implement it in the morning.