Major change in work restart calculations coming

News updates about the Prohashing pool
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.
Post Reply
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Major change in work restart calculations coming

Post by Steve Sokolowski » Sat Jan 16, 2016 9:14 am

We're pleased to announce that a major change in how work restarts are calculated will be released soon.

Currently, determining the time wasted after a work restart is sent to a miner is accomplished by sending easy shares to that miner and waiting for the result to see how long it takes to respond. Unfortunately, this strategy has some drawbacks: some pools like NiceHash prohibit work on shares that are so easy, and time is wasted on these useless shares during the testing.

We were able to implement a more accurate method of determining this time by using statistics and curve fitting. Beginning with the next release, the concept of "work restart testing" will be removed. The "r=" password argument will also become obsolete. Instead, the characteristics of the miner will be analyzed using statistics and the work restart time of that miner will be able to be automatically calculated, removing the need for any human intervention.

We've discovered that this new method is also more accurate, in addition to being simpler - which leads to greater profits. We'll notify everyone of the changes when they are about to deploy. When they do deploy, those who use an "r=" password argument will be asked to delete it from their configurations. Some API fields will also be removed and the website will be modified to remove the concept of "static restart intervals." For now, the old code is still deployed and no action should be taken until we provide notice of the exact release date.
Post Reply