- Yesterday's "duplicate share" fix was wildly successful. Rejected shares are now at 0.9%. About half of that total consists of shares rejected because the merge mining information is stale. Those shares should still be credited for the primary coin, even if the dogecoin block they reference is stale. I'm going to work on that tonight, which should reduce rejected shares to 0.5%.
- More importantly, the earlier fix of "share is above target" errors for fast miners meant that the big spikes that occur occasionally are no longer causing those people to get rejected shares, or causing others to get duplicate shares.
- CryptoX reported a bug with saving settings, which Chris will work on tonight.
- Chris did some Internet research and determined a way to prevent spam on these forums, which seems to have been successful. The bots stopped posting in the "Bitcoin Thoughts" forum, so he just needs to delete all the existing accounts they have already registered and that issue should be fixed.
- There is an issue where miners' payouts can be further improved when the same coin is being mined as is being paid out. For example, if a miner selects to mine 42 coins with c=42, and sets a payout proportion of 42 to 100%, that miner can possibly lose the spread between the buy and sell price for 42. That doesn't make sense, because no coins are being traded. Instead, for cases where the same coin is being mined as is being paid, I will work this weekend on paying out 1:1.
- For the first time, the payout script paid out all coins in a fully automated fashion, removing a big waste of Chris's time.
- Cryptsy seems to be holding votes on which coins to add to its platform. Chris cast many votes on all the scrypt coins, and withheld votes on non-scrypt coins. He installed the daemons to download the blockchains for the coins with the highest number of votes so that they can start being mined as soon as they appear on Cryptsy, if they do.
Status as of Wednesday, November 19
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.
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.
- Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA
Status as of Wednesday, November 19
Here's today's status: