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

Show warning if user has a pruned Bitcoin node locally running #3273

Open
chimp1984 opened this issue Sep 16, 2019 · 3 comments
Open

Show warning if user has a pruned Bitcoin node locally running #3273

chimp1984 opened this issue Sep 16, 2019 · 3 comments
Labels

Comments

@chimp1984
Copy link
Contributor

@chimp1984 chimp1984 commented Sep 16, 2019

BitcoinJ requires a non-pruned Bitcoin node. We get frequently issues that users who don't know that run into problems. We should find a way to detect if a local node is running in pruned mode and if so show a popup to tell the user to either shut down that pruned node and connect to the provided bitcoin nodes or change their pruned node to a non-pruned node.
Related is that a Bitcoin node cannot be used while it is syncing with the network. Not sure if that can be detected.

If there is no way to detect pruned mode from Bisq (we cannot use RPC for that), we could use the special exceptions thrown in BitcoinJ to catch those and react on those to show a popup.

@acrual

This comment has been minimized.

Copy link

@acrual acrual commented Sep 16, 2019

@chimp1984 not only detecting a prune node but also if the local node is not running itself.
In my case I had chosen my local node, yet I had forgotten to start it. I didn't realize that was the problem until the bsq tx didn't get through

@stale

This comment has been minimized.

Copy link

@stale stale bot commented Dec 18, 2019

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.

@stale stale bot added the was:dropped label Dec 18, 2019
@ripcurlx

This comment has been minimized.

Copy link
Member

@ripcurlx ripcurlx commented Dec 18, 2019

Still relevant.

@stale stale bot removed the was:dropped label Dec 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.