Status as of Tuesday, November 18

Discussion of development releases of Prohashing / Requests for features
Forum rules
The Development forum is for discussion of development releases of Prohashing and for feedback on the site, requests for features, etc.

While we can't promise we will be able to implement every feature request, we will give them each due consideration and do our best with the resources and staffing we have available.

For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
Post Reply
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Status as of Tuesday, November 18

Post by Steve Sokolowski » Tue Nov 18, 2014 10:07 am

Here's today's status:
  • Yesterday's release fixed many significant bugs, reducing the number of work restarts by almost 50% to our test miners, much more than anticipated. Interestingly, the release uncovered other bugs that did not occur because they were prevented from becoming significant by the ones we fixed.
  • The latest issue is of "duplicate shares." The reason for the duplicate shares is that the "extranonce" value sent to the miners is being duplicated, but because there were so many work restarts before, the issue would never be a big problem. I have a fix for this issue and will release it this evening if testing goes well.
  • Some miners appear to have had a hashrate increase of as much as 10% due to the reduction in work restarts. The reduction in duplicate shares later today should help these miners become even more profitable.
  • Other remaining issues include coins not coming back online after cryptsy's "locked wallets," which I am working on, and the issue that old coins can't use sendmany to issue payouts because they use buggy code forked from an old version of bitcoin. To fix those issues, I'll just use sendtoaddress for each payout.
Expect a 2-minute outage later today while I restart the server to eliminate the "duplicate shares" issue.
Post Reply