currently I do not see the networkID in the protocol - but I think we will need that as currently It leads to:
- I seem to cannot switch the network from main to something cheaper / testing friendlier for the balance-manager I am testing in currently.
- Now only main is assumed - when signing EIP-155 style I need the networkId - currently I can only guess main - but it feels really wrong.
- IMHO the dApp should be able to signal which networks it is able to be used with and which ones it prefers
- perhaps network switching should be build in the protocol
Found a way now with balance-manager to switch networks for wallet connect:
you just do not click ‘logout’ which seems to set the network back to 1.
You switch to the network of your linking with metamask - and then you click on balance manager and then wallet connect. This is now good for testing- but potentially dangerous for users ( cc @Ricburton )