Topic: P2Pool 0 shares, i need help <<resolved>> (Read 1297 times)

Hi, I found similar issues with p2pool and 10 GH hasrate ie low. It's all inside a really big forum. However I will quote from here for ease of reading:-

Quote from https://bitcointalk.org/index.php?topic=18313.6820 Page 342

I started asking questions a few pages earlier btw

I've copied my final summery here for your ease to read:-


Quote from: Rluner on October 25, 2013, 04:59:16 PM


After around 1 week of solid processing at 10 gh/s via p2pool network I received 0.00337845 BTC; after missing 16 block payouts in a row.
I'm sorry to say this can't be giving me my fair share for my work done on the p2pool network so I have moved off it.

You may have something wrong with your miner setup, or with the pool you're using - how many p2pool 'shares' did you submit ?

There is some element of 'randomness' - but a week of 15Gh/s has found 17 P2Pool-type 'shares' and apart from the 2 days when that miner had found no p2pool-shares, I've been paid on every block found.

Thanks for all the responses. It's good to get feed back.

My miner setup was working perfect before the difficulty rose to 268 m. I was running my own p2pool client, efficiently was near perfect, stall rate was virtually zero, DOA was zero. I was able to find a share in nearly every block and got paid out nearly every time. I think I missed two payouts in about twenty, but I hadn't found a share so I knew that was correct too.

As soon as the difficulty rose to 268 m without anything changing at my side (after three months working perfectly) I stopped receiving payouts. After a week I ended up with one pay out of a very low amount as previously wrote in a previous post, but p2pool has paid out about 17 times. I had noticed that I couldn't get a successful share before the pool solved a block and when I did manage to get two , one was orphaned. That's when I got my only payout in a week.

Summery....

After a week of running at 268 m I have to say p2pool did not work for my 10 gh processing.

It had worked perfectly below 268m difficulty, my payouts were nearly ever time and perfect amounts as I calculated from inputting numbers into online calculators.

The problem seems to me that my 10 gh can't get a share fast enough for the network, but although I was informed when I did get a share I would get my fair share I clearly didn't.

Also I have to add, at the same time I had another 10 gh in another pool, not p2pool, and this paid what I would have expected, over the same time period.

I end by saying I believe in the p2pool idea, and I thank the coders, but I also believe as the difficulty rises more low hashing users may have to leave p2pool network due to the issues I have mentioned.

thanks zvs

Yah, just the low hash rate.  You can change your share difficulty, but only make it higher than whatever p2pool's default target is atm, not lower..

i.e.  bitcoinaddress/500000+50

makes your target share difficulty 500k instead of 150-200k or whatever it's currently at..  the 2nd amount is what the website or whatever uses to track your hashrate

I sometimes still point my gfx card on my main computer to a p2pool & I use 500000+5, re: just trying to get lucky & having a low enough 2nd value so it'll report my hashrate somewhat accurately

I saw something on the forums about changing the difficulty and thought that was relevant for me. So it's just because I have a pitifully slow hash rate?
OK. I guess I'll go to a pool, I would have liked to have made some BTC while supporting decentralisation.

two block erupters, 660mhash or so, well, you can see the expected time to share there:  10 days

i wouldn't use p2pool if i was under 10ghash, unless it was just for kicks (trying to get lucky or something like that)

Hi people.
I hope someone can help me out.
I am running p2pool with 2 block erupters I have 0 shares and suspect maybe I need to change my share difficulty?
Here is what my console is saying

2013-11-09 17:21:19.904019 P2Pool: 17426 shares in chain (10412 verified/17430 total) Peers: 8 (0 incoming)
2013-11-09 17:21:19.904240  Local: 663MH/s in last 2.4 minutes Local dead on arrival: ~85.2% (67-95%) Expected time to share: 10.0 days
2013-11-09 17:21:19.904393  Shares: 0 (0 orphan, 0 dead) Stale rate: Efficiency: Current payout: 0.0000 BTC
2013-11-09 17:21:19.904528  Pool: 35254GH/s Stale rate: 17.2% Expected time to block: 17.3 hours


that local dead on arrival is new, I accidentally ctrl-c and closed the connection which has been open since yesterday some time.

Please help!