[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool

[azw409]

I love P2Pool and having been running it for a while but I have a pretty marginal rig at around 700MH/s and with the latest hike in difficulty I'm just not getting any shares any more. I'm sure I will at some point but knowing my luck that will happen with P2Pool to fails to find a block and so all that hashing effort will be wasted.

Is it possible to lower the share difficulty so smaller miners are still getting regular shares albeit smaller ones ? I'm assuming that would be a fundamental change to the P2Pool source that will be incompatible with other P2Pool nodes out there ? If so, would it be possible to create a fork, say EasierP2Pool and recruit enough participants ?

Thanks

[mdude77]

I love P2Pool and having been running it for a while but I have a pretty marginal rig at around 700MH/s and with the latest hike in difficulty I'm just not getting any shares any more. I'm sure I will at some point but knowing my luck that will happen with P2Pool to fails to find a block and so all that hashing effort will be wasted.

Is it possible to lower the share difficulty so smaller miners are still getting regular shares albeit smaller ones ? I'm assuming that would be a fundamental change to the P2Pool source that will be incompatible with other P2Pool nodes out there ? If so, would it be possible to create a fork, say EasierP2Pool and recruit enough participants ?

Thanks

At 700MH/s, your best bet is to retire or go to another pool like BTC Guild.  I'm at about 7.5GH/s and my estimated time to share is 2.9 hours.  You're looking at around 31 hours per share, and with variance, there will be days when you don't get a share at all.

M

[centove]

I keep getting this spamming my p2pool node's terminal window.  Happens every 3-5 seconds:

Code:

2013-08-14 08:55:53.386000 >   File "p2pool\util\deferred_resource.pyc", line 24
, in render
2013-08-14 08:55:53.387000 >
2013-08-14 08:55:53.388000 >   File "twisted\internet\defer.pyc", line 134, in m
aybeDeferred
2013-08-14 08:55:53.389000 >
2013-08-14 08:55:53.390000 >   File "twisted\web\resource.pyc", line 216, in ren
der
2013-08-14 08:55:53.391000 >
2013-08-14 08:55:53.392000 >   File "twisted\internet\defer.pyc", line 1187, in
unwindGenerator
2013-08-14 08:55:53.393000 >
2013-08-14 08:55:53.393000 > --- <exception caught here> ---
2013-08-14 08:55:53.393000 >   File "twisted\internet\defer.pyc", line 1045, in
_inlineCallbacks
2013-08-14 08:55:53.394000 >
2013-08-14 08:55:53.395000 >   File "p2pool\web.pyc", line 186, in render_GET
2013-08-14 08:55:53.395000 >
2013-08-14 08:55:53.395000 >   File "p2pool\web.pyc", line 446, in <lambda>
2013-08-14 08:55:53.396000 >
2013-08-14 08:55:53.396000 > exceptions.KeyError: 'last_'

Everything seems to work OK, but I don't know what this error means.  Only started yesterday.

Are you getting shares or lots of rejects (in the miner software) I switched to cgminer 3.3.3 and started seeing these and every thing was being rejected. Switched back to cgminer 3.3.1 and all was well again.

[rav3n_pl]

333 is bugged, use 332 or 334

[AtomSea]

I've been reading this thread daily for awhile now - very nice. (borat accent)

Yeah, for real, can someone point me to a link that can help me merge mine Namecoin on our p2p pool node?

Talk nerdy to me.

Thank you.

[daemondazz]

I've been reading this thread daily for awhile now - very nice. (borat accent)

Yeah, for real, can someone point me to a link that can help me merge mine Namecoin on our p2p pool node?

Talk nerdy to me.

Thank you.

Just add this to the end of your p2pool command line (replacing username, password and 7333 with your namecoind user/pass and RPC port):

Code:

--merged http://username:password@127.0.0.1:7333/

Not particularly hard

[Ghost of USD]

Cool, we just mined a block with 10.14311847 BTC in transaction fees

https://blockchain.info/block-index/406373/000000000000001514684f6f04348420660fa46ff02b36104623f9fcdfc75052

[yxxyun]

Cool, we just mined a block with 10.14311847 BTC in transaction fees

https://blockchain.info/block-index/406373/000000000000001514684f6f04348420660fa46ff02b36104623f9fcdfc75052

Cool. Generation: 25 + 10.14311847 total fees.

[HellDiverUK]

I keep getting this spamming my p2pool node's terminal window.  Happens every 3-5 seconds:

Code:

2013-08-14 08:55:53.386000 >   File "p2pool\util\deferred_resource.pyc", line 24
, in render
2013-08-14 08:55:53.387000 >
2013-08-14 08:55:53.388000 >   File "twisted\internet\defer.pyc", line 134, in m
aybeDeferred
2013-08-14 08:55:53.389000 >
2013-08-14 08:55:53.390000 >   File "twisted\web\resource.pyc", line 216, in ren
der
2013-08-14 08:55:53.391000 >
2013-08-14 08:55:53.392000 >   File "twisted\internet\defer.pyc", line 1187, in
unwindGenerator
2013-08-14 08:55:53.393000 >
2013-08-14 08:55:53.393000 > --- <exception caught here> ---
2013-08-14 08:55:53.393000 >   File "twisted\internet\defer.pyc", line 1045, in
_inlineCallbacks
2013-08-14 08:55:53.394000 >
2013-08-14 08:55:53.395000 >   File "p2pool\web.pyc", line 186, in render_GET
2013-08-14 08:55:53.395000 >
2013-08-14 08:55:53.395000 >   File "p2pool\web.pyc", line 446, in <lambda>
2013-08-14 08:55:53.396000 >
2013-08-14 08:55:53.396000 > exceptions.KeyError: 'last_'

Everything seems to work OK, but I don't know what this error means.  Only started yesterday.

Are you getting shares or lots of rejects (in the miner software) I switched to cgminer 3.3.3 and started seeing these and every thing was being rejected. Switched back to cgminer 3.3.1 and all was well again.

I don't think it was anything to do with miners - I had nothing mining on the node at the time.  Besides, I use bfgminer.  Rejects and stales were at zero, as usual for my node.

Restarting both p2pool and bitcoind seems to have fixed the problem. 

[AtomSea]

I've been reading this thread daily for awhile now - very nice. (borat accent)

Yeah, for real, can someone point me to a link that can help me merge mine Namecoin on our p2p pool node?

Talk nerdy to me.

Thank you.

Just add this to the end of your p2pool command line (replacing username, password and 7333 with your namecoind user/pass and RPC port):

Code:

--merged http://username:password@127.0.0.1:7333/

Not particularly hard

You're hired.

[ksenter]

I just got my little single.  It arrived a little less than half an hour ago, it literally took me about 5 minutes to set it up and get it mining on p2pool.  Admittedly I've been reading this thread, and the cgminer thread for a long while, and had already downloaded the latest p2pool, cgminer and zadig, and had been mining on p2pool with my GPUs for a while.  But really, you guys have made this incredibly easy.  Thanks so much everyone for all of your hard work!  I'll be donating some btc your way once I've mined some.  Who all should I donate to, forrestv, kano, ckolivas, anyone else?

So far everything is looking good.  I'm getting right at 30GH give or take a GH, temp is 56-57C.  It was a little hotter and a little louder but I took the grates off of the fans like other people had said on the BFL forums, and that made it a little less whiny (if not quieter) and a couple of degrees cooler.

Anyway thanks again everyone!

[freshzive]

what's up with my node displaying much higher pool hashrates than p2pool.info?

for example right now my node says 6.07TH/s and p2pool.info reads closer to 5.2TH/s

[mdude77]

what's up with my node displaying much higher pool hashrates than p2pool.info?

for example right now my node says 6.07TH/s and p2pool.info reads closer to 5.2TH/s

I think p2pool.info is referencing nodes on another fork.

M

[daemondazz]

what's up with my node displaying much higher pool hashrates than p2pool.info?

for example right now my node says 6.07TH/s and p2pool.info reads closer to 5.2TH/s

I think p2pool.info is referencing nodes on another fork.

The "other fork" is only in the 10's of GH range (last I saw) not the TH range, so it's more likely it's just estimating the network rate a bit differently than fresh's local node.

For reference, my local node is currently showing a network rate of 5.93TH/s. It does vary a bit as hardware is added and removed, etc.

[twmz]

what's up with my node displaying much higher pool hashrates than p2pool.info?

for example right now my node says 6.07TH/s and p2pool.info reads closer to 5.2TH/s

I think p2pool.info is referencing nodes on another fork.

The "other fork" is only in the 10's of GH range (last I saw) not the TH range, so it's more likely it's just estimating the network rate a bit differently than fresh's local node.

For reference, my local node is currently showing a network rate of 5.93TH/s. It does vary a bit as hardware is added and removed, etc.

My p2pool node (which I don't use, personally, and so don't monitor closely) got hosed somehow and was in a non-stop error loop.  I killed it, git pull-ed, and restarted it and it looks like it is working again, although my node thinks the pool speed is about 4.6 TH/s.  If that is not what other people's nodes think, let me know.

PM me for faster service if you see any future problems

Update: P.S.  p2pool.info is showing the average hashrate over the past hour based on samples taken every 5 minutes.  So if hashrate spikes up briefly and then drops back to normal, you won't see the hashrate jump up as high on p2pool.info.

[DopeLabs]

so i convinced my brother to write a python script that will send an email (or an sms/mms if your provider has a gateway ex: 5551234567@vzwpix.com (verizon)) when you get a share and/or when a block is found. the message will tell you if its a share or a block, and also put in the current payout when either is found.

you can find it here:

http://gist.github.com/dreness/6247320

if you like it and feel like donating a buck or two, send to the address in my sig and i will give him the cash personally.

cheers!!

[elebit]

I love P2Pool and having been running it for a while but I have a pretty marginal rig at around 700MH/s and with the latest hike in difficulty I'm just not getting any shares any more.

Sooner or later you should get one. It should all even out in the long run.

Of course, if you start getting shares once a week or something then it's time to switch pool, but it can't be that bad..?

[kano]

I love P2Pool and having been running it for a while but I have a pretty marginal rig at around 700MH/s and with the latest hike in difficulty I'm just not getting any shares any more.

Sooner or later you should get one. It should all even out in the long run.

Of course, if you start getting shares once a week or something then it's time to switch pool, but it can't be that bad..?

700MH/s at currently 23400 difficulty is ...
23400 * 2^32 / (700 x 10^6) sec = 143574.6 sec = 39hrs 52min 55sec share average

[wtogami]

p2pool LTC shares are now 85% for version 13.  When it reaches 95%, older versions of p2pool will be permanently left behind.  p2pool-13+ requires litecoin-0.8.3.7+.  Please upgrade both immediately in order to avoid problems.

[freshzive]

I love P2Pool and having been running it for a while but I have a pretty marginal rig at around 700MH/s and with the latest hike in difficulty I'm just not getting any shares any more.

Sooner or later you should get one. It should all even out in the long run.

Of course, if you start getting shares once a week or something then it's time to switch pool, but it can't be that bad..?

700MH/s at currently 23400 difficulty is ...
23400 * 2^32 / (700 x 10^6) sec = 143574.6 sec = 39hrs 52min 55sec share average

how long does a share last in terms of payout? e.g. if you are getting 1 share every 2 days will you still be getting a payout for each block or will there be periods where your payout dips down to zero?