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

[smoothrunnings]

When updating networks.py to a new identifier/prefix and a new spread setting, is it okay to keep the existing share chain data file for the new network? I know you can't run two network.py configs on same network, but it seems like keeping the prior share data wouldn't hurt the new network.

We'll probably bite the bullet and roll out the corrected SPREAD setting this week for VTC.

PS- It'd be nice if anyone else has tested my earlier diff to share feedback on it.

So your update only only applies to the front-end that has the graphs? Will I get any thing out of it if I apply it to my P2Pool that has a different front-end?

[1714077134]

1714077134

[1714077134]

1714077134

[roy7]

So your update only only applies to the front-end that has the graphs? Will I get any thing out of it if I apply it to my P2Pool that has a different front-end?

Do you run a Vertcoin p2pool node? We need to do a hard fork of the network to fix a setting that was wrong when the network first went live. Has nothing to do with the graphs.

[roy7]

This is an interesting discussion, please let us know the results.

P2pool is important for bitcoin and making it accessible to more people is important. This type of change helps public pools - and that helps bitcoin and p2pool. Let's face it, many people won't set up their own p2pool node, they want easy and compared to pools that require registration, p2pool is easy.

Decreasing variance (since people are impatient and don't care about the math) could be helpful too. 

Compare the "local rate reflected in shares" between:

http://vtc.royalminingco.com:9171/static/graphs.html?Day  (standard node)
http://vtc-us-east.royalminingco.com:9171/static/graphs.html?Day  (test node)

Standard node has about twice the hash power. The share graph has peaks up to 10x the mean speed, and many gaps. The test node with half the power has peaks only about 5x the mean speed, and almost no gaps.

I guess one could calculate the standard deviation on the graphs to get an idea of the variance reduction between the two, but just visually it's very clear.

[clown]

I have created the proxy pool as discussed earlier, source will be released very soon. I just want to get a bit of testing done. We will be able to scale p2pool to hell and back.

[smoothrunnings]

So your update only only applies to the front-end that has the graphs? Will I get any thing out of it if I apply it to my P2Pool that has a different front-end?

Do you run a Vertcoin p2pool node? We need to do a hard fork of the network to fix a setting that was wrong when the network first went live. Has nothing to do with the graphs.

I am confused by the comment after the question...

I run a Bitcoin p2pool.  p2pool.smoothrunnings.ca:9332/

[roy7]

So your update only only applies to the front-end that has the graphs? Will I get any thing out of it if I apply it to my P2Pool that has a different front-end?

Do you run a Vertcoin p2pool node? We need to do a hard fork of the network to fix a setting that was wrong when the network first went live. Has nothing to do with the graphs.

I am confused by the comment after the question...

I run a Bitcoin p2pool.  p2pool.smoothrunnings.ca:9332/

Ok then the changes we're making to the Vertcoin networks.py won't affect you in any way.

[mmouse]

PS- It'd be nice if anyone else has tested my earlier diff to share feedback on it.

I implemented your patch to work.py for my VTC node at vtc.coinpools.de:9171. Looks good so far.

One question, I can't find an answer to: where does this 1.67% of pools shares limit come from? This seems reasonable for a big network like p2pool for LTC or BTC, but many altcoins do have 5-10 pool nodes... Shouldn't this limit somehow be related to the pool node count?

PS @roy7: sorry for the delay, I managed to miss the followup discussion here

[smoothrunnings]

how do I change the port 9332 to something else for the website front-end? I know how to change the port for the bitcoin but I need to change it for the front-end now. I have setup a second server on a different box, also does the server need to communicate with the pool on 9333 or can I change that port too?

Thanks,

[bitpop]

how do I change the port 9332 to something else for the website front-end? I know how to change the port for the bitcoin but I need to change it for the front-end now. I have setup a second server on a different box, also does the server need to communicate with the pool on 9333 or can I change that port too?

Thanks,

https://en.bitcoin.it/wiki/P2Pool

  --p2pool-port PORT    use port PORT to listen for connections (forward this
                        port from your router!) (default: bitcoin:9333,
                        litecoin:9338)

  -w PORT or ADDR:PORT, --worker-port PORT or ADDR:PORT
                        listen on PORT on interface with ADDR for RPC
                        connections from miners (default: all interfaces,
                        bitcoin:9332, litecoin:9327)

[smoothrunnings]

how do I change the port 9332 to something else for the website front-end? I know how to change the port for the bitcoin but I need to change it for the front-end now. I have setup a second server on a different box, also does the server need to communicate with the pool on 9333 or can I change that port too?

Thanks,

https://en.bitcoin.it/wiki/P2Pool

  --p2pool-port PORT    use port PORT to listen for connections (forward this
                        port from your router!) (default: bitcoin:9333,
                        litecoin:9338)

  -w PORT or ADDR:PORT, --worker-port PORT or ADDR:PORT
                        listen on PORT on interface with ADDR for RPC
                        connections from miners (default: all interfaces,
                        bitcoin:9332, litecoin:9327)

so to clarify the --p2pool-port is port that when you access it hits the webpage and not the mining pool for the coin(s)?

[bitpop]

No 9332 is both mining and web page
9333 is p2p

[smoothrunnings]

No 9332 is both mining and web page
9333 is p2p

So I am back to my original question. How do I change the website front-end port?

[twmz]

No 9332 is both mining and web page
9333 is p2p

So I am back to my original question. How do I change the website front-end port?

The answer is still -w.  You can't change the port for only the website front-end without changing the port for miners.  The port for the front-end and the miners is always the same port.

[smoothrunnings]

No 9332 is both mining and web page
9333 is p2p

So I am back to my original question. How do I change the website front-end port?

The answer is still -w.  You can't change the port for only the website front-end without changing the port for miners.  The port for the front-end and the miners is always the same port.

That's not true. I have seen P2Pool sites that have bitcoin set to port 9332 but when you try to access the front-end get a message that no page exists, and some have bitcoin on port 9332 and the front-end on a different port like port 80.

[bitpop]

No 9332 is both mining and web page
9333 is p2p

So I am back to my original question. How do I change the website front-end port?

The answer is still -w.  You can't change the port for only the website front-end without changing the port for miners.  The port for the front-end and the miners is always the same port.

That's not true. I have seen P2Pool sites that have bitcoin set to port 9332 but when you try to access the front-end get a message that no page exists, and some have bitcoin on port 9332 and the front-end on a different port like port 80.

Show us

[twmz]

No 9332 is both mining and web page
9333 is p2p

So I am back to my original question. How do I change the website front-end port?

The answer is still -w.  You can't change the port for only the website front-end without changing the port for miners.  The port for the front-end and the miners is always the same port.

That's not true. I have seen P2Pool sites that have bitcoin set to port 9332 but when you try to access the front-end get a message that no page exists, and some have bitcoin on port 9332 and the front-end on a different port like port 80.

I'll clarify that it's not possible with the standard p2pool node software and built-in command line options.  Anything is possible if you are willing to change the code yourself.  The sites you have seen must have customized nodes.  You can too!  Just break out your favorite text editor and hack away.

[bitpop]

Or proxy port 80 to duplicate it probably what they did

[mmouse]

PS- It'd be nice if anyone else has tested my earlier diff to share feedback on it.

I implemented your patch to work.py for my VTC node at vtc.coinpools.de:9171. Looks good so far.

I did some more minor changes to work.py and web.py to get information for the web frontend about network diff, pool diff and share diffs - I was interested to actually see what's going on You can have a look at vtc.coinpools.de:9171.

[roy7]

I did some more minor changes to work.py and web.py to get information for the web frontend about network diff, pool diff and share diffs - I was interested to actually see what's going on You can have a look at vtc.coinpools.de:9171.

I like it! It's helpful to see the per-miner share difficulty targets. In fact, knowing the share diff target and their hash rate one could also provide an "average time per share", so miners know what to expect.

[mmouse]

I like it! It's helpful to see the per-miner share difficulty targets.

Thanks. Do we have some repo, where we could work on this and some other improvements to p2pool for altcoins?

I'd really like to consolidate the many altcoin builds (one git repo per coin ) into one build which works for most coins, for example...