-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Do not connect to a local pruned node #2668
Comments
You can pass --btcNodes=... as prog. argument. List the remote node there then it should not connect to localhost (not 100% sure if it overrides localhost but should) |
What if there is no known reliable remote full (non-pruned) node available? I'm running a local pruned bitcoin node but don't have a remote full node available. I'd still like to be able to run Bisq without having to shut down my local pruned node. If I understand correctly, this is currently not possible. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant. |
Use switch |
A pruned bitcoin node is running locally.
I don't want Bisq to connect to it because as far as I know it can't use pruned nodes.
I want to use a remote node, but can't set it on the network settings page (greyed out), the only option available was resync spv node, but obviously that won't happen while my bitcoin node is running, because bisq wants to connect to it.
Is the a config file I can set a remote node or some other method to tell bisq to use a remote node?
The text was updated successfully, but these errors were encountered: