-
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
Temporarily deactivate public network option #3938
Temporarily deactivate public network option #3938
Conversation
This will be in place until we are able to check if a connected Bitcoin Core is configured properly for our requirements
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for addressing this critical issue
It seems Bisq will fallback to using the public Bitcoin network if valid Bitcoin nodes are not configured, which is unreliable. Maybe you should fallback to the provided Bitcoin nodes instead? |
Regarding re-enabling the public network option, even with pruning and bloom filter checks in place, see #3982 (comment). |
To perform the checks on the local Bitcoin node, we initiate a Bitcoin connection to get information from the handshake and then we close it, just to have Bisq rebuild the connection in case the node is well configured. We might be able to perform these checks by hooking into the regular/existing connection process. In that case the checks would be free in terms of network IO. I might take this up, if there's demand. |
This will be in place until we are able to check if a connected Bitcoin Core is configured properly for our requirements.