Quote from: vaelrock on December 23, 2013, 09:00:38 PM

Quote from: zvs on December 23, 2013, 08:36:54 PM

Quote from: vaelrock on December 23, 2013, 08:05:03 PM

Quote from: zvs on December 23, 2013, 07:54:28 PM

Quote from: dr blowfin on December 23, 2013, 07:06:19 PM

So we got pools down, pools that constantly lose connection, pools with missing coins and pools only paying out 20% of correct rewards...yet difficulty is now over 30. WTF is going on?

You'd have to be crazy to be pool mining this so must be some serious solo mining going on.

yeah, i've had a pool at 0% fee running since hour 2

i havent had any issues

i'm at >40m .. with about 1.5mhash

though not that having these serves any real purpose (i think almost time to switch back to my doge p2pool)

And what pool is it ? I also mined on a p2pool for 6 hours and miss multiple millions TIPS. Is there a magical way to determine in advance that the pool you're gonna mine on is not bugged/a scam ?
Because they all use the same templates so you cannot even judge by their appearance.

Edit : seems you are the operator of the pool I'm speaking of. I mined from ~9:30 AM UTC to 15:30 AM UTC on your pool with 9MH/s and got ~800k TIPS. diff was between 10 and 20, so I should have get at least 4 to 5 millions. What happened ?

Edit 2 : I still appear in your page in the "payouts if a block were found now" section. Am I getting paid even 4 hours after stopping ? I don't get it.

Edit 3 : I'm still receiving payment from what seems to be your pool, 600k more. So I really don't get it.

I nigger-rigged it w/o restarting p2pool so you can look at each individual block on the new block explorer. Click on them and it shows who got what.

You're definitely not missing multiple millions of TIPS... it's set to a 60 block range, if you just started mining and, say, 10 minutes had passed, then you'd theoretically only get 1/6th of what you'd get if you had been there a full hour... re: difficulty is supposed to adjust so that there is a block every 60s. on the flip side, after you leave, you'll still get stuff for that 10m you were there for another 50m.. assuming you got any shares. there are two values... one is the difficulty it uses to show your hash rate on the graph and one is the difficulty that will show up as a share in the share explorer

they show up as immature until confirmed

http://nogleg.net:1911/fee

a block

http://fedorachain.info/block/6681f404a4f810f3ddc31a6ae2ca2aa5347e035e0bbe0323be91abecf4dd2547

go look at the earlier ones if you think you're missing something

and it's not being run on a VPS

ed: maybe you need to download the new client, it was giving out 1/5th value before

Ok so I looked precisely at the block history, and here is the explanation :
Just after joining the pool, 4 blocks were found, which is extremely lucky for your pool. Because I joined less than 30mn before, I got paid much less. This is normal to avoid pool hoping, I understand that.
But after, blocks were found a lot less as the difficulty greatly increased, and people leaved the pool probably for this very reason (from ~80MH/s to currently ~20MH/s).
So because I had a great hashrate contribution, I'm still getting paid with the newer blocks found, but as they are less and less common, the payment are farther and farther away one from another.
I'm currently at ~1.5M from your pool, so the explanation is a combination luck/payment method/payment interval due to the difficulty increase and the current lack of hashrate on your pool.

Everything seems to fit, I apologize for having put in doubt your pool.

What probably explains why people are leaving your pool is the fact that you can get paid multiple hours after. Standard PPLNS/PPS/Prop pools are much faster, so if you don't have the tool to check, you can believe in a scam. And because of that, people will really never get paid due to the fact that no new block will ever be found with just a few MH/s

yeah, the pool was super lucky for the first... 12 hours or so? now it's been, hmm, I wouldn't say super unlucky, but unlucky for the last 6-8 hours (0 blocks). it should still be getting a block every 3 hrs or so. I just moved my miners off of it to go back to DOGE (it was at .00000080 or w/e), so now maybe it's every 4 hours.. but if I adjusted the settings now, then it'd screw everyone that mined earlier. on the flip side, nobody will want to mine on it if it only solves a block every couple hours and it takes them days to reach full share. with current setting it really needs a block every 30-45m.

this problem is also partially due to client not handling difficulty correctly. it's supposed to solve a block every 60s. that's why I set it the way I did

This isn't every minute Grin

12/24/13 04:36:42 received block e13d65ca168ac7605d14 from 108.x.x.x:xxxx
12/24/13 04:45:33 received block 7ff03e212c7f149b3296 from 74.x.x.x:xxxx
12/24/13 04:48:33 received block f801b2c1ae779b7bb55c from 50.x.x.x:xxxx
12/24/13 04:49:16 received block dfe07351334d719470b2 from 86.x.x.x:xxxx
12/24/13 04:51:31 received block 5ada86d4e51dbec56e8a from 86.x.x.x:xxxx
12/24/13 04:56:51 received block dbe16715da8c609d5cb4 from 86.x.x.x:xxxx
12/24/13 04:57:39 received block ec62a0121a3e77083262 from 81.x.x.x:xxxx
12/24/13 05:00:46 received block 206e99a105fa84984218 from 207.x.x.x:xxxx
12/24/13 05:00:57 received block 24411adae366b870deb5 from 207.x.x.x:xxxx
12/24/13 05:04:21 received block 6dbe8778fb9f98aaa6a5 from 50.x.x.x:xxxx
12/24/13 05:04:49 received block a88c6f4422f74eb84538 from 81.x.x.x:xxxx
12/24/13 05:11:00 received block 2ff479fecabc859912cd from 50.x.x.x:xxxx
12/24/13 05:13:25 received block c4cb08265267b2a89a39 from 50.x.x.x:xxxx
12/24/13 05:13:32 received block 0552235b4a8c79cd66f9 from 50.x.x.x:xxxx
12/24/13 05:21:23 received block 9609e87c7ac0e8b61066 from 50.x.x.x:xxxx
12/24/13 05:22:32 received block 9819758f9e4ff9659848 from 50.x.x.x:xxxx
12/24/13 05:32:56 received block b8ce3b7a48dd35f5da47 from 50.x.x.x:xxxx
12/24/13 05:33:38 received block 654528c034a3a27626e2 from 81.x.x.x:xxxx
12/24/13 05:35:52 received block 76d12d9cc072f48d0476 from 207.x.x.x:xxxx

(and so if you are running a pool you should be connected to this 207, 50, 86, and 81)