Orphan blocks issue resolved
Posted: Thu Feb 28, 2019 10:06 am
We discovered an issue where some mature blocks were incorrectly marked as orphans, and some orphaned blocks were incorrectly marked as mature. The problem was that there are some coins that don't have anyone mining them, so blocks we found months ago are unlikely to ever be confirmed. The program that checks blocks sorted by block_hash, not by date, so it would always spend all its time checking the status of these old blocks, and timeout before getting to the newest blocks. We changed the program to mark all blockchains that haven't had any new blocks within 14 days as lost, because we won't be able to spend money on a blockchain that nobody is mining anyway.
The fix was issued last night and verified today, and we responded to all support tickets regarding the issue.
The fix was issued last night and verified today, and we responded to all support tickets regarding the issue.