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

[bitpop]

Does anyone knows why or if p2pool is not calculating the pool fee we set?

Like I get no payouts to the pool's address.

Igor

You get shares and they're random but they add up long term

The payout for the miners is working! The one that doesn't work is the payout for the pool fee! Like I set up the pool to have 2% fee. I'm not getting this payment!

Igor

I told you to wait, now wait.

[bitpop]

That's a decent idea about running a VPS for a bitcoind relay.  I could stick p2pool on there too while I'm at it.

I like this idea of a VPS with the p2pool and bitcoind nodes on it. Will probably be trying that in the new few days. Anyone else have any tips on doing it?

There's a Bitcoin tutorial for digital ocean

I know how to set up bitcoind on a VPS generally. Just wondering about the p2pool aspect of it. For example, is it better to have bitcoin and/or p2pool local nodes that connect to their counterparts on the VPS or just have the miners connect directly to p2pool+bitcoind on the VPS?

Just connect to vps make p2pool public
Open ports 833 9332 9333

[zvs]

That's a decent idea about running a VPS for a bitcoind relay.  I could stick p2pool on there too while I'm at it.

I like this idea of a VPS with the p2pool and bitcoind nodes on it. Will probably be trying that in the new few days. Anyone else have any tips on doing it?

There's a Bitcoin tutorial for digital ocean

I know how to set up bitcoind on a VPS generally. Just wondering about the p2pool aspect of it. For example, is it better to have bitcoin and/or p2pool local nodes that connect to their counterparts on the VPS or just have the miners connect directly to p2pool+bitcoind on the VPS?

Just connect to vps make p2pool public
Open ports 833 9332 9333

If the VPS is good enough to run p2pool on with ~8 outgoing connections, then I'd just run p2pool there.   Bitcoind isn't a problem, since getting slow block notifications in p2ool doesn't really penalize you (all in all, it's probably beneficial as far as building off previous shares goes).... if you ever solved a block, it'd increase chances of it being an orphan tho, I suppose.

..... but I wouldn't open it to the public,  not on one of those 'couple of dollars' VPS'es that I was referring to, hah

[bitpop]

You don't want to separate them, you'll get less efficiency, generating new work is critical

[TierNolan]

The payout for the miners is working! The one that doesn't work is the payout for the pool fee! Like I set up the pool to have 2% fee. I'm not getting this payment!

You get 2% of all shares submitted, not 2% of the fee credited to each share.

If your miners are generating 1 share a day, you would get 1 share to fee every 50 days.

[Acejam]

That's a decent idea about running a VPS for a bitcoind relay.  I could stick p2pool on there too while I'm at it.

I like this idea of a VPS with the p2pool and bitcoind nodes on it. Will probably be trying that in the new few days. Anyone else have any tips on doing it?

Many of the public P2Pool nodes do just this. However if that person's P2Pool instance goes down, your miners will stop. Hopefully you have a backup pool configured, but you'd be surprised how many people don't do this.

I have setup a giant cluster of P2Pool instances. You can mine with us using credentials just like any other pool. However on the backend, everything is running P2Pool. Everything is also load balanced for failover and high availability. As of now things are running with zero fee's, and my plan is to add merged mining eventually to cover operational costs.

Check us out @ http://p2pool.io

[bkminer]

I have setup a giant cluster of P2Pool instances. You can mine with us using credentials just like any other pool. However on the backend, everything is running P2Pool. Everything is also load balanced for failover and high availability. As of now things are running with zero fee's, and my plan is to add merged mining eventually to cover operational costs.

Check us out @ http://p2pool.io

I'm asking this because I'm working on a VPS node as well... I noticed your efficiency is 56% which is not so good for a p2pool node....

How are you working on the latencies?

[smooth]

I specifically wonder whether there is any value if having a local p2pool node that just talks to the VPS node.  That would reduce latency between the miners and the p2pool node, but would slightly increase latency between the miners and the rest of the p2pool network (due to the extra hop). Likewise if there is a local p2pool node, is there an advantage to also having a local bitcoind node, again connected only to the remote VPS bitcoind? That would reduce latency between p2pool and bitcoind (getblocktemplate) but again I'm not sure how much that matters.

[bkminer]

I specifically wonder whether there is any value if having a local p2pool node that just talks to the VPS node.  That would reduce latency between the miners and the p2pool node, but would slightly increase latency between the miners and the rest of the p2pool network (due to the extra hop). Likewise if there is a local p2pool node, is there an advantage to also having a local bitcoind node, again connected only to the remote VPS bitcoind.  That would reduce latency between p2pool and bitcoind (getblocktemplate) but again I'm not sure how much that matters.

I'm looking at VPS because my GBT latency is still .4s+ though I dropped my block size 750000 it's a little better now but I do hover around 100 to 102% and I noticed that elizium.name is on digital ocean with a GBT latency of .013s Still wondering if the .4s is hurting me.

-Rick

[zvs]

I just had to close a p2pool with over 4000 connections/sockets open.  Is there any way to fix this?  It's trivially easy to knock someone's p2pool offline?

[smoothrunnings]

How do I setup fees on every payment with P2Pool?

I am asking because I am going to loan one of my miners to a friend who will be running on my pool. He's agreed on a 50/50 split. Since he and I are the only ones using this pool I don't have to about anything.

[zvs]

This is what I managed w/ one computer and about 45 seconds:

Code:

tcp        0      0 5.9.24.81:9555          71.42.153.15:61772      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61613      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49614      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61657      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61653      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61660      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61767      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61690      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61611      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61750      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61698      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61648      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61775      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49647      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61667      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61672      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61622      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49637      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49609      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61714      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61671      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49643      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49639      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61652      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61700      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61761      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61732      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61726      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61605      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61709      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61609      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61758      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61735      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61603      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49625      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61733      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61728      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49628      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61720      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61654      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61754      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61740      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61724      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61773      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61729      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61612      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49620      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61692      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49646      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49645      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61641      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49611      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61682      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49653      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61711      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61640      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61676      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61602      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61697      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61744      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61712      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49606      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61704      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61687      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61674      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49607      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61685      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49633      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61771      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61606      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61765      ESTABLISHED 2679/python

I guess a firewall rule limiting the # of simultaneous connections  would work?

[smooth]

I guess a firewall rule limiting the # of simultaneous connections  would work?

If you are on linux and using iptables you can use the recent module to block IPs that attempt connections too fast. You are still vulnerable to DDOS but I guess that just goes with the territory of having anything open to the world.

[jedimstr]

This is what I managed w/ one computer and about 45 seconds:

Code:

tcp        0      0 5.9.24.81:9555          71.42.153.15:61772      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61613      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49614      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61657      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61653      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61660      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61767      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61690      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61611      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61750      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61698      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61648      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61775      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49647      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61667      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61672      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61622      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49637      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49609      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61714      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61671      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49643      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49639      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61652      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61700      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61761      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61732      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61726      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61605      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61709      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61609      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61758      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61735      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61603      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49625      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61733      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61728      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49628      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61720      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61654      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61754      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61740      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61724      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61773      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61729      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61612      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49620      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61692      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49646      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49645      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61641      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49611      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61682      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49653      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61711      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61640      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61676      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61602      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61697      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61744      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61712      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49606      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61704      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61687      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61674      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49607      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61685      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:49633      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61771      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61606      ESTABLISHED 2679/python
tcp        0      0 5.9.24.81:9555          71.42.153.15:61765      ESTABLISHED 2679/python

I guess a firewall rule limiting the # of simultaneous connections  would work?

Btw- I figured out where all those quick connects/disconnects to your node were coming from when you had it up a few months ago.  It was MacMiner (Mac GUI for BFGMiner/CGMiner/CPUMiner). They set your node as one of the default backup pools.  So all users of MacMiner eventually hit your pool when their primaries failed over.  

They don't have you as backup anymore, so you may not see as many connections now.

[rav3n_pl]

How do I setup fees on every payment with P2Pool?

I am asking because I am going to loan one of my miners to a friend who will be running on my pool. He's agreed on a 50/50 split. Since he and I are the only ones using this pool I don't have to about anything.

You not set it. Payment is directly from block. You can only set fee - how many % shares are count to node owner.

[smoothrunnings]

How do I setup fees on every payment with P2Pool?

I am asking because I am going to loan one of my miners to a friend who will be running on my pool. He's agreed on a 50/50 split. Since he and I are the only ones using this pool I don't have to about anything.

You not set it. Payment is directly from block. You can only set fee - how many % shares are count to node owner.

So if I want to set the fee so that 50% of the shares come back to my node how would I do that?

[K1773R]

How do I setup fees on every payment with P2Pool?

I am asking because I am going to loan one of my miners to a friend who will be running on my pool. He's agreed on a 50/50 split. Since he and I are the only ones using this pool I don't have to about anything.

You not set it. Payment is directly from block. You can only set fee - how many % shares are count to node owner.

So if I want to set the fee so that 50% of the shares come back to my node how would I do that?

you set fee to 50, magic!
i bet you didnt expect that...

[smoothrunnings]

How do I setup fees on every payment with P2Pool?

I am asking because I am going to loan one of my miners to a friend who will be running on my pool. He's agreed on a 50/50 split. Since he and I are the only ones using this pool I don't have to about anything.

You not set it. Payment is directly from block. You can only set fee - how many % shares are count to node owner.

So if I want to set the fee so that 50% of the shares come back to my node how would I do that?

you set fee to 50, magic!
i bet you didnt expect that...

Sorry I am still new to the p2pool, what do you mean set your fee? I am guessing I have remove the --give-author 0 from the startup command?

Thanks,

[roy7]

Sorry I am still new to the p2pool, what do you mean set your fee? I am guessing I have remove the --give-author 0 from the startup command?

Thanks,

I don't use p2pool but from my google search it looks like "-f 50" will do what you want. It will assign 50% of the shares that come in to you, instead of the miner. (Not 50% of the amount paid, so it'll average out the same over time but may not work exactly as you expect short term.)

[smoothrunnings]

Sorry I am still new to the p2pool, what do you mean set your fee? I am guessing I have remove the --give-author 0 from the startup command?

Thanks,

I don't use p2pool but from my google search it looks like "-f 50" will do what you want. It will assign 50% of the shares that come in to you, instead of the miner. (Not 50% of the amount paid, so it'll average out the same over time but may not work exactly as you expect short term.)

I think -f 50 is for the Windows version of P2Pool. I am running the Linux version.