I went back to MC for ~ one day, 2 days ago, after a mistake in estimating the gains from the main graph. I "got" half what I got at Waffle in the last ~24 hours. I said "got" because everything is in unexchanged, and god only knows when and how much I will be paid. Take a look at pool picker, MC has been largely underperforming over the last 10 days. Of course3 you can stay there because you like it and there's no argument about that. But saying that all pools perform the same is just not facts, at least over periods like the last week or 10 days.

I guess it depends what he calls payout. If it's the balance at the end of the payday (the red number in the graph), then it would be wrong and off by ~30%. If he somehow sums up every actual single user payout (or has access to it otherwise), then that would be accurate. With the numbers a quote in the post at 07:31:21, it looks like he is looking at the right payout (contrary to what I was doing  )

I just noticed on the main graph that the total BTC (all users) does not go back to 0 at the end of the pay day, even far from it (~ 80-90 BTC maybe). I actually looked at that graph the last few days and that's why I decided to mine again at MC, thinking the pool was getting at least 0.01 BTC/(Mh/s)/day (170-200 BTC/day for ~14000Mh/s). It seems that I actually got much less than that the last 12 hours; I probably made a mistake in estimating the perfs per day by not paying attention to the initial BTC at the beginning of the day.

So I first thought there was a bug with the graph, and then I though: do all these BTC not being paid every day come from many users with very small balance? I know I've had one for a few days. I guess you'd need quite a few users with a balance less than 0.01 BTC (~8000 ?).

>>>>>  Limited time offer <<<<<<<<
!!! 0.03 BTC for an invitation to a pool twice as fast as SimonG's !!!

But wait!! Just for today, for the same low price of 0.03 BTC you get two pools  ... that's right! two pools for the price of one! So don't waste a second and get to your bitcoin wallet!

"The cake is a lie" ... don't contact me!

Can you turn down your ad a notch please, it is very distracting.

Over the last 3 days I've got an average of ~0.0178 BTC per day. At today's rate that's ~$15/day, with 1.8Mh/s (about 1.3% rejects).
Would you mind sharing your address? I would like to see the difference in the patterns, if any?

I am not sure why their unexchanged will grow differently (with the assumption that all server mine and trade exactly the same). I know that, sometimes, some trades randomly get stuck in the exchanges (i.e. Crypsty from my personal experience) and they need manual intervention (i.e. cancel and resubmit). Maybe it is something like that.

As for the perfs of the past few days, I have noted several days when you had larger payouts, eg. Jan 6th or a few days before. (although, to be fair, it looks like their hashrate decreased a bit compared to yours). It would require careful examination for each day to be sure, and I do not have much time right now ... but it seems to me that, at least for your example of the last day, your total gains increased very similarly to theirs, contrary to what it may have looked like at first glance.

Cheers.

They started the day with way more unexchanged than you it looks like (something like 0.09). So it looks like the gain for today is similar, no?

Hi,

I have been having an accepted MH/s around 1.8 MH/s on average since starting mining on that multipool a few days ago. But suddenly, during the last hour or so, it has been dropping continuously (now at 0.5686 MH/s). Everything seems fine on my miner side:

WU =  1655.3/m
<5s>: 1.802M, :1.814Mh/s
Lots of "Accepted" rolling up ... All HW = 0.

Any idea what could cause something like that? I know that sometimes share can be not accepted for various reasons, but I was under the impression that at least WU number and accepted shares on the pool side should always be kind of consistent with each other.

Since starting to write this post, the rate seems to climb back up a bit. So I guess I'll keep the panic at bay for now I am just trying to understand how that could work. Just a frontend issue maybe?