Skip to content
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

Merged

Conversation

ripcurlx
Copy link
Contributor

@ripcurlx ripcurlx commented Feb 5, 2020

This will be in place until we are able to check if a connected Bitcoin Core is configured properly for our requirements.

Bildschirmfoto 2020-02-05 um 10 32 56

This will be in place until we are able to check if a connected
Bitcoin Core is configured properly for our requirements
@ripcurlx ripcurlx requested a review from wiz February 5, 2020 09:33
@ripcurlx ripcurlx added this to the v1.2.6 milestone Feb 5, 2020
Copy link
Member

@sqrrm sqrrm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK

@sqrrm sqrrm merged commit 3748a7e into bisq-network:master Feb 5, 2020
Copy link
Contributor

@wiz wiz left a 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

@ripcurlx ripcurlx added the is:priority PR or issue marked with this label is up for compensation label Feb 5, 2020
@wiz
Copy link
Contributor

wiz commented Feb 19, 2020

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?

@cbeams
Copy link
Contributor

cbeams commented Feb 27, 2020

Regarding re-enabling the public network option, even with pruning and bloom filter checks in place, see #3982 (comment).

@dmos62
Copy link
Contributor

dmos62 commented Feb 27, 2020

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.

@ripcurlx ripcurlx deleted the temporarily-deactivate-public-network branch July 16, 2021 07:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
is:priority PR or issue marked with this label is up for compensation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants