-
Notifications
You must be signed in to change notification settings - Fork 148
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
Feature Request: Locking Nodes #470
Comments
Hey @michaelWuensch, this is a good idea. However, "locking" of the LND node isn't possible as there isn't an RPC available to lock the node (see WalletUnlocker.proto). Unlocking the wallet would be possible but I think it may make sense to handle that in the app you're building, no? |
@jamaljsr |
Ah yes, it is possible to startup the nodes in a locked state. Before starting the network, right-click on the v0.13 node, go to Advanced Options, click on the Pre-fill Default Command icon, then remove The only drawback to this is if the node isn't unlocked within 2 minutes, Polar will mark it as failed to startup. You can still continue using the node from your app but you wont be able to interact with it from the Polar UI. |
Okay thanks, that should work if I can setup that node. |
Oh right. Polar won't show you the option to open a Terminal if it thinks the node hasn't started properly. You could bypass Polar in this instance and connect directly to the docker container using a command such as:
The path of the compose file assumes you only have one network defined in Polar. If you have multiple, you'll need to change the 1 to a 2 or 3 based on the order that they were created. Also change |
Is your feature request related to a problem? Please describe.
The new lnd v0.13.0 version changed a lot in regards to unlocking nodes.
I would like to be able to test if unlocking in my application works by locking those nodes in Polar
Describe the solution you'd like
Ideally if a node was selected in the graph, in the details panel there could be a button "lock/unlock".
To avoid password hazzle a standard password that is always "polar" could be used, as this is solely for testing purposes anyway.
If this can already be acheived with Polar, then a short answer on how to do this would also be sufficient.
The text was updated successfully, but these errors were encountered: