Status as of Monday, November 24

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 Monday, November 24

Post by Steve Sokolowski » Mon Nov 24, 2014 9:15 am

Here's today's status. We have fixed many bugs and made many optimizations in a release going out tonight.
  • There is a problem with the pool's reported profitability, which is displaying at the top of the page and on Cryptsy. The cause is that when the server loses connection with the dogecoin daemon, even for a few seconds, the pool eliminates dogecoin profitability from the total and get stuck until the next reporting period. Of course, the correct behavior is that the dogecoin profitability should be restored when dogecoins come back online. This issue is fixed in the next release, but until then, the effects of the bug are that poolPicker is showing a much lower profitability than people are actually receiving, and the payout chart is much lower than actual as well.
  • In the next release, a side effect of this fix is that the profitability chart at the bottom of the page will be updated in real time, rather than delayed by several minutes.
  • We've finalized an improvement where stale shares will be credited the merge mined block, if the merge mined portion of the block is valid. That will give most stale shares about 15% of normal value, a significant improvement from zero.
  • We resolved the "lost" blocks issue, which allows us to mine about 10 additional coins. We also discovered the cause of another several errors with coins: apparently, when mining some proof of stake coins, the wallet needs to be unlocked. Once the release occurs, Chris is going to start adding these new coins.
  • Someone suggested a very quick and easy error condition to add to the other 34 errors we have: if the buy price is less than the sell price. While Cryptsy was 100% at fault in the previous situation, this new error type would have saved us the need to negotiate with them for reimbursement. We added a new error code for that situation.
  • The situation with Cryptsy has spread to the media; a rather negative article about the situation is posted at https://www.cryptocoinsnews.com/bug-cry ... -operator/.
  • The next goal after these issues are resolved will be to migrate as much of our trading away from Cryptsy as soon as possible. We will start with Poloniex. The goal will be to have Cryptsy available as an exchange only for its unique coins, so that most of our business is on reliable platforms.
  • Earlier in the week, Chris had been working on creating a social media presence. He created twitter, facebook, and g+ accounts, all of which are now featured on the front page.
Post Reply