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

[nicklello]

Regarding trying to increase adoption of p2pool....

are there any 'official' packaged releases of p2pool for Linux and/or Windows ?

Thinking that if there are not, establishing packages in the main repositories may be a good way to promote adoption.

[1714856191]

1714856191

[1714856191]

1714856191

[1714856191]

1714856191

[1714856191]

1714856191

[wariner]

Regarding trying to increase adoption of p2pool....

are there any 'official' packaged releases of p2pool for Linux and/or Windows ?

Thinking that if there are not, establishing packages in the main repositories may be a good way to promote adoption.

https://github.com/p2pool/p2pool

[trendax]

It's alive! (barely) The 21 Bitcoin Computer running P2Pool (proof of concept)

https://twitter.com/CoinCadence/status/674982369884008448

Wow that's neat, I expected some fun stuff to come from 21 Bitcoin computer. Good job.

[Richy_T]

Regarding trying to increase adoption of p2pool....

are there any 'official' packaged releases of p2pool for Linux and/or Windows ?

Thinking that if there are not, establishing packages in the main repositories may be a good way to promote adoption.

A livecd might be interesting. Or possibly a VM.

[P2XTPool]

Hey Forrestv, v0.11D of BitcoinXT is now officially released with support for BIP65: https://github.com/bitcoinxt/bitcoinxt/releases/tag/v0.11D

Okay, can you post the output of the RPC getinfo command?

You should merge my pull request https://github.com/p2pool/p2pool/pull/287

[nicklello]

Regarding trying to increase adoption of p2pool....

are there any 'official' packaged releases of p2pool for Linux and/or Windows ?

Thinking that if there are not, establishing packages in the main repositories may be a good way to promote adoption.

A livecd might be interesting. Or possibly a VM.

Or even just availability in .deb and/or .rpm format with all the dependencies taken care of.....

[-ck]

I've been working with some experimental ckproxy code designed to consolidate multiple user logins into different upstream connections. As a practical upshot of this I'm able to create a p2pool node that should accept many workers to the same user login without slowing down the p2pool node behind it. Each different user that logs in will add extra load because of the way p2pool is designed but it does allow me to create a public p2pool node that should be able to cope with many more workers than a regular p2pool node is able to.

As an experiment then, I've put up a public p2pool node with a 1% fee to test this out. So if you would like to help test it out, please direct your miners to:

Code:

stratum+tcp://node.ckpool.org:9332

If you wish to monitor progress, the actual statistics and graphs etc. are visible at http://node.ckpool.org:19332 but please don't use this url too often as it speaks directly to the p2pool node behind ckproxy.

What I'm looking for most of all are people to test multiple workers logged in with the same username, and remember to use your bitcoin address to log in with!
If it proves mildly popular I may leave this node up long term. Please give it a go.

EDIT: That node is in west coast USA. If there is demand I can also start up separate nodes in China and Germany...

[p3yot33at3r]

Hi -ck,

What a coincidence, only yesterday I was looking at your ckproxy repo with thoughts on this exact same thing. US West is a long way away from me here in Europe, but I'll point a small S3 at it for testing purposes - hopefully more p2pool users will help out also.

Many thanks for taking the time & trouble to look into this & set it up - much appreciated  

[idonothave]

I've been working with some experimental ckproxy code designed to consolidate multiple user logins into different upstream connections. As a practical upshot of this I'm able to create a p2pool node that should accept many workers to the same user login without slowing down the p2pool node behind it. Each different user that logs in will add extra load because of the way p2pool is designed but it does allow me to create a public p2pool node that should be able to cope with many more workers than a regular p2pool node is able to.

As an experiment then, I've put up a public p2pool node with a 1% fee to test this out. So if you would like to help test it out, please direct your miners to:

Code:

stratum+tcp://node.ckpool.org:9332

If you wish to monitor progress, the actual statistics and graphs etc. are visible at http://node.ckpool.org:19332 but please don't use this url too often as it speaks directly to the p2pool node behind ckproxy.

What I'm looking for most of all are people to test multiple workers logged in with the same username, and remember to use your bitcoin address to log in with!
If it proves mildly popular I may leave this node up long term. Please give it a go.

EDIT: That node is in west coast USA. If there is demand I can also start up separate nodes in China and Germany...

I have set one SP20 to work there (1PXJiWRQt3gNBAe4j6dbugEqhufJdgncCc)

[-ck]

Hi -ck,

What a coincidence, only yesterday I was looking at your ckproxy repo with thoughts on this exact same thing. US West is a long way away from me here in Europe, but I'll point a small S3 at it for testing purposes - hopefully more p2pool users will help out also.

Many thanks for taking the time & trouble to look into this & set it up - much appreciated  

Cool, so far so good. Since you're in the EU I guess I could set up the .de node as well. Will post here once it's ready and you can try that instead.

I forgot to mention the nodes are as equally well connected for fast block propagation as my solo ckpool is (they're part of my network of nodes) and have the same bitcoind optimisations.

Ok in addition I've added a node in Germany

Direct your miners to:

Code:

stratum+tcp://de.ckpool.org:9332

Statistics graphs etc. of that node are visible at http://de.ckpool.org:19332 but please don't use the URL too often

I have set one SP20 to work there (1PXJiWRQt3gNBAe4j6dbugEqhufJdgncCc)

Thanks, I appreciate the testing.

EDIT: This code is all still in TESTING so there may be issues. The de server is still not quite running properly.

[p3yot33at3r]

Great - just swapped over to the de node 

ping to the US was 302ms, while to the de node it's only 54ms - much better! 

Let me know if you need anything else -ck.

[idonothave]

Hi -ck,

What a coincidence, only yesterday I was looking at your ckproxy repo with thoughts on this exact same thing. US West is a long way away from me here in Europe, but I'll point a small S3 at it for testing purposes - hopefully more p2pool users will help out also.

Many thanks for taking the time & trouble to look into this & set it up - much appreciated  

Cool, so far so good. Since you're in the EU I guess I could set up the .de node as well. Will post here once it's ready and you can try that instead.

I forgot to mention the nodes are as equally well connected for fast block propagation as my solo ckpool is (they're part of my network of nodes) and have the same bitcoind optimisations.

Ok in addition I've added a node in Germany

Direct your miners to:

Code:

stratum+tcp://de.ckpool.org:9332

Statistics graphs etc. of that node are visible at http://de.ckpool.org:19332 but please don't use the URL too often

I have set one SP20 to work there (1PXJiWRQt3gNBAe4j6dbugEqhufJdgncCc)

Thanks, I appreciate the testing.

EDIT: This code is all still in TESTING so there may be issues. The de server is still not quite running properly.

I have ten times better latencies to de.ckpool.org than to node.ckpool.org, I have switched SP20 to de.ckpool.org... or?

[-ck]

Great - just swapped over to the de node  

ping to the US was 302ms, while to the de node it's only 54ms - much better!  

Let me know if you need anything else -ck.

Nope, all good. Just make sure you still have a backup/failover set up as this code is all new and almost certainly there will be issues.

I have ten times better latencies to de.ckpool.org than to node.ckpool.org, I have switched SP20 to de.ckpool.org... or?

Same thing. Seems to be okay now, just make sure you have a failover pool set up.

[p3yot33at3r]

Great - just swapped over to the de node  

ping to the US was 302ms, while to the de node it's only 54ms - much better!  

Let me know if you need anything else -ck.

Nope, all good. Just make sure you still have a backup/failover set up as this code is all new and almost certainly there will be issues.

I have ten times better latencies to de.ckpool.org than to node.ckpool.org, I have switched SP20 to de.ckpool.org... or?

Same thing. Seems to be okay now, just make sure you have a failover pool set up.

Always 

Many thanks again -ck. With all the nastyness going on atm, it's great that a dev such as yourself is willing to step in & help out us p2poolers 

[-ck]

Many thanks again -ck. With all the nastyness going on atm, it's great that a dev such as yourself is willing to step in & help out us p2poolers 

Incredibly the DE node has already found a share.

[p3yot33at3r]

Many thanks again -ck. With all the nastyness going on atm, it's great that a dev such as yourself is willing to step in & help out us p2poolers 

Incredibly the DE node has already found a share.

Yeah, I saw that 

I'm not seeing my payout address in the graphs for some reason:

17RAoAa2ZJy5vh2YNwx2NMHijrRmAajGr2

[idonothave]

Many thanks again -ck. With all the nastyness going on atm, it's great that a dev such as yourself is willing to step in & help out us p2poolers 

Incredibly the DE node has already found a share.

Yeah, I saw that 

I'm not seeing my payout address in the graphs for some reason:

17RAoAa2ZJy5vh2YNwx2NMHijrRmAajGr2

you cannot see it because it is working with default address which is sense of the thing
future payouts is another thing and he ck has there different solution then p2pool originaly has or?

[p3yot33at3r]

Oh yeah. Oops 

[-ck]

Many thanks again -ck. With all the nastyness going on atm, it's great that a dev such as yourself is willing to step in & help out us p2poolers 

Incredibly the DE node has already found a share.

Yeah, I saw that 

I'm not seeing my payout address in the graphs for some reason:

17RAoAa2ZJy5vh2YNwx2NMHijrRmAajGr2

you cannot see it because it is working with default address which is sense of the thing
future payouts is another thing and he ck has there different solution then p2pool originaly has or?

Does the p2pool intrinsic web page usually show miners logged into a public node as separate addresses? I currently have 2 active miners in the proxy logs:

Code:

[2015-12-12 06:38:53.071] User 1PXJiWRQt3gNBAe4j6dbugEqhufJdgncCc:{"hashrate1m": "1.48T", "hashrate5m": "1.36T", "hashrate1hr": "658G", "hashrate1d": "36.5G", "hashrate7d": "5.27G", "lastupdate": 1449920333, "workers": 1, "shares": 741666, "bestshare": 2691098.6662059599}
[2015-12-12 06:38:53.071] User 17RAoAa2ZJy5vh2YNwx2NMHijrRmAajGr2:{"hashrate1m": "381G", "hashrate5m": "380G", "hashrate1hr": "134G", "hashrate1d": "7.03G", "hashrate7d": "1.01G", "lastupdate": 1449920333, "workers": 1, "shares": 142968, "bestshare": 475613.94521986018}

If all is going correctly, 1PXJiWRQt3gNBAe4j6dbugEqhufJdgncCc got the share and as far as I can tell it was credited to him, and only 1% credited to my 1GYU9ouTVY6ECTqidLe96mWn485dP6WZaJ address.

[p3yot33at3r]

Yes, on the standard p2pool web GUI every mining address on that node can be seen.

PS:  BLOCK!!