P2Pool Server List

[digicoins]

Very helpful, thanks a lot!

[1714045080]

1714045080

[1714045080]

1714045080

[1714045080]

1714045080

[centove]

I have it sorted by fee, then country. The page is cached, so the host/port order is only random when the page is initially created. But each column is sortable after the fact. However, the sorted results require javascript. Without it, the list will just be in a random order.

What I'm talking about, is the following:

Host : Port Descending:

Looks good till:
50.196.159.77:9332   
5.9.24.81:9332   
5.9.157.150:9332   
46.134.219.35:9332   

And so on... Nothing critical, just an observation.

[Mogumodz]

I made a list of all the publicly available bitcoin p2pool nodes here - http://p2pool-nodes.info/

I have included some basic info about each pool - let me know if there's anything else you want to see added. It updated a couple times per day.

Any chance you can make the host/port clickable like fee.

[zvs]

I made a list of all the publicly available bitcoin p2pool nodes here - http://p2pool-nodes.info/

I have included some basic info about each pool - let me know if there's anything else you want to see added. It updated a couple times per day.

nice list

mr. t's house of pity has been activated as of 21:00 CST (-5 GMT) to increase efficiencies

sadly a few ppl with high hashrates are not on public ports

ed: and mr. t is sad that one of these people, some CTG thing, overwrote one of mr. t's shares by getting two in a row
ed2: or wait, is this 128.218.etc?  then just temporarily lost connection =/

[dc81]

I have it sorted by fee, then country. The page is cached, so the host/port order is only random when the page is initially created. But each column is sortable after the fact. However, the sorted results require javascript. Without it, the list will just be in a random order.

What I'm talking about, is the following:

Host : Port Descending:

Looks good till:
50.196.159.77:9332   
5.9.24.81:9332   
5.9.157.150:9332   
46.134.219.35:9332   

And so on... Nothing critical, just an observation.

done

[dc81]

I made a list of all the publicly available bitcoin p2pool nodes here - http://p2pool-nodes.info/

I have included some basic info about each pool - let me know if there's anything else you want to see added. It updated a couple times per day.

Any chance you can make the host/port clickable like fee.

i have it in the back end, so the next update will show it. should show up by the end of the day.

[Mogumodz]

I made a list of all the publicly available bitcoin p2pool nodes here - http://p2pool-nodes.info/

I have included some basic info about each pool - let me know if there's anything else you want to see added. It updated a couple times per day.

Any chance you can make the host/port clickable like fee.

i have it in the back end, so the next update will show it. should show up by the end of the day.

Thanks buddy, just checked and all working

[zvs]

So, I made my p2pool log public at www.nogleg.com/log  (times displayed are in CST, -5 UTC/GMT. it gets reset periodically)..  no sensitive information there, only IPs shown are other p2pool nodes that anyone could see themselves by running p2pool.  The addresses shown getting shares can be seen by going to my pool anyway & the amount they are receiving is displayed publically in the 'payouts if block is found now'.

Anyway,

There are a few incoming connections that are incredibly annoying that I've considered firewalling, but then I think it's possible they may fix their pool at some point, so..

I assume the stuff about 'peer sent entire transaction xxxxxxxxx that was already received' means that I got person X's share before person Y's (and sometimes person Z, Z2, etc)?.. so orphan is incoming?  (ed: well, for my share that was just orphaned, I didn't see anything about that... just from timestamps that the Mav one was about 150ms earlier)

What do the transactions pulled from latency queue signify?

Also, wouldn't a p2pool node w/ many people connected have problems with the 'new work to worker' stuff?   It looks like each takes about 5ms or so.  I usually run my p2pool on ramfs, but after some recent shenanigans where I lost about 12hrs of data, I stopped... does that make that new work process quicker?

anyone know about any of those?



(ed2:  i just changed incoming connections max to 1.  maybe some superstition about those IPs that just connect and timeout over and over, but didnt like the start)

(ed3: this is info from a pool other than my own, a share that I had orphaned)

mine:

Time first seen: Thu May 02 2013 08:42:42 GMT-0500 (Central Daylight Time) (1367502162.504647)

1CTgYxMTY5j6SLytKeMsBWAXuUc6yNKcAe: 

Time first seen: Thu May 02 2013 08:42:44 GMT-0500 (Central Daylight Time) (1367502164.585231) 

a second opinion at another pool:

mine:

Time first seen: Thu May 02 2013 08:42:42 GMT-0500 (Central Daylight Time) (1367502162.457166)

1CTgYxMTY5j6SLytKeMsBWAXuUc6yNKcAe: 

Time first seen: Thu May 02 2013 08:42:44 GMT-0500 (Central Daylight Time) (1367502164.538657)

... wouldn't the base client have rendered that share DOA (as it was over 2000ms late), even though 1CTgYxMTY5j6SLytKeMsBWAXuUc6yNKcAe did happen to get the following share about 10 seconds later..... or dies it resurrect it from the dead to send out both to everyone?

... and why does someone with 60ghash+ have 2+ second lag time?

[furball]

I hope you don't mind me asking but I noticed that your latency time on your nogleg.com P2Pool site is very low...impressively low! :-)

Were you playing around with the max connections a while(in both Bitcoin and P2Pool) to get it that low? Do you use a certain value to achieve that?

Any help would be greatly appreciated!

[furball]

Is there any chance we could get Harvest Coin on the P2Pool server list on page one here? It would be greatly appreciated! Here is the relevant information.

Dublin::Ireland::http://mining.harvestcoin.com:9332::0.5::BTC::Harvest Coin::Furball
Dublin::Ireland::http://mining.harvestcoin.com:9327::0.5::LTC::Harvest Coin::Furball

Thanks again.

[RobRoy]

Hi all!

Sorry...little speak english

I setup new p2pool in Hungary / Europe

BTC
host: p2pool.web2go.hu
post: 9332
login: btcaddr
pass: x

fee: 0.5%

stat: http://p2pool.web2go.hu:9332/static/index.html

LTC
host: p2pool.web2go.hu
post: 9327
login: ltcaddr
pass: x

fee: 0.5%

stat: http://p2pool.web2go.hu:9327/static/index.html

Budapest::Hungary::p2pool.web2go.hu:9327::0.5::LTC::HunPool::RobRoy
Budapest::Hungary::p2pool.web2go.hu:9332::0.5::BTC::HunPool::RobRoy

Thanks!

[zvs]

5.9.24.81:9332, 0% fee, 0.1% donation

[kano]

http://5.9.24.81:9332/static/    for Bitcoins,  0.1 donation, 0.0 fee

http://5.9.24.81:19327/static/  for Clownshoe coins, 0.0 donation, 1.0 fee,   subject to being dismantled at any moment

furball:  the latency is (from my experience) mostly determined by your maxblocksize.  set it to 5000 (so you can catch a few transactions that might have bloated fees)  and your latency should drop a lot.  less transactions = lower latency.   also less orphans

Sigh, why do people do that?

Basically your saying that pool mining is 100 times better for bitcoin that your p2pool coz some pools can commit up to 100x the transactions that you do.
Transactions are the other part of what is necessary to keep bitcoin alive.
No transactions means no bitcoin.

Sigh, again.

[gyverlb]

http://5.9.24.81:9332/static/    for Bitcoins,  0.1 donation, 0.0 fee

http://5.9.24.81:19327/static/  for Clownshoe coins, 0.0 donation, 1.0 fee,   subject to being dismantled at any moment

furball:  the latency is (from my experience) mostly determined by your maxblocksize.  set it to 5000 (so you can catch a few transactions that might have bloated fees)  and your latency should drop a lot.  less transactions = lower latency.   also less orphans

Sigh, why do people do that?

greed. Three ways to improve the situation:

• speedup bitcoind rpc interfaces so that they can handle large blocks without slowing down
• track the amount of transactions included in P2Pool shares for each miner and make P2Pool distribute the transactions fees proportionally
• let the market decide: when transactions are piling up, there's motivation to increase the block size

Note that the first one would be useful for every pool and may be the simplest to implement: I'm not familiar with the code but I don't see why the interface needs to slow down with block size. bitcoind could maintain a cache of block templates and serve requests from it, updating this cache asynchronously according to incoming transactions and block generations.

[zvs]

http://5.9.24.81:9332/static/    for Bitcoins,  0.1 donation, 0.0 fee

http://5.9.24.81:19327/static/  for Clownshoe coins, 0.0 donation, 1.0 fee,   subject to being dismantled at any moment

furball:  the latency is (from my experience) mostly determined by your maxblocksize.  set it to 5000 (so you can catch a few transactions that might have bloated fees)  and your latency should drop a lot.  less transactions = lower latency.   also less orphans

Sigh, why do people do that?

greed. Three ways to improve the situation:

• speedup bitcoind rpc interfaces so that they can handle large blocks without slowing down
• track the amount of transactions included in P2Pool shares for each miner and make P2Pool distribute the transactions fees proportionally
• let the market decide: when transactions are piling up, there's motivation to increase the block size

Note that the first one would be useful for every pool and may be the simplest to implement: I'm not familiar with the code but I don't see why the interface needs to slow down with block size. bitcoind could maintain a cache of block templates and serve requests from it, updating this cache asynchronously according to incoming transactions and block generations.

greed?  so is that why people send out transactions with 10000 fee?

what if i didn't think they were worth including in my blocks?

[gyverlb]

http://5.9.24.81:9332/static/    for Bitcoins,  0.1 donation, 0.0 fee

http://5.9.24.81:19327/static/  for Clownshoe coins, 0.0 donation, 1.0 fee,   subject to being dismantled at any moment

furball:  the latency is (from my experience) mostly determined by your maxblocksize.  set it to 5000 (so you can catch a few transactions that might have bloated fees)  and your latency should drop a lot.  less transactions = lower latency.   also less orphans

Sigh, why do people do that?

greed. Three ways to improve the situation:

• speedup bitcoind rpc interfaces so that they can handle large blocks without slowing down
• track the amount of transactions included in P2Pool shares for each miner and make P2Pool distribute the transactions fees proportionally
• let the market decide: when transactions are piling up, there's motivation to increase the block size

Note that the first one would be useful for every pool and may be the simplest to implement: I'm not familiar with the code but I don't see why the interface needs to slow down with block size. bitcoind could maintain a cache of block templates and serve requests from it, updating this cache asynchronously according to incoming transactions and block generations.

greed?  so is that why people send out transactions with 10000 fee?

what if i didn't think they were worth including in my blocks?

I don't get your point.

[furball]

furball:  the latency is (from my experience) mostly determined by your maxblocksize.  set it to 5000 (so you can catch a few transactions that might have bloated fees)  and your latency should drop a lot.  less transactions = lower latency.   also less orphans

Thanks so much for the tip zvs, will definitely give that a go.

[kano]

furball:  the latency is (from my experience) mostly determined by your maxblocksize.  set it to 5000 (so you can catch a few transactions that might have bloated fees)  and your latency should drop a lot.  less transactions = lower latency.   also less orphans

Thanks so much for the tip zvs, will definitely give that a go.

... and another p2pooler makes p2pool 100 times worse than using any of the top pools ...

[gyverlb]

furball:  the latency is (from my experience) mostly determined by your maxblocksize.  set it to 5000 (so you can catch a few transactions that might have bloated fees)  and your latency should drop a lot.  less transactions = lower latency.   also less orphans

Thanks so much for the tip zvs, will definitely give that a go.

... and another p2pooler makes p2pool 100 times worse than using any of the top pools ...

He might well lose a bit of money with a maxblocksize so low but it's better than almost any other pool. If income is better on p2pool, the market decides to switch to p2pool.

So Kano, why don't you patch bitcoin for speeding up getblocktemplate to avoid this instead of harassing miners who don't have the knowledge to do it themselves?

[furball]

furball:  the latency is (from my experience) mostly determined by your maxblocksize.  set it to 5000 (so you can catch a few transactions that might have bloated fees)  and your latency should drop a lot.  less transactions = lower latency.   also less orphans

Thanks so much for the tip zvs, will definitely give that a go.

... and another p2pooler makes p2pool 100 times worse than using any of the top pools ...

He might well lose a bit of money with a maxblocksize so low but it's better than almost any other pool. If income is better on p2pool, the market decides to switch to p2pool.

So Kano, why don't you patch bitcoin for speeding up getblocktemplate to avoid this instead of harassing miners who don't have the knowledge to do it themselves?

Just for the record...I made the change that ZVS suggested and my latency has gone to sub 0.05 and my efficiency is at 120%, so I'm a happy camper! Thanks ZCS, appreciate the help.

I'm no genius when it comes to these things and always open to people's opinions...I'm just grateful I got an answer to my question...great Bitcoin community!