FORK of BC?
-
https://bitinfocharts.com/feathercoin/
is showing two 0.8.6.2 clients and 1 0.8.6.1 client.
Could this cause the fork?
I dont see any fork message in my debug log, I just see the below.
2017-02-04 21:05:56 ERROR: ProcessBlock() : CheckBlock FAILED 2017-02-04 21:05:58 ProcessBlock: Preliminary checks 2017-02-04 21:05:58 ERROR: CheckBlockHeader() : block with timestamp before last checkpoint 2017-02-04 21:05:58 ERROR: ProcessBlock() : CheckBlock FAILED 2017-02-04 21:05:58 ProcessBlock: Preliminary checks 2017-02-04 21:05:58 ERROR: CheckBlockHeader() : block with timestamp before last checkpoint 2017-02-04 21:05:58 ERROR: ProcessBlock() : CheckBlock FAILED
-
84.240.31.184 /Satoshi:0.8.6.2/
-
-
@GMC
Time Since Last Block 39 Hours 55 Minutes -
So the release of 0.9.6 fucked every pool over who is still on 0.8.6.2
-
All Pools need to get informed ASAP.
-
Give me Coins has been notified and they are upgrading to 0.9.6 now.
-
FTC have had the 0.9.x series available for installation for a year, they may need to change over, but it should have been by 0.11 …
However, there were no changes made to 0.9.6 that should have caused that problem. We need to look into it a bit more before final judgment.
The only “likely” culprit is 0.11 version forward compatibility. I can just see an edge case of old versions of 0.8. being still used However, this seems strange that FTC explorer was out of date.
If it is out of date, it would indicate that (old versions) being used (for mining pools and explorers etc) is the issue (and FTC won’t have to look to release 0.9.6.1 urgently with a bug fix…
-
Update:
Hashrate looks good. - Difficulty also.
Theblocksfactory still needs to update to 0.9.6, others look fine.
Checked all exchanges, they are also fine.
Regards,
ChekaZ -
Cheers @Chekaz, I messaged FTC server admins to check the block explorer also.
-
I have contacted The Blocks Factory via Twitter and BitcoinTalk