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

[iegservers]

Hey, I clicked on the open pool list on P2Pool.org.. and its blank.

http://p2pool-nodes.info/

It was populated the other day..

I just was looking at this my self to see if we were on the list. guess not lol

[1714260969]

1714260969

[1714260969]

1714260969

[1714260969]

1714260969

[Gamonics]

Just getting started with mining and curious about p2pool. What's the difference between these two projects?

https://github.com/forrestv/p2pool/graphs/contributors
https://github.com/Rav3nPL/p2pool-rav/graphs/contributors

Lots of other questions:

Are these just different implementations of the p2pool protocol?

Looks like forrestv's project's last release was in 2013. Does that indicate stable/finished software or does that indicate an abandoned project?

Rav3nPL's project seems to have more recent activity. Which project is better and why?

Are there other p2pool implementations aside from these two?

Is it possible to use Rav3nPL according to the guidance in http://p2pool.in/ ?

Which p2pool software project are most people using in Linux?

Thanks in advance for replies.

[jonnybravo0311]

Isn't it true that if you mine on a node with other people (in your local area, to keep latency down), you can reduce difficulty to get a share that way (as the entire node finds a share, and distributes it to the participants via a lower difficulty pps method)?

I see that to be a viable workaround to flaw #2 above. Sure, it might boost centralization a bit as miners conglomerate into local nodes, but as long as there are geographic distances between miners super-nodes (51% of hashrate) shouldn't exist due to latency.

If this has already been answered in the thread, sorry!  

No.

You can only lower your share difficulty to the network's determined difficulty.  You do this by using the "/" after your address.  This may sound confusing, but it's pretty easy in reality.

If the node you're mining on has a considerably higher hash rate than what you are contributing, then it is advantageous to you to tell the node you want to have the network minimum share value.  For example.  Let's say that I run my own node and I have 30TH/s on it.  If you bring a single S5 onto my node, then you should setup your user name like this: "MYBTCADDRESS/1000".  That "/1000" will ensure that the node will accept the minimum share difficulty for your miner - which right now is 3,200,000ish.  My 30TH/s miner, if I set the user name up like this: "MYBTCADDRESS", will assign me a share difficulty of about 14,000,000.

P2Pool assigns your miners difficulty based upon the node's total hash rate.  You override that value by using "/".

Hope that helps.

So I am on a node that has 10Th+ and I have a S5 there running at 500Gh so I should set it at  /? use 1000?

Left to its own devices a node will adjust the share time to 30 minutes.  Therefore if the node's total hash rate would find a share in under half an hour the node will adjust the share difficulty up so that it settles back to that 30 minute mark.

You override that by using the "/".  As long as you use any value that is less than the network minimum share difficulty your worker will submit the minimum share difficulty.  So... Using /1000 or /1 or /1000000 doesn't matter.

[windpath]

Just getting started with mining and curious about p2pool. What's the difference between these two projects?

https://github.com/forrestv/p2pool/graphs/contributors
https://github.com/Rav3nPL/p2pool-rav/graphs/contributors

Lots of other questions:

Are these just different implementations of the p2pool protocol?

Looks like forrestv's project's last release was in 2013. Does that indicate stable/finished software or does that indicate an abandoned project?

Rav3nPL's project seems to have more recent activity. Which project is better and why?

Are there other p2pool implementations aside from these two?

Is it possible to use Rav3nPL according to the guidance in http://p2pool.in/ ?

Which p2pool software project are most people using in Linux?

Thanks in advance for replies.

Rav3nPL's version is identical for bitcoin, however he includes support for many alt coins as well.

Forrest is basically inactive as far as development goes, the pool works just fine as long as you have enough has power to keep active shares in the chain.

I believe most implement the default code from Forrest's repository, usually with one of the optional front ends available.

[jonnybravo0311]

Just getting started with mining and curious about p2pool. What's the difference between these two projects?

https://github.com/forrestv/p2pool/graphs/contributors
https://github.com/Rav3nPL/p2pool-rav/graphs/contributors

Lots of other questions:

Are these just different implementations of the p2pool protocol?

Looks like forrestv's project's last release was in 2013. Does that indicate stable/finished software or does that indicate an abandoned project?

Rav3nPL's project seems to have more recent activity. Which project is better and why?

Are there other p2pool implementations aside from these two?

Is it possible to use Rav3nPL according to the guidance in http://p2pool.in/ ?

Which p2pool software project are most people using in Linux?

Thanks in advance for replies.

Rav3n's fork brings p2pool support for a bunch of alt coins.  The original project written by forrestv has only support for BTC and LTC.  Also, Rav3n's fork has a different front end.

EDIT: looks like windpath pushed the post button right before I did

[jonnybravo0311]

Alright... I've never seen this before.  Can somebody explain this from my logs:

Code:

2015-02-21 14:34:39.585148  Local: 46102GH/s in last 10.0 minutes Local dead on arrival: ~7.3% (5-10%) Expected time to share: 29.7 minutes
2015-02-21 14:34:39.585209  Shares: 136 (7 orphan, 12 dead) Stale rate: ~14.0% (9-21%) Efficiency: ~100.4% (92-107%) Current payout: 0.0000 BTC
2015-02-21 14:34:39.585311  Pool: 1025TH/s Stale rate: 14.3% Expected time to block: 2.2 days
2015-02-21 14:34:40.883225 Peer sent entire transaction bf60e45e409ed34fb9fc66c168f523c86573389cd036d762213944e2af0f25a8 that was already received
2015-02-21 14:34:42.635166 GOT SHARE! 1DeVLDoGvkbbB5n3dPvbpDbwiKGjYckCy9 8322ab0e prev 7d9ffbc9 age 86.38s DEAD ON ARRIVAL
2015-02-21 14:34:42.816110 New work for worker! Difficulty: 9881.151697 Share difficulty: 17750679.688090 Total block value: 25.219599 BTC including 1397 transactions
2015-02-21 14:34:42.960120 New work for worker! Difficulty: 500.000000 Share difficulty: 3738875.477555 Total block value: 25.219599 BTC including 1397 transactions
2015-02-21 14:34:43.094841 New work for worker! Difficulty: 256.000000 Share difficulty: 17750679.688090 Total block value: 25.219599 BTC including 1397 transactions
2015-02-21 14:34:43.240753 New work for worker! Difficulty: 9881.151697 Share difficulty: 17750679.688090 Total block value: 25.219599 BTC including 1397 transactions
2015-02-21 14:34:43.407120 P2Pool: 17397 shares in chain (17401 verified/17401 total) Peers: 20 (13 incoming)
2015-02-21 14:34:43.407407  Local: 46412GH/s in last 10.0 minutes Local dead on arrival: ~7.6% (5-10%) Expected time to share: 29.6 minutes
2015-02-21 14:34:43.407553  Shares: 137 (7 orphan, 12 dead) Stale rate: ~13.9% (9-21%) Efficiency: ~100.5% (92-107%) Current payout: 0.0076 BTC
2015-02-21 14:34:43.407703  Pool: 1040TH/s Stale rate: 14.3% Expected time to block: 2.1 days

Specifically, I'm looking for an explanation as to why my node is suddenly reporting a payout to the node's payout address.  I have 0% fees.  The only miner on my node is my own (some of my own gear, plus some rentals).  All of the rigs, owned and rented are set to mine to the same BTC address.  So, why do I suddenly have a payout going to my node's payout address???

EDIT: aurel57, take a look at the workers.  Notice the one that has difficulty of 500 and share difficulty of 3738875?  That's an S3 that I have set as "ADDRESS+500/500".  The others are the rentals.  One has "ADDRESS+256".  The others just have "ADDRESS".  You can see the effects of using the "+" and "/" clearly here.

[aurel57]

Isn't it true that if you mine on a node with other people (in your local area, to keep latency down), you can reduce difficulty to get a share that way (as the entire node finds a share, and distributes it to the participants via a lower difficulty pps method)?

I see that to be a viable workaround to flaw #2 above. Sure, it might boost centralization a bit as miners conglomerate into local nodes, but as long as there are geographic distances between miners super-nodes (51% of hashrate) shouldn't exist due to latency.

If this has already been answered in the thread, sorry!  

No.

You can only lower your share difficulty to the network's determined difficulty.  You do this by using the "/" after your address.  This may sound confusing, but it's pretty easy in reality.

If the node you're mining on has a considerably higher hash rate than what you are contributing, then it is advantageous to you to tell the node you want to have the network minimum share value.  For example.  Let's say that I run my own node and I have 30TH/s on it.  If you bring a single S5 onto my node, then you should setup your user name like this: "MYBTCADDRESS/1000".  That "/1000" will ensure that the node will accept the minimum share difficulty for your miner - which right now is 3,200,000ish.  My 30TH/s miner, if I set the user name up like this: "MYBTCADDRESS", will assign me a share difficulty of about 14,000,000.

P2Pool assigns your miners difficulty based upon the node's total hash rate.  You override that value by using "/".

Hope that helps.

So I am on a node that has 10Th+ and I have a S5 there running at 500Gh so I should set it at  /? use 1000?

Left to its own devices a node will adjust the share time to 30 minutes.  Therefore if the node's total hash rate would find a share in under half an hour the node will adjust the share difficulty up so that it settles back to that 30 minute mark.

You override that by using the "/".  As long as you use any value that is less than the network minimum share difficulty your worker will submit the minimum share difficulty.  So... Using /1000 or /1 or /1000000 doesn't matter.

ok thanks

[aurel57]

EDIT: aurel57, take a look at the workers.  Notice the one that has difficulty of 500 and share difficulty of 3738875?  That's an S3 that I have set as "ADDRESS+500/500".  The others are the rentals.  One has "ADDRESS+256".  The others just have "ADDRESS".  You can see the effects of using the "+" and "/" clearly here.

Interesting to see that. So why did you do the +256?

[iegservers]

EDIT: aurel57, take a look at the workers.  Notice the one that has difficulty of 500 and share difficulty of 3738875?  That's an S3 that I have set as "ADDRESS+500/500".  The others are the rentals.  One has "ADDRESS+256".  The others just have "ADDRESS".  You can see the effects of using the "+" and "/" clearly here.

Interesting to see that. So why did you do the +256?

im using the +256 on my s3 as well.

from original post here https://bitcointalk.org/index.php?topic=671189.0

Edit: AntMiners support p2pool. Static difficulty configuration recommended.
Since p2pool adjusts the difficulty frequently, therefore would bring hash rate loss when the difficulty changes at any time. As a result is that AntMiners' hash rate may be a little lower than that released officially when they are mining in p2pool.
We suggest you configure a static difficulty for AntMiner, when you mine in p2pool. Recommended difficulty is 256 or 512.

2. How to configure a static diff when AntMiner mines in p2pool?
Through ‘Status->Miner Configuration‘, configure Pool Worker as 'BTC address/256+256' or 'BTC address+256'.

[Meuh6879]

because so many users left.....

new 0.10 core is problematic, too, for the 127.0.0.1 antispam feature (if P2Pool is try to catch bitcoind at host IP ... bitcoin core shutdown after 10 seconds after start).

so, at the start, you must delay the P2Pool node.

1) Bitcoin core server
2) P2pool node
3) Miner software (BFGMiner in my case)

---

Crash is an other main problem since 0.9.1 ...  

[Songminer]

Alright... I've never seen this before.  Can somebody explain this from my logs:

Code:

2015-02-21 14:34:39.585148  Local: 46102GH/s in last 10.0 minutes Local dead on arrival: ~7.3% (5-10%) Expected time to share: 29.7 minutes
2015-02-21 14:34:39.585209  Shares: 136 (7 orphan, 12 dead) Stale rate: ~14.0% (9-21%) Efficiency: ~100.4% (92-107%) Current payout: 0.0000 BTC
2015-02-21 14:34:39.585311  Pool: 1025TH/s Stale rate: 14.3% Expected time to block: 2.2 days
2015-02-21 14:34:40.883225 Peer sent entire transaction bf60e45e409ed34fb9fc66c168f523c86573389cd036d762213944e2af0f25a8 that was already received
2015-02-21 14:34:42.635166 GOT SHARE! 1DeVLDoGvkbbB5n3dPvbpDbwiKGjYckCy9 8322ab0e prev 7d9ffbc9 age 86.38s DEAD ON ARRIVAL
2015-02-21 14:34:42.816110 New work for worker! Difficulty: 9881.151697 Share difficulty: 17750679.688090 Total block value: 25.219599 BTC including 1397 transactions
2015-02-21 14:34:42.960120 New work for worker! Difficulty: 500.000000 Share difficulty: 3738875.477555 Total block value: 25.219599 BTC including 1397 transactions
2015-02-21 14:34:43.094841 New work for worker! Difficulty: 256.000000 Share difficulty: 17750679.688090 Total block value: 25.219599 BTC including 1397 transactions
2015-02-21 14:34:43.240753 New work for worker! Difficulty: 9881.151697 Share difficulty: 17750679.688090 Total block value: 25.219599 BTC including 1397 transactions
2015-02-21 14:34:43.407120 P2Pool: 17397 shares in chain (17401 verified/17401 total) Peers: 20 (13 incoming)
2015-02-21 14:34:43.407407  Local: 46412GH/s in last 10.0 minutes Local dead on arrival: ~7.6% (5-10%) Expected time to share: 29.6 minutes
2015-02-21 14:34:43.407553  Shares: 137 (7 orphan, 12 dead) Stale rate: ~13.9% (9-21%) Efficiency: ~100.5% (92-107%) Current payout: 0.0076 BTC
2015-02-21 14:34:43.407703  Pool: 1040TH/s Stale rate: 14.3% Expected time to block: 2.1 days

Specifically, I'm looking for an explanation as to why my node is suddenly reporting a payout to the node's payout address.  I have 0% fees.  The only miner on my node is my own (some of my own gear, plus some rentals).  All of the rigs, owned and rented are set to mine to the same BTC address.  So, why do I suddenly have a payout going to my node's payout address???

EDIT: aurel57, take a look at the workers.  Notice the one that has difficulty of 500 and share difficulty of 3738875?  That's an S3 that I have set as "ADDRESS+500/500".  The others are the rentals.  One has "ADDRESS+256".  The others just have "ADDRESS".  You can see the effects of using the "+" and "/" clearly here.

I suspect I may have used your node and got an address wrong when I was renting... perhaps the suffix was entered incorrectly.  I had rented some hash and remember leaving your node because of no shares showing up.   I've experienced this on my own node... when I mined to a truncated address.  If shares are earned without an deliverable address, the spoils go to the node address

Think that might be it.  Want to send it to me? 

[jonnybravo0311]

Ahhhh.... That makes sense.  No problem.  When the block is found I'll send you over any BTC my node's payout address receives.

[TheAnalogKid]

At last! Hopefully there will be a few more to make up for the terrible last 10 days we've had - although I do have the feeling that the reason we got these 2 blocks is because so many users left.....

Apparently I hit #344479, you're welcome...

The funny thing is, I was one of those who left P2Pool ... then found the block on another P2Pool node...

Right after the back-to-back 4 day droughts (right before the last horrible 8-day one) I decided to split up my total hash rate off of just P2Pool to diversify.  I tossed about an equal 1/3 each P2Pool, Kano, and NastyPool.  Turns out I found the block with my miner on NastyPool which has been running about a week, after mining on my own node for over 6 months with nothing.

As with the past, I knew the pool would come back around and make up for itself, but I loathe the idea of "wasting" work, which wasn't a problem until recently when we went >3 days between blocks and shares started falling off.

[Gamonics]

Thank you jonnybravo and windpath.

Curious too: what happened with http://p2pool-nodes.info/ earlier today when it was blank? Anybody know?

[aurel57]

There is a new block!

[jonnybravo0311]

There is a new block!

Woohoo!

Songminer, PM me a BTC address to which I can send you the fees from my node.  For the block, I got 0.00737277BTC.  You can see it here: https://blockchain.info/address/16fV9qEHcdNN3pDpqQBBP3tMVfJ4i23PAU

[raywillet]

Any word on what's up with east.p2pool.co?

[aurel57]

Any word on what's up with east.p2pool.co?

http://us-east.p2pool.co/static/  ?? if this is the node your asking about it seems to be working?

[yslyung]

hi guys, since i upgraded & started to use latest version of p2pool from github by forrestv which says p2pool version unknown 7032706f6f6c2d6d6173746572 under windows usiong python & i've set the pseduo share diff manually for different type of miners such as :

btc add +500 for 5xs3 & the console shows :  New work for worker! Difficulty: 500.000000 Share difficulty: 4618833.547130 Total block value: 25.019008 BTC including 18 transactions (which is correct)

but for other miners i've set the pseduo share diff to +1000 (4 miners) & +1400 (42 miners) it does not show on the console (such as the New Work for worker line) ?

but the miners does hit & get shares. is there anything to be concern of in this case ?

in the older version 13.4 of p2pool it does show the New Work for worker for every other miner. but i did check the miners individually, the last diff is the diff i set ie, +1000 or +1400.

and if i do not add the +1000 or +1400 it does show the new work for worker once in a while in very high numbers. but in the older version 13.4 .exe of p2pool it shows up frequently.

same results when i'm using latest .exe version from raven, only the 13.4 .exe version works/shows the info properly.

there are multiple miners using the same settings under the same btc add.

tia for any help or info.

[Legov]

hi guys, since i upgraded & started to use latest version of p2pool from github by forrestv which says p2pool version unknown 7032706f6f6c2d6d6173746572 under windows usiong python & i've set the pseduo share diff manually for different type of miners such as :

btc add +500 for 5xs3 & the console shows :  New work for worker! Difficulty: 500.000000 Share difficulty: 4618833.547130 Total block value: 25.019008 BTC including 18 transactions (which is correct)

but for other miners i've set the pseduo share diff to +1000 (4 miners) & +1400 (42 miners) it does not show on the console (such as the New Work for worker line) ?

but the miners does hit & get shares. is there anything to be concern of in this case ?

in the older version 13.4 of p2pool it does show the New Work for worker for every other miner. but i did check the miners individually, the last diff is the diff i set ie, +1000 or +1400.

and if i do not add the +1000 or +1400 it does show the new work for worker once in a while in very high numbers. but in the older version 13.4 .exe of p2pool it shows up frequently.

same results when i'm using latest .exe version from raven, only the 13.4 .exe version works/shows the info properly.

there are multiple miners using the same settings under the same btc add.

tia for any help or info.

IMO the maximum setting of pseudo share diff is below 1000.
If you set a higher diff then the real pseudo share diff is reduced to less than 1000.
Search for this in your logfile

Code:

New work for worker! Difficulty: 999.9