Bitcoin Forum

I'm running core 12.1 over public WiFi. I haven't had any problems until the last couple of days. Then I started to find that I couldn't synchronise my blockchain. This morning I was 2 days behind, and it appeared to start synchronisation, but after 2 hours it hadn't reduced the out-of-date time. I noticed that I had 3 classic nodes in my peer list, and I blocked them for a week. Fairly quickly, my sync. arrears dropped to 12 hours, and it hung there. When I looked at my peer list, I saw that one of the Satoshi nodes had been replaced by another node type (bitcoinj I think). I banned that, and the synchronisation completed fairly soon afterwards.

My question is - Is there a new attempt to disadvantage Core users by classic, or has something got at my core software?

I'm starting to get a bit concerned about this.
If I leave classic nodes in my peer list, then it seems to slow down synchronisation, If I ban them for a week, then sync zips along.
I guess I should do a full malware scan to see if anything has got at my core installation.
I'm on McDonalds WiFi, and I know that they log web activity, presumably for marketing research, but I'm not sure how to check their investigation into the use of non-standard ports.

It's just like before, though not quite as bad due to some client changes, re: block timeouts, downloading from multiple peers, etc.

It's still much faster to connect to a single 'fast' node in order to synch the blockchain, than it is to connect to multiple nodes.

For the node I have on my home internet connection, I've always just used 1 maxconnection and connect to whatever server I happen to have running bitcoind at the time.

I guess if you wanted to test speed differential, you could see what I mean, re:  maxconnections=1 connect=192.254.76.218 ... that's the node I have running bitcoind at the moment, anyway..  

speaking of servers, dacentec restocked a whole bunch of $20 and $25 stuff yesterday.  jeje.