Closing down the pool (yes, again).
Two main reasons:
a) I believe bitcoin is dying a slow protracted death, with falling hashrates and falling values it's only a matter of time before it's gone entirely.
b) we had server issues which led to the outage earlier on today, but believed them to be fixed - sadly not and we're now at a state where the pool server won't boot properly, and given my position on a) I'm not willing to invest any more time in fixing this and carrying on running it just to have it all for nothing in what I suspect may be a matter of weeks.
There was one block which hadn't confirmed yet, once it has I'll get it paid out. All remaining balances will be paid out.
It ain't coming back this time, thanks for the hashes over the past few months.
Topic: [CLOSED] RFCPool.com - page 2. (Read 22121 times)
Yep, sorry, fairly major issues overnight and this morning, sorry about this. Our first serious downtime since we started though.
I'm aware of blocks #45 and #46 showing incorrect payouts, I'll fix this shortly.
I'm aware of blocks #45 and #46 showing incorrect payouts, I'll fix this shortly.
Website and API is down, maybe more but I can't check from my mobile.
Update 13:38h: Pool seems up and running again but now my unconfirmed balance is wrong; pending payouts for blocks #45 and #46 are missing. Please check.
Update 13:38h: Pool seems up and running again but now my unconfirmed balance is wrong; pending payouts for blocks #45 and #46 are missing. Please check.
I just died a little inside
How about average number of times a share was paid over the x number of blocks? For a pplns pool i think that's your best indictor of luck.
for example your luck from block 8 to block 17 was 1.09 or 109%
edit: unless you change N again in which case you'd be better of showing (average payouts per share)/N to keep average luck at 100%.
for example your luck from block 8 to block 17 was 1.09 or 109%
edit: unless you change N again in which case you'd be better of showing (average payouts per share)/N to keep average luck at 100%.
Three blocks isn't much to go on statistically.
One thing I need to do is make it easier to work out our luck over any defineable timeframe but I'm not sure how to implement it yet.
If someone gives me a decent idea on how to represent it then I'll code it up
Those graphs which show a moving line of luck on recent blocks aren't bad, but I kind of want a number rather than a graph, IYSWIM
One thing I need to do is make it easier to work out our luck over any defineable timeframe but I'm not sure how to implement it yet.
If someone gives me a decent idea on how to represent it then I'll code it up
Those graphs which show a moving line of luck on recent blocks aren't bad, but I kind of want a number rather than a graph, IYSWIM
Like BTCG % above or below diffculty - was calculated per difficulty ( was like that before they went pps)
They Also had 24h luck but I guess thats only good for a very big pool.
LOL. Did I say something about bad luck? Never mind. 
That'll teach you
LOL. Did I say something about bad luck? Never mind.
Three blocks isn't much to go on statistically.
One thing I need to do is make it easier to work out our luck over any defineable timeframe but I'm not sure how to implement it yet.
If someone gives me a decent idea on how to represent it then I'll code it up
Those graphs which show a moving line of luck on recent blocks aren't bad, but I kind of want a number rather than a graph, IYSWIM
One thing I need to do is make it easier to work out our luck over any defineable timeframe but I'm not sure how to implement it yet.
If someone gives me a decent idea on how to represent it then I'll code it up
Those graphs which show a moving line of luck on recent blocks aren't bad, but I kind of want a number rather than a graph, IYSWIM
Some ideas (if you really can't be dealing with charts):
1. Number of blocks found in last time period (week, month whatever) compared to expected
2. CDF (like Slush's pool)
3. Average shares per block/difficulty
I think the best looking thing would be a density plot of all round lengths compared to other pools, like this:
Three blocks isn't much to go on statistically.
One thing I need to do is make it easier to work out our luck over any defineable timeframe but I'm not sure how to implement it yet.
If someone gives me a decent idea on how to represent it then I'll code it up
Those graphs which show a moving line of luck on recent blocks aren't bad, but I kind of want a number rather than a graph, IYSWIM
One thing I need to do is make it easier to work out our luck over any defineable timeframe but I'm not sure how to implement it yet.
If someone gives me a decent idea on how to represent it then I'll code it up
Those graphs which show a moving line of luck on recent blocks aren't bad, but I kind of want a number rather than a graph, IYSWIM
Ok, conclusion after 6 days: the stale rate is still awesome (0.03%) but the pool seems to kind of unlucky. The last three blocks took longer then they should have. But hey, luck is a lady, I guess I'll stay. 
I want a cool banner thingie 
There's some kind of sorcery 
going on with the stales. I just don't get it.
going on with the stales. I just don't get it. As MMC closed over sudden its doors yesterday I switched to this pool and after my first day of mining I must say I'm loving it here. Great website and stats and even better: 24h of mining without a single stale share. Keep up the Good work!
Keep up the Good work!Awesome! Tell your friends. The more the merrier!
As MMC closed over sudden its doors yesterday I switched to this pool and after my first day of mining I must say I'm loving it here. Great website and stats and even better: 24h of mining without a single stale share. Keep up the Good work!
Keep up the Good work!
Considering it. I want to see if MM has some staying power before I invest man-hours into it.
Also we're looking at migrating to poolserverj and shadders is currently in the middle of implementing it in that; so once proven stable it shouldn't be too difficult to do anyway.
Also we're looking at migrating to poolserverj and shadders is currently in the middle of implementing it in that; so once proven stable it shouldn't be too difficult to do anyway.
Hat trick! 3 blocks today. Woot!
glad i switched at the right time but its so hard not to go back with merged mining. Any hope in enabling merged mining?Stop by our IRC chan. It's been discussed. Not sure the final verdict.
Hat trick! 3 blocks today. Woot!
glad i switched at the right time but its so hard not to go back with merged mining. Any hope in enabling merged mining?
Hat trick! 3 blocks today. Woot!
Jump to: