That's because there is already more than one sharechain in use already - changing the seednodes to pools that are using multiple sharechains won't make any difference, in fact it will only increase the problem. I did mention the problem some pages back.
Isn't updating the seednodes to reliable ones what we needed to do, IconFirm? That is why I am trying to gather only seednodes which are running the new wallet and get rid of old junk ones that are causing problems. Tell me if I am going down the wrong path here.Yes, if you are 100% certain that they are using the correct sharechain.
I fired up my node again & am connected to 5 nodes:
http://5.39.79.140:9322/ is running an out of date wallet.
http://77.249.199.235:9322/ is a blank page, so it's impossible to tell what that node is running at all. I'll ban that IP.
http://185.3.135.82:9322/ is a blank page, so it's impossible to tell what that node is running at all. I'll ban that IP too.
So only 2 out of 5 nodes are known to be up to date wallet wise, but unknown if they are both on the same sharechain. Maybe banning the blank nodes will improve things.....