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.
Orphan blocks issue resolved
Forum rules
The News forum is only for updates about the Prohashing pool.
Replies to posts in this forum should be related to the news being announced. If you need support on another issue, please post in the forum related to that topic or seek one of the official support options listed in the top right corner of the forums page or on prohashing.com/about.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
The News forum is only for updates about the Prohashing pool.
Replies to posts in this forum should be related to the news being announced. If you need support on another issue, please post in the forum related to that topic or seek one of the official support options listed in the top right corner of the forums page or on prohashing.com/about.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
-
Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA