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

[TTravis]

You will get a lot of disconnects when first starting p2pool as many peers are dropped for using outdated p2pool software, as well as having to download the share chain. You also need to allow port 9333 through your firewall & router to the host running p2pool.

Just start it normally and wait a while - the errors will gradually stop as it settles & finds good nodes to download the chain from.

Thanks,  will do.

[1713883306]

1713883306

[1713883306]

1713883306

[p3yot33at3r]

You will get a lot of disconnects when first starting p2pool as many peers are dropped for using outdated p2pool software, as well as having to download the share chain. You also need to allow port 9333 through your firewall & router to the host running p2pool.

Just start it normally and wait a while - the errors will gradually stop as it settles & finds good nodes to download the chain from.

Thanks,  will do.

No problem. It can be a little disconcerting when p2pool is started up for the first time, but as your node gradually downloads the chain the errors will stop - but it does take a while  

Currently the share chain is at 17372 - you should see shares on your node gradually increasing.......

[Meuh6879]

yep, i confirm this (lot disconnexion because of no valid v14 p2pool client).
but, it's not a problem if shares rise ... like 4000 shares after 15min (not verified !).

[TTravis]

You will get a lot of disconnects when first starting p2pool as many peers are dropped for using outdated p2pool software, as well as having to download the share chain. You also need to allow port 9333 through your firewall & router to the host running p2pool.

Just start it normally and wait a while - the errors will gradually stop as it settles & finds good nodes to download the chain from.

looks like it is working now.  I have much to learn here.

Now, I need someone to point me in the direction of Kano's custom firmware for AntMiners.

29)=0.0029 BTC
2015-11-15 17:37:45.052459  Pool: 866TH/s Stale rate: 15.5% Expected time to block: 3.8 days
2015-11-15 17:37:48.058576 P2Pool: 17312 shares in chain (9109 verified/17316 total) Peers: 7 (0 incoming)
2015-11-15 17:37:48.059197  Local: 1333GH/s in last 10.0 minutes Local dead on arrival: ~2.2% (1-4%) Expected time to share: 1.9 hours
2015-11-15 17:37:48.059365  Shares: 3 (0 orphan, 0 dead) Stale rate: ~0.0% (0-57%) Efficiency: ~118.3% (51-119%) Current payout: (0.0029)=0.0029 BTC
2015-11-15 17:37:48.059535  Pool: 866TH/s Stale rate: 15.5% Expected time to block: 3.8 days
2015-11-15 17:37:49.446352 Peer sent entire transaction 169eb6acb29de5402d66bc707ac356c5a68cad42cd3e2b61cd7982da8e39f9d6 that was already received
2015-11-15 17:37:51.064183 P2Pool: 17312 shares in chain (9109 verified/17316 total) Peers: 7 (0 incoming)
2015-11-15 17:37:51.064321  Local: 1332GH/s in last 10.0 minutes Local dead on arrival: ~2.2% (1-4%) Expected time to share: 2.0 hours
2015-11-15 17:37:51.064390  Shares: 3 (0 orphan, 0 dead) Stale rate: ~0.0% (0-57%) Efficiency: ~118.3% (51-119%) Current payout: (0.0029)=0.0029 BTC
2015-11-15 17:37:51.064465  Pool: 866TH/s Stale rate: 15.5% Expected time to block: 3.8 days


Is 866 TH/s hash rate normal, or is it down because of some kind of change in software version?

If the numbers look good to me, compared to AntPool which I am using now, I'll bring over about 150 TH/s.

Thanks Everyone,

Tom

[p3yot33at3r]

Yeah, the hash rate is correct, it has been jumping about quite a lot lately. What version of antminer are you using?

https://github.com/kanoi/cgminer-binaries

[TTravis]

Yeah, the hash rate is correct, it has been jumping about quite a lot lately. What version of antminer are you using?

https://github.com/kanoi/cgminer-binaries

I've got 1-S3, 2-S3+, 120-S5, and 8-S7, all with stock Bitmain firmware.  Right now I am pointing the S3's to p2pool while testing.

I am ordering at least 4 more S7's when they become available.

Tom

[p3yot33at3r]

Cool 

kano has binaries for the S1,2 & 3 at the link I posted. For the S5 I use this one:

https://www.dropbox.com/s/gk6gva5e12g4qsr/SD-S5-20150107_cgm_4_9_0-queue_0_no-submit.tar.gz?dl=0

..but unfortunately there isn't one for the S7 - yet.....(subtle hint for king kano  )

[TTravis]

Cool 

kano has binaries for the S1,2 & 3 at the link I posted. For the S5 I use this one:

https://www.dropbox.com/s/gk6gva5e12g4qsr/SD-S5-20150107_cgm_4_9_0-queue_0_no-submit.tar.gz?dl=0

..but unfortunately there isn't one for the S7 - yet.....(subtle hint for king kano  )

So what do these binaries do for me?  Would I still be able to mine on AntPool in case of failover?

[p3yot33at3r]

They re-enable cgminer to submit stale shares, as p2pool can find blocks with stale shares - as well as other stability improvements. And yes, you can use them on other pools too, no problem, but you're better off failing over to another p2pool node really, as your shares are stored in the p3pool share chain & can be transferred to any node - thus you won't lose any if your node goes down.

All clever stuff 

[p3yot33at3r]

Regarding the latest Bitcoin Core version 0.11.2 - I've been running it on my node with the latest p2pool git version for over 24 hours now without issue, it runs fine & is finding shares.

Matt has also released a new version of the relaynetworkclient, which is also running well.

Nice to wake up to another BLOCK! 

[wariner]

I think it is important to warn:

Code:

 +VERSION_CHECK = lambda v: None if 110200 <= v else 'Bitcoin version too old. Upgrade to 0.11.2 or newer!' 

upgrade your bitcoin core to 0.11.2

https://github.com/p2pool/p2pool/commit/482f410b0f48696901ae2a732450d02a27c0edc6

[Carlton Banks]

I think it is important to warn:

Code:

 +VERSION_CHECK = lambda v: None if 110200 <= v else 'Bitcoin version too old. Upgrade to 0.11.2 or newer!' 

upgrade your bitcoin core to 0.11.2

https://github.com/p2pool/p2pool/commit/482f410b0f48696901ae2a732450d02a27c0edc6

0.10.4 will handle v4 blocks also. Difficult to justify 0.10.x these days, but possibly some still mine with it (some still probably mine with 0.9.5, although not for much longer)

[TTravis]

I am up and running with p2pool now.  Someone please check me out to see if everything looks good.

I have a Dell Percision 390 w/ 8GB memory and 250 GB SSD running latest bitcoin core and p2pool 14.0-25-g482f410.

bitcoin.conf has only three lines:  server=1, rpcuser, and rpcpassword.

I am running on a T1 connection with everything connected to local node on network.
bitcoin client shows 42 active connections
p2pool shows 6 out, 2 in

Right now local rate shows 76 TH/s which is a little less that what I normally see on "that bug pool".


I have Antminers connected, all with standard firmware and settings.  3-S3's, 1-S4, and 77-S5's

I am looking for suggestions as to parameters for bitcoin.conf, or anything else that will help me run better.
Should I be looking at something called a relay node for better performance?

My p2pool address is: bitcoin.computing-management.com:9332

What would you do?

Thanks,

Tom

[Richy_T]

I am up and running with p2pool now.  Someone please check me out to see if everything looks good.

I have a Dell Percision 390 w/ 8GB memory and 250 GB SSD running latest bitcoin core and p2pool 14.0-25-g482f410.

bitcoin.conf has only three lines:  server=1, rpcuser, and rpcpassword.

I am running on a T1 connection with everything connected to local node on network.
bitcoin client shows 42 active connections
p2pool shows 6 out, 2 in

Right now local rate shows 76 TH/s which is a little less that what I normally see on "that bug pool".


I have Antminers connected, all with standard firmware and settings.  3-S3's, 1-S4, and 77-S5's

I am looking for suggestions as to parameters for bitcoin.conf, or anything else that will help me run better.
Should I be looking at something called a relay node for better performance?

My p2pool address is: bitcoin.computing-management.com:9332

What would you do?

Thanks,

Tom

If you go back the past few pages, there are some settings that should improve bitcoind's memory usage.

You might also consider upgrading to custom firmware on your miners. There are some changes that make things work better with p2pool. Details a few more pages back.

[windpath]

I am up and running with p2pool now.  Someone please check me out to see if everything looks good.

I have a Dell Percision 390 w/ 8GB memory and 250 GB SSD running latest bitcoin core and p2pool 14.0-25-g482f410.

bitcoin.conf has only three lines:  server=1, rpcuser, and rpcpassword.

I am running on a T1 connection with everything connected to local node on network.
bitcoin client shows 42 active connections
p2pool shows 6 out, 2 in

Right now local rate shows 76 TH/s which is a little less that what I normally see on "that bug pool".


I have Antminers connected, all with standard firmware and settings.  3-S3's, 1-S4, and 77-S5's

I am looking for suggestions as to parameters for bitcoin.conf, or anything else that will help me run better.
Should I be looking at something called a relay node for better performance?

My p2pool address is: bitcoin.computing-management.com:9332

What would you do?

Thanks,

Tom

Looking good Tom, congrats!

Everything looks pretty solid in your stats except for your efficiency.

It looks like you would benefit from finding some closer p2pool peers, your ping times are a little high and may be the cause of your orphaned shares: http://bitcoin.computing-management.com:9332/pings

Your getblocktemplate latency looks about normal, which would indicate that your bitcoin.conf may not be worth playing with. If you want to give it a try here are some pretty aggressive settings:

Code:

blockmaxsize=750000
mintxfee=0.0001
minrelaytxfee=0.0001
limitfreerelay=5
maxconnections=15

Matt's relay network certainly can not hurt, however it's slightly redundant in p2pool because the p2pool network is it's own relay network (thats why we have so few orphans).

[TTravis]

Thanks guys.  I am trying to read up on the past year.  I want to get things running as well as I can before I bring over the other half of my hash.

I will take put in the above mentioned changes for bitcoin.conf.  I have a feeling that leaving it open ended is taking up too much bandwith.

I'll do some research and find out what peers might be better.  Where do you specify the list of peers?

I have not yet found the custom firmware for AntMiner S5 and S7.  I didn't think it existed.  If someone could point me there, I would appreciate.

[jonnybravo0311]

As far as I know, there is currently no custom firmware for the S7.  The S5, however, does have updated firmware.  It's based on cgminer 4.8.0.  You can find it here: https://www.nicehash.com/sw/SD-S5-20150415_nicehash_perf_graphs.tar.gz.  I'm not sure, but there might be another version for the S5 around somewhere... the one I linked above is from NiceHash and provides extranonce support along with some graphs.

[Richy_T]

This is the one I'm using for my S5. Seemed to show some improvement for me though that could be because the pool hash rate is dropping and I have a bigger share.

https://bitcointalk.org/index.php?topic=18313.msg12983474#msg12983474

[p3yot33at3r]

As far as I know, there is currently no custom firmware for the S7.  The S5, however, does have updated firmware.  It's based on cgminer 4.8.0.  You can find it here: https://www.nicehash.com/sw/SD-S5-20150415_nicehash_perf_graphs.tar.gz.  I'm not sure, but there might be another version for the S5 around somewhere... the one I linked above is from NiceHash and provides extranonce support along with some graphs.

If I remember correctly, that nicehash version does not submit stale shares.....

Yup, here it is:

https://bitcointalk.org/index.php?topic=18313.msg12695616#msg12695616

[windpath]

...
I'll do some research and find out what peers might be better.  Where do you specify the list of peers?
...

Peers are added on the command line with the -n flag (note: if they use a custom port, include it ip_address:port).

Example:

Code:

./run_p2pool.py --address your_payout_address --outgoing-conns 10 -n 54.235.94.19 -n another_ip -n annother_ip rpc_user rpc_pass

Open source node scanner:
https://github.com/litecoin-project/p2pool-scanner

Online implementation of above:
http://p2pool.co/