Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Use different database paths for different blockchains #1328
Raiden must not assume that the running blockchain client is always connected to the same network. Raiden can handle different networks by:
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.
referenced this issue
Mar 29, 2018
Yeah option 2 is fine. But how would that work?
You connect to the ethereum client at the specified
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.