Yeah I had noticed that too. I also noticed that the seed nodes from previous configs weren't on 24 hrs and I only seem to have time to work on fluttercoin when they were offline. So I built out a seed node that is on the good block chain.
so use a config like this and you should be ok. The IPs are the clean server on the good block chain that I built thats up 24/7.
server=0
upnp=0
ipv6=0
noirc=1
listen=0
dnsseed=0
gen=0
4way=0
rpcuser=XXXXXX
rpcpassword=XXXXXX
rpcport=7474
port=7408
seednode=162.243.194.203
addnode=162.243.194.203
Your most recent block should be above 107,000 if you are on the right chain.
Donations are certainly welcome but not necessary to keep this seed node online
FLT: F7tjuZYyK27qSvs5jpSctZrt47znWKNr8f
slax0r, you want to make this official, I can add this to the seednode list the clients use. We have 4 right now. All should be online, they are on AWS nodes, one is the multipool.
For those syncing, easiest way is to use the following, .10 is backward compatible to .7 as well. I think it may be time to setup .11 so it ignores .7 going forward, the sync problems are a pain in the ass. I'm not sure why they are online at all, I have set checkpoints for them, but I guess their height is not high enough to get to the checkpoints. And if you are on a client that is not in sync, you should see a warning about checkpoint. If you are in sync, this is does not appear.
rpcuser=x
rpcpassword=x
rpcallowip=127.0.0.1
noirc=1
listen=1
dnsseed=1
server=1
connect=54.215.241.255
connect=87.98.188.77
connect=50.147.45.28
connect=54.84.46.196
connect=162.243.194.203
also after you sync, remove the connect lines, or delete the conf file completely, it is not needed to stay in sync, and find nodes.
I run with the following on both versions old/new:
rpcuser=x
rpcpassword=x
rpcallowip=127.0.0.1
noirc=1
listen=1
dnsseed=1
server=1
As of this afternoon on explorer we are at 43.3% running 4.5.8+ version clients, why is it so hard to update your client? But I guess since there are nodes still at 90k, 105k, 106k, they can't even figure out they are out of sync either. I wish there was a SHUTDOWN option alert I could send and they would all be gone