Quote from: bible_pay on April 03, 2019, 12:56:13 PM

** POOL.BIBLEPAY.ORG hashing status update **

...

So at this point, pool.biblepay now marks work that is solved within 1 second of another share as Stale (the user still gets credit for the first solution, first in still wins). This resulted in an approx 50% decrease in rewards to the top 5 pool users (IE anyone running multi-wallets).

Quote from: capulo

.

Would setting different worker ids be enough to prevent "stable" submissions that are within 500ms of each other? Or do we need a separate logins for pool.biblepay.org? At least, it'll look like we have more users with unique IDs. As long as auto withdraw is working, it should be somewhat automated except the one time setup for each account.

Quote from: secoccular on April 03, 2019, 02:46:16 PM

Quote from: GaryH on April 03, 2019, 01:31:47 PM

My opinion is we're gonna need to make it easier for users to come to BBP.

..
I recall Rob saying a while ago, that BBP is really geared towards tech-savy Christians. Rob, if I have that wrong, please chime in with what the target audience is as you see it. If it is really more for technical Christians who enjoy spending time on github and doing testing, then BBP is actually a complete success. That is, it's appealing to that small group it's intended for.

This is a good opinion. At the very least, we need a "resync" option within the QT wallet where everything is erased except the essential files (masternode.conf, biblepay.conf, and wallet.dat). BiblePay had so many mandatory upgrades in the last few months, it was hard to keep up with. I've spent an inordinate amount of time and effort supporting others those that missed a mandatory update and had to start from scratch.