-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple nodes / accounts #87
Comments
They way I do this right now is I just install the extension two times with a slightly different logo. Maybe a different build option for regest or testnet would be cool so the browser extension is easily distinguishable. |
Interesting work-around, though I want to avoid people having two extensions active at once, since they'll both try to inject WebLN at the same time and it won't be deterministic which one is "active". |
I can't see this being much use beyond Joule developers. I'd guess that most application developers go straight to mainnet, since payments are so small on lightning that it's fine to risk the few satoshis and test directly on mainnet. Is installing Joule for multiple chrome users and then switching between them a good workaround? |
That's what I do now, testnet on another chrome user. works fine. I think KISS and sticking to one node is fine. |
I have multiple nodes and I love Joule. UP!! |
Zap now has multiple node / wallet / account support. Maybe Joule soon. |
Maybe this is just because I test a lot, but I think there's a use case for having multiple nodes you can connect to and choose from. At the very least for hopping between mainnet / testnet / regtest if you're a developer. Some notes on implementation:
webln
enabled website and you change accounts. Probably prompt the user before doing this.The text was updated successfully, but these errors were encountered: