The number of shares currently displayed in the "My Stats" section of each pool is currently exactly that, the number of submitted shares. To make it easier for miners to compare their contribution, I would like to change that to the value used by the payout system which would be the sum of all shares multiplied by their difficulty.
Let's assume Miner A submits ten shares at difficulty 10. With the current system he would see "10" as his number of shares. Under the proposed system he would see 10 * 10 = 100. Miner B with a much weaker rig, submits 100 shares but at difficulty 1 which would also result in the value 100. As such their contribution to the block effort would be equal. Using a payout system without temporal variance this would result in both miners receiving an equal amount. With PPLNS which we use to prevent pool hopping, there would be a slight variance depending on when both miners submitted shares and whether one of them stopped mining at some point.
This change would be in line with what most other pools are using today. What do you think?
We've just deployed two fixes for the Lyra2re2 based pools Monacoin and Vertcoin. The hashrate should be in line with the actual values and the payouts should be distributed more evenly according to hashrate. I will monitor this constantly.
As already discussed in the other thread related to this, the Monacoin pool was supposed to find a lot more blocks over the day than it did given its hashrate. As a matter of fact the pool did find blocks, 10 to be precise. The reason those blocks were not visable on the pool's block list was a subtle change done to the process when submitting mined blocks. After the pool detects that a submitted share has hit the block target, the block gets submitted to the coin daemon. When this succeeds the block has been mined and the block reward is given to the submitter of the block - the pool. This worked fine. What went wrong is, that after submitting a block we also request the block's coinbase transaction hash from the daemon to track the confirmation progress. For some unknown reason this hash was not returned by the daemon for those last ten blocks. A coding error in the pool - introduced yesterday - caused the entire block to be regarded as orphaned because of the missing transaction hash and thus the block got not listed. It was simply forgotten. The code was reverted to the less strict block submission success check. Seven of the ten blocks have fully been paid already and the other three blocks are in their unlock stage.
My apologies for this mess!
I scoped this site a little while back, and the XMR hash rate was under 40kh/s. its now over 100 with the shutdown of another pool. Here's the thing. this pool found a block on average once a month with that low hash rate. A pool with 1Mh finds a block roughly every day, so by that token a small pool with 1 tenth the hash power should find a block every 10 days. I've been here a week, and before that it said last block was found a month ago. so you have a months worth of hashing at 20-50kh/s plus the last few days of 100kk/s+. what is the current effort % on that. because it seems like we should be over 500%. (I've never gone above 420% without finding a block, but that's just me) also, does this site report orphans? (also they found 5 blocks, all 2 months ago, whats up with that. was there alot of hashing power here at one time?)
Customer support service by UserEcho