Quote from: drays on May 25, 2021, 11:59:32 PM

Quote from: dexterw1n on May 24, 2021, 11:27:19 PM

I just wonder if it's something in the 3.0.0 or the 3.0.1 client or both. I suck at crypto, is there something I could put in my conf to block node2.bullion.one? So I can test it and see if it's that? I dunno, I'm currently reindexing right now.

As far as I know, there is no explicit way to manually block a node. However you can force the wallet to connect only to some predefined nodes, and reject all others.
For that you need to remove "addnode=" entries from your bullion.conf (in case if there were any), and add "connect=" entries pointing to the hosts you want to exclusively connect to.

So, basically, you need to put this into your bullion.conf:

Code:

connect=95.217.77.209
connect=82.21.164.47
connect=89.210.233.40
connect=24.55.154.69
connect=73.121.220.52

However I doubt this will actually help... Might worth a try, anyway. I already did so, and my wallet is connected to all nodes except node2.bullion.one currently.

Is it bullion.conf or cryptobullion.conf Huh

I have entries in the latter while the former is empty.

In my cryptobullion.conf file I now have:

Code:

connect=95.217.77.209
connect=82.21.164.47
connect=89.210.233.40
connect=24.55.154.69
connect=73.121.220.52

# addnode=174.72.227.20:7695
# addnode=175.156.166.57:7695
# addnode=67.128.36.90:7695
# addnode=76.169.51.184:7695
# addnode=80.3.158.239:7695
# addnode=87.98.243.61:7695
# addnode=94.130.237.52:7695
# addnode=94.15.192.76:7695