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

[Ente]

The 10 is only on outbound connections.  If you portforward you can have more than 10.  10 outbound + unlimited inbound.

Ah, nice!
I have tcp 9333 forwarded, closed p2pool and restarted. Anything else I forgot? I am still at 10+0..
Is (only) 9333 right?
I dont need to announce this or anything, do I?
Or is it just normal that it takes that long for nodes to connect?

Ente

[tiker]

Nope, nothing else you need to do.

I've done the same, forwarded port and waited.  I've seen 30+ connections - 10 out and 20+ incoming to my node.

[Ente]

hmm, okay then..
I just rechecked, and could telnet into 9333 from outside. P2pool saw that connection (and timed out), so I just have to wait for connections to come in (still 10+0, after one hour)

Thanks for the info!

Ente

[twmz]

hmm, okay then..
I just rechecked, and could telnet into 9333 from outside. P2pool saw that connection (and timed out), so I just have to wait for connections to come in (still 10+0, after one hour)

Thanks for the info!

Ente

It will take a while.  P2Pool nodes prefer to connect to nodes that have been up for a long time, so if your node is just recently added to the network, you won't get chosen very often.

[Ente]

It will take a while.  P2Pool nodes prefer to connect to nodes that have been up for a long time, so if your node is just recently added to the network, you won't get chosen very often.

Makes sense!
The IP will auto-reconnect every 24h, will that make that node "unreliable"? Or does it just have to run a long time without restart/reboot to be "reliable"? I.E. does every installation have an ID or something? Or does it change with running instance, or with IP?

Hmm, I guess only forrestv can answer this?

Ente

[tiker]

Your node has to be running for a while without the IP changing.  It took me 12 hours (over night) before I saw my first connection.  It was a few weeks later when I saw higher numbers.

[Red Emerald]

Your node has to be running for a while without the IP changing.  It took me 12 hours (over night) before I saw my first connection.  It was a few weeks later when I saw higher numbers.

I see my first few connections pretty much instantly.  And I get to 10 really fast.  I just restarted my miner to update and am back at 13 peers in under a minute.

[tiker]

Yes, but you've been running for awhile.   When you ran your p2pool node for the very first time how long did it take?

[Red Emerald]

Yes, but you've been running for awhile.   When you ran your p2pool node for the very first time how long did it take?

I'm pretty sure I had 10 in under a minute when I first setup, too.  My backup node is much newer and it got connections just as fast as the server that has been up since January.

I have a public IP, so theres no UPNP on my primary.  I thought that might make a difference at first, but my secondary node has the port firewalled and no UPNP either.  It should have a harder time getting connections, but it still gets them just as fast.

Maybe try adding " -n p2pool.stitthappens.com:8335" to your command? That should get you connected to me at the very least. Theres a list of public nodes on http://nodes.p2pmine.com/, but that lists the worker port instead of the p2p port.

[eightbitbandit]

Hi everyone, I've been playing around with bitcoind/p2pool on my Fedora 16 box, and I decided to write an init script to manage starting and stopping things between updates. I think I might be one of the odd ones who's not using a Debian system, so I figured I'd add to your options . Feel free to take a look and copy/modify as you see fit. http://pastebin.com/qCDQerWP

[forrestv]

P2Pool release 0.10.3 signed tag: 0.10.3 UPGRADE REQUIRED before April 1st (BIP 16 date), March 27th for Litecoin

Windows binary: http://u.forre.st/u/jtjrvlxm/p2pool_win32_0.10.3.zip
Tarball: https://github.com/forrestv/p2pool/tarball/0.10.3
Zipball: https://github.com/forrestv/p2pool/zipball/0.10.3

This release purposely breaks compatibility in order to manage the changes BIP16 will bring, but also includes some other useful protocol changes. It's also the first release posted here that includes the new graphing implementation, which works on Windows (screenshot: http://u.forre.st/u/iastaoit/some-graphs.png).

Changes:
* Require users to be running a BIP16-compatible bitcoind (0.6.0rc4 or higher, or luke-jr's 0.5.4 backport). 0.6.0.rc4 is available at http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.6.0/test/ 0.5.4rc1 at https://bitcointalk.org/index.php?topic=72069.0
* New graph implementation (works on Windows!) with per-miner graphs. Go to http://127.0.0.1:9332/static/graphs.html once installed to view.
* The "script" bad output script bug will be fixed on the changeover on April 1st.
* Shares include a "version vote" that lets clients display a warning when an upgrade will soon be required.
* Shares contain the hash of their 100th parent share which could let a challenge/response protocol be implemented to verify that nodes are friendly and not just spamming you with shares.
* Shares contain a merkle branch so P2Pool's unique merged mining method could be used by other chains without any additional overhead on the Bitcoin blockchain.

[rjk]

It's also the first release posted here that includes the new graphing implementation, which works on Windows.

Changes:
* New graph implementation (works on Windows!) with per-miner graphs. Go to http://127.0.0.1:9332/static once installed to view.

Yay!

[NothinG]

* New graph implementation (works on Windows!) with per-miner graphs. Go to http://127.0.0.1:9332/static once installed to view.

Would it be possible to code in where miners can define a password for their graphs?

[twmz]

P2Pool release 0.10.3 signed tag: 0.10.3 UPGRADE REQUIRED before April 1st (BIP 16 date), March 27th for Litecoin

This version also includes the suggested message at startup about donations.  If you explicitly enabled donating, it thanks you.  If you have forced donations off, it asks you to change your mind and donate.  If you don't have the donation command line argument at all, it explains that it is donating 0.5% by default and explains how to change that with the command line parameter.

Thank you, forrestv.

[DeathAndTaxes]

Yes, but you've been running for awhile.   When you ran your p2pool node for the very first time how long did it take?

I'm pretty sure I had 10 in under a minute when I first setup, too.  My backup node is much newer and it got connections just as fast as the server that has been up since January.

I have a public IP, so theres no UPNP on my primary.  I thought that might make a difference at first, but my secondary node has the port firewalled and no UPNP either.  It should have a harder time getting connections, but it still gets them just as fast.

Maybe try adding " -n p2pool.stitthappens.com:8335" to your command? That should get you connected to me at the very least. Theres a list of public nodes on http://nodes.p2pmine.com/, but that lists the worker port instead of the p2p port.

The first 10 are outbound.  They are your nodes contacting other nodes.  The "slow" part is the 11th+ connection.  Your nodes only maintains 10 outbound and only repalces one of those when one is lost so the 11th+ are other nodes choosing yours.  It takes a while.  There is some luck involved but the network prefers older nodes so it may take some time (sometimes minutes, sometimes hours) before another node "picks" you.

[NothinG]

Yes, but you've been running for awhile.   When you ran your p2pool node for the very first time how long did it take?

I'm pretty sure I had 10 in under a minute when I first setup, too.  My backup node is much newer and it got connections just as fast as the server that has been up since January.

I have a public IP, so theres no UPNP on my primary.  I thought that might make a difference at first, but my secondary node has the port firewalled and no UPNP either.  It should have a harder time getting connections, but it still gets them just as fast.

Maybe try adding " -n p2pool.stitthappens.com:8335" to your command? That should get you connected to me at the very least. Theres a list of public nodes on http://nodes.p2pmine.com/, but that lists the worker port instead of the p2p port.

The first 10 are outbound.  They are your nodes contacting other nodes.  The "slow" part is the 11th+ connection.  Your nodes only maintains 10 outbound and only repalces one of those when one is lost so the 11th+ are other nodes choosing yours.  It takes a while.  There is some luck involved but the network prefers older nodes so it may take some time (sometimes minutes, sometimes hours) before another node "picks" you.

Does this mean each node is setup to house 10 preferred miners at a time?
If so, I should add that to my site.

[DeathAndTaxes]

Does this mean each node is setup to house 10 preferred miners at a time?
If so, I should add that to my site.

No.

This has nothing to do with miners. 

[spiccioli]

* New graph implementation (works on Windows!) with per-miner graphs. Go to http://127.0.0.1:9332/static once installed to view.

Would it be possible to code in where miners can define a password for their graphs?

You set miners password inside data/bitcoin/vip_pass file or I did not understand your question

spiccioli

[Ente]

P2Pool release 0.10.3

Sweet! :-)
Can't wait to get home!

UPGRADE REQUIRED before April 1st (BIP 16 date), March 27th for Litecoin[/b]

This release purposely breaks compatibility in order to manage the changes BIP16 will bring

Uh, so what happens when a few, or when most nodes switch? I can't imagine the sharechain would split, you would have made instructions about that. So it doesnt matter when we switch, as long as it is in the next days? Sooner, to get all the nice new features! :-)

Aah, individual graphs, awesome!
I am considering leaving work earlier today just to check it out!

Ente

[twmz]

Uh, so what happens when a few, or when most nodes switch? I can't imagine the sharechain would split, you would have made instructions about that. So it doesnt matter when we switch, as long as it is in the next days? Sooner, to get all the nice new features! :-)

You can upgrade anytime you want between now and April 1.  Assuming this is going to work just like the last protocol change a few weeks ago, the p2pool software will automatically switch from the old way to the new way at midnight (U.S. Eastern Time probably) on April 1.  And there is probably a 1 hour grace period like there was last time to account for the fact that everyone's clocks are not exactly synchronized.