Quote from: Sterlingcoin on October 16, 2017, 10:07:25 PM

Quote from: Sapfon on October 13, 2017, 04:59:27 PM

Seems like my wallet is stuck, been at block 715128 for 121 days now with 35 active connections. Checked firewall and re-installed once. Did we have other solutions ? I know it was somewhere in these 250 pages Cheesy

Hi Sapfon. So very sorry for the slow response. I had been away for some personal matter for several days. Please do not think your issue was being ignored.

Being stuck for that long certainly means something is wrong. A few things could be the culprit. First, and take no offense to this obvious culprit, has it run out of disk space? I assume that answer is no and you would have already been aware of that. Bear with my thinking out loud.

Second, a misbehaving peer. I know this seems very unlikely given the number of peers, but it might be a quick fix and worth a minute. 1) Stop your wallet. 2) Navigate within the SLG data directory (Windows: c:\Users\Sapfon\AppData\Roaming\sterlingcoin\ or Linux: ~/.sterlingcoin/ ) and delete ONLY the peers.dat file. 3) Start the wallet.

Third, getting into more time intensive resolutions, you may have an unconforming blockchain (you forked somehow). This does seem unlikely given the number of peers also, but troubleshooting. To check this, let's compare the block hash of the latest block you have, block 715128. The block explorer reveals this block hash as 46d11aebe6bee6f5c2cad719c1d9479ac7fca93fbc4b48402607926ca9822cab and we want to compare that to what block hash you have for block 715128. To do so from Windows, click the 'Explorer' button and input 715128 in the block number input box. Then click 'Jump to Block'. The Block Hash is the 2nd line of output. In Linux you would issue the RPC command "./sterlingcoind getblockhash 715128". Comparing the first and last few characters will suffice, 46d1 ... 2cab. If yours is different, a resync will be in order as the reorganization functions of the wallet certainly have failed you in 121 days. If your hash is the same, I suspect the above second resolution should fix the issue.

I am sorry you are having an issue and hope this information helps. Again, sorry for the slow response and you feeling the need to scour 250 pages. Of course, this slow of a response is not normal and not the time a community member should expect assistance. Unique circumstances made it so and I will be standing by to offer more assistance if needed.

First two parts were not the issue but 3rd... It gives me 21bcb6b37863e881f1427f7d7bb5868bc4f433088cbc9d8c5647f9a9ae4cc512 as Block hash :O So I need to resync apparently.