Quote from: y_virtual on November 12, 2016, 09:47:23 PM

Quote from: onsightit on November 12, 2016, 09:10:55 PM

Quote from: y_virtual on November 12, 2016, 08:49:04 PM

Quote from: solarcoiner on November 12, 2016, 08:34:39 PM

Quote from: y_virtual on November 12, 2016, 07:41:52 PM

Quote from: onsightit on November 12, 2016, 06:57:57 PM

Quote from: solarcoiner on November 12, 2016, 06:48:54 PM

Quote from: Scalextrix on November 12, 2016, 06:34:18 PM

I seem to be back on the long chain again, so far so good

Just installed the new update and reloading blockchain. I will post the results

2.1.7.1 is ready to go. Help->Check for Update, then let me know if you are still having issues. Thanks, again, everyone.

-Steve

~~Now it doesn't even try to catch up - it's In Sync right after downloading the bootstrap. I will post a screenshot and a text file with the getpeerinfo.~~ I am connecting from a cellular IP (random within the provider's range).

EDIT: will repeat the bootstrap download, just to be sure it got right.
EDIT2: Now it works! This time it did sync up to the current Explorer block height, and keeps on syncing. Will now go on to upgrade all wallets.
Thank you Steve!

Mine wont sync although it says in sync. Im missing about 20 blocks.

When I got back from the cellular IP to my regular LAN/WAN setup, syncing stopped altogether - it does say "In Sync" (with a new empty wallet) and would apparently start staking with a non-empty wallet. As per Steve, my regular IP may have been banned for up to 24 hours, but shouldn't it be trying to sync during the ban, instead of staying In Sync and staking at the wrong block height? This time I need to post a snapshot - back here in a few minutes.

Let me delete the peers.dat on the master node and see if that helps some of you that may be banned. I'll edit this post when done...

EDIT: Done.

solarcoiner, can you PM me your debug.log file?

OK, I will try it now, but this current logic would still leave the possibility for any IP that gets banned to fork since it will stay In Sync & Staking instead of just hanging in a Syncing state until the ban expires. Or may be that would't be an issue later on? Still the possibility remains that anyone newly connected and syncing will have the (bad) chance to sync to a banned IP and join that fork.

EDIT: Just re-loaded the blockchain from the bootstrap, synced to 1456166... took it a while waiting for 94 more blocks, but eventually decided it's In Sync at 1456166.

While I am currently researching the problem (I believe there are still too many forked 2.1.7 nodes, even though 2.1.1 is being successfully blocked), could everyone that is not on the block displayed by CryptoID do the following:

1. Shutdown your wallet.
2. Delete peers.dat.
3. Verify that solarcoin.conf only has the master node: addnode=162.243.214.120
4. Restart the wallet.
5. Reload the Blockchain.

I have just created a fresh bootstrap from the master node. The reason you stop several blocks short of the longest chain is because the fork you are on is not generating blocks, or doing so slowly. If you can get past that chain, you should be good.

-Steve

EDIT: 2.1.7 still outnumbers 2.1.7.1 almost 5 to 1, so we need to get more nodes to update.