Hi!
Most of the time I’m having only 2 or 3 Bitcoin network peers. Very rarely do I have 4 and it’s always for a short time. This doesn’t allow me to do almost any operation in Bisq.
What can I do about this?
Hi!
Most of the time I’m having only 2 or 3 Bitcoin network peers. Very rarely do I have 4 and it’s always for a short time. This doesn’t allow me to do almost any operation in Bisq.
What can I do about this?
I started having the very same issue. I think it has been like this for me since around April 26th, and it was getting progressively worth. As of yesterday I keep getting “Synchronizing with DAO” nonstop and it never completes. Because of this I can’t take offers - Bisq gives me an error message about invalid chain height. Hoping whatever this latest wave of malfunction is will go away soon.
In Matrix chat @pazza83 gave advice: “You could try deselecting connect via Tor to improve your connection.”
This helped me and my bitcoin peers are now at 5 while before they were 1-3.
This is in the Settings > Network Info > Use Tor for Bitcoin Network.
not using tor is faster, but is not private, obviously. Regarding DAO sync then, you can only connect to seednodes throuth tor, and tor has been under heavy load lately: Performance – Tor Metrics
Do I need to connect to my own node? Because I don’t have one.
It’s just recommended, you’ll experience less issues.
I had the same issue today. I suspect that in times of ‘extreme crypto greed’ like now tor is under heavy load like suddenwhipvapor is also saying.
Switching off connection via tor only made it worse, as I went from 3 to 2 peers. I resynced the DAO state from resources (settings → preferences → scroll down, rebuild dao state from resources) and shortly after that I went from 3 to 4 network peers again. With tor. Don’t know if it’s coincidence, but I thought it’s worth mentioning.
Why are 4 bitcoin network peers necessary, could it be done with three also? What would be the reason not do do that?
it’s for redundancy reasons, you could otherwise select the onion address of a single node, and place it in custom node under settings > network, so bisq will be happy with just that one alone