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

[mdude77]

The larger p2pool is, the higher the share difficulty.  Right now the share difficulty is 2million.  Yes, that makes variance large for little guys.  Has always been a downside of p2pool.

In today's day and age, 200gh/s isn't that much.

At that share difficulty, how much hashrate do I need to have, so I could expect 1 share a day on average?

I'm guessing about 100gh/s.

M

[1714196533]

1714196533

[1714196533]

1714196533

[jonnybravo0311]

Updated list to include FSC (fusioncoin):

To help other p2pool ops that may be interested in sharing their merged mining income, I have dedicated addresses you can send to that I'll then convert to BTC and feed back into the pool:

DVC: 1f56VqR9ajX3K42qSaDezvKXFmruSDg1B
IXC: xaNQ54gxowcwHyxqGtFM4vwCfS84V6fmKF
NMC: N1XhWNmvGhFL145zmQGQv7Vug6mThNh1iQ
I0C: jMDtRnMAk2WxaoAw8HUceMaxPPqAuZ8AEN
FSC: Fjhv8Sk8iC7AF76CTJbKo1zkHLUbTTTBs2

(I haven't given up on this yet... despite the fact that it doesn't seem be going anywhere.)

M

I checked out some of the exchanges and there's pretty much no activity on any of them for FSC.  Not sure if you even could convert to BTC.  I've currently got 139,000 FSC (well, that is the balance in my wallet, not all of it's confirmed yet) that I can send if you want to combine them with whatever you've got.

I've got about 100,000 or so here.  I'll keep them stashed away until/if the day comes they have some value.

M

Just fired 150,000 over to your donation address.  Transaction ID: 6351b47af29579dcbdac7fc8a7d042534a9ddde1684a87e4b99f08088595b4f6

[jonnybravo0311]

The larger p2pool is, the higher the share difficulty.  Right now the share difficulty is 2million.  Yes, that makes variance large for little guys.  Has always been a downside of p2pool.

In today's day and age, 200gh/s isn't that much.

At that share difficulty, how much hashrate do I need to have, so I could expect 1 share a day on average?

I'm guessing about 100gh/s.

M

You can figure it out using the following formula:

Difficulty * 2**32 / hashrate / 86400 = number of days to find a share

Since you want the days to find a share to be 1, you can solve for hash rate.

2272866.97 * 2**32 / hashrate / 86400 = 1

hashrate = 112.98482991097931851851852 GH/s as of right now

[andmax]

Can anyone help me I rebooted my p2pool node running on Ubuntu 14.04 and I get this error. Bitcoin Qt is running and up to date. My node has been running fine up until the last reboot.

andrew@andrew-Inspiron-530s:~$ python ~/p2pool/run_p2pool.py -n 82.196.8.44:9333 -n 146.185.183.227:9333 <username> <password>
2014-06-04 04:53:52.347693 p2pool (version 13.4-24-gf0eeb48-dirty)
2014-06-04 04:53:52.347840
2014-06-04 04:53:52.347932 Testing bitcoind RPC connection to 'http://127.0.0.1:8332/' with username 'xxxxxxx'...
2014-06-04 04:53:52.349553 > Error while checking Bitcoin connection:
2014-06-04 04:53:52.349666 > Traceback (most recent call last):
2014-06-04 04:53:52.349720 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused.
2014-06-04 04:53:53.351541 > Error while checking Bitcoin connection:
2014-06-04 04:53:53.351698 > Traceback (most recent call last):
2014-06-04 04:53:53.351770 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused

[windpath]

On the speed/variance topic:

This is a miner who has been mining consistently at 10 GHs (yes, ten) on P2Pool .

The miner was paid (i.e. had a share) in 15 of the last 20 blocks.

100 GHs is completely realistic for P2Pool, you just have to be patient and the BTC will come in.



Edit: As it turns out this miner was previously on another p2pool node at about 250 GHs, then dropped to 10 GHs June 3rd, so these payouts do not accurately reflect 10 GHs...

I do still believe 100 GHs, over time, will do just fine on p2pool....

[jonnybravo0311]

Can anyone help me I rebooted my p2pool node running on Ubuntu 14.04 and I get this error. Bitcoin Qt is running and up to date. My node has been running fine up until the last reboot.

andrew@andrew-Inspiron-530s:~$ python ~/p2pool/run_p2pool.py -n 82.196.8.44:9333 -n 146.185.183.227:9333 <username> <password>
2014-06-04 04:53:52.347693 p2pool (version 13.4-24-gf0eeb48-dirty)
2014-06-04 04:53:52.347840
2014-06-04 04:53:52.347932 Testing bitcoind RPC connection to 'http://127.0.0.1:8332/' with username 'xxxxxxx'...
2014-06-04 04:53:52.349553 > Error while checking Bitcoin connection:
2014-06-04 04:53:52.349666 > Traceback (most recent call last):
2014-06-04 04:53:52.349720 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused.
2014-06-04 04:53:53.351541 > Error while checking Bitcoin connection:
2014-06-04 04:53:53.351698 > Traceback (most recent call last):
2014-06-04 04:53:53.351770 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused

You have any restrictions on the number of connections allowed to your bitcoind process?  Did you try stopping/restarting bitcoind?  Does Ubuntu 14.04 have some kind of built-in security that you need to allow port 8332 traffic (sorry, don't know that distribution well enough)?  Can you telnet into that IP/port successfully?

[CaptEmulation]

I do still believe 100 GHs, over time, will do just fine on p2pool....

A 100GHS miner will have barely acceptable variance right now but in one week or month's time-- who knows?

[DeeBo]

I just got my Antminer S1 in and decided to give p2pool a shot.  I set up my own node and got my miner connected to it and mining successfully but I wasn't finding any shares.  I turn over to the stats at http://127.0.0.1:9332 and it says ETA 11 hours to find 1 share    Meanwhile it's ETA 19 hours for the pool to find a block so that means if I'm lucky I'll get 1 or 2 shares and if they happen to be at the beginning of the round... well it's PPLNS so it won't even count right?  I'm starting to see why this isn't catching on.  We need much less difficulty on the shares so little guys like me can actually mine on it without it being a cointoss whether I get any actual bitcoins out of it.  I've got another S1 coming in tomorrow but 6-7 hours per share still doesn't cut it for me (especially with the PPLNS system.)

*sigh*  Back to GHash I go for tonight.  I may try looking for other pools in the morning since I don't like how big GHash is getting but at least I get steady rewards over there.

The larger p2pool is, the higher the share difficulty.  Right now the share difficulty is 2million.  Yes, that makes variance large for little guys.  Has always been a downside of p2pool.

In today's day and age, 200gh/s isn't that much.

That said, I've got someone on my node who has 800MH/s..


Might I suggest eligius over GHash?

M

I looked at it today and I like Eligus.  My 2nd Antminer S1 came in this morning and I had them both switched over to Eligus and went to cash out of GHash.  Unfortunately, they have a minimum 0.01 withdrawal limit and I had only mined about 0.005.  On top of that, it looks like they charge a ridiculous 0.001 "commission" on withdrawal so I had to switch my miners back to GHash until I hit my minimum and then give them a 10% fee to cash out.  They don't mention that withdrawal commission when they say "0% fee pool."  I like the way Eligus does it better where they send the generated coin from the next block directly to you when you hit your minimum (and it's all actually free as far as I can tell.)

[jonnybravo0311]

I just got my Antminer S1 in and decided to give p2pool a shot.  I set up my own node and got my miner connected to it and mining successfully but I wasn't finding any shares.  I turn over to the stats at http://127.0.0.1:9332 and it says ETA 11 hours to find 1 share    Meanwhile it's ETA 19 hours for the pool to find a block so that means if I'm lucky I'll get 1 or 2 shares and if they happen to be at the beginning of the round... well it's PPLNS so it won't even count right?  I'm starting to see why this isn't catching on.  We need much less difficulty on the shares so little guys like me can actually mine on it without it being a cointoss whether I get any actual bitcoins out of it.  I've got another S1 coming in tomorrow but 6-7 hours per share still doesn't cut it for me (especially with the PPLNS system.)

*sigh*  Back to GHash I go for tonight.  I may try looking for other pools in the morning since I don't like how big GHash is getting but at least I get steady rewards over there.

The larger p2pool is, the higher the share difficulty.  Right now the share difficulty is 2million.  Yes, that makes variance large for little guys.  Has always been a downside of p2pool.

In today's day and age, 200gh/s isn't that much.

That said, I've got someone on my node who has 800MH/s..


Might I suggest eligius over GHash?

M

I looked at it today and I like Eligus.  My 2nd Antminer S1 came in this morning and I had them both switched over to Eligus and went to cash out of GHash.  Unfortunately, they have a minimum 0.01 withdrawal limit and I had only mined about 0.005.  On top of that, it looks like they charge a ridiculous 0.001 "commission" on withdrawal so I had to switch my miners back to GHash until I hit my minimum and then give them a 10% fee to cash out.  They don't mention that withdrawal commission when they say "0% fee pool."  I like the way Eligus does it better where they send the generated coin from the next block directly to you when you hit your minimum (and it's all actually free as far as I can tell.)

Kind of off topic... but you can setup an auto-payout on GHash.  This way you just mine until you get to 0.01, and you'll get paid on their next scheduled payout (usually once a day).  No fees for auto-payouts.

[andmax]

Can anyone help me I rebooted my p2pool node running on Ubuntu 14.04 and I get this error. Bitcoin Qt is running and up to date. My node has been running fine up until the last reboot.

andrew@andrew-Inspiron-530s:~$ python ~/p2pool/run_p2pool.py -n 82.196.8.44:9333 -n 146.185.183.227:9333 <username> <password>
2014-06-04 04:53:52.347693 p2pool (version 13.4-24-gf0eeb48-dirty)
2014-06-04 04:53:52.347840
2014-06-04 04:53:52.347932 Testing bitcoind RPC connection to 'http://127.0.0.1:8332/' with username 'xxxxxxx'...
2014-06-04 04:53:52.349553 > Error while checking Bitcoin connection:
2014-06-04 04:53:52.349666 > Traceback (most recent call last):
2014-06-04 04:53:52.349720 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused.
2014-06-04 04:53:53.351541 > Error while checking Bitcoin connection:
2014-06-04 04:53:53.351698 > Traceback (most recent call last):
2014-06-04 04:53:53.351770 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused

You have any restrictions on the number of connections allowed to your bitcoind process?  Did you try stopping/restarting bitcoind?  Does Ubuntu 14.04 have some kind of built-in security that you need to allow port 8332 traffic (sorry, don't know that distribution well enough)?  Can you telnet into that IP/port successfully?

Sorry I'm new to Ubuntu, it has been running fine for the last month, I rebooted as there was a Ubuntu update and then I got this error. I have re formatted re-installed Ubuntu, Bitcoin Qt and p2pool so now have a fresh install but still getting this error. How can I see if Ubuntu is blocking port 8332 and if bitcoin is restricting a number of connections. When I first installed it it ran perfectly so not sure why I'm getting this now.

[spiccioli]

Can anyone help me I rebooted my p2pool node running on Ubuntu 14.04 and I get this error. Bitcoin Qt is running and up to date. My node has been running fine up until the last reboot.

andrew@andrew-Inspiron-530s:~$ python ~/p2pool/run_p2pool.py -n 82.196.8.44:9333 -n 146.185.183.227:9333 <username> <password>
2014-06-04 04:53:52.347693 p2pool (version 13.4-24-gf0eeb48-dirty)
2014-06-04 04:53:52.347840
2014-06-04 04:53:52.347932 Testing bitcoind RPC connection to 'http://127.0.0.1:8332/' with username 'xxxxxxx'...
2014-06-04 04:53:52.349553 > Error while checking Bitcoin connection:
2014-06-04 04:53:52.349666 > Traceback (most recent call last):
2014-06-04 04:53:52.349720 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused.
2014-06-04 04:53:53.351541 > Error while checking Bitcoin connection:
2014-06-04 04:53:53.351698 > Traceback (most recent call last):
2014-06-04 04:53:53.351770 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused

You have any restrictions on the number of connections allowed to your bitcoind process?  Did you try stopping/restarting bitcoind?  Does Ubuntu 14.04 have some kind of built-in security that you need to allow port 8332 traffic (sorry, don't know that distribution well enough)?  Can you telnet into that IP/port successfully?

Sorry I'm new to Ubuntu, it has been running fine for the last month, I rebooted as there was a Ubuntu update and then I got this error. I have re formatted re-installed Ubuntu, Bitcoin Qt and p2pool so now have a fresh install but still getting this error. How can I see if Ubuntu is blocking port 8332 and if bitcoin is restricting a number of connections. When I first installed it it ran perfectly so not sure why I'm getting this now.

andmax,

are <username> <password> the same you have inside .bitcoin/bitcoin.conf's rpcuser/rpcpassword keys ?

spiccioli

[andmax]

Can anyone help me I rebooted my p2pool node running on Ubuntu 14.04 and I get this error. Bitcoin Qt is running and up to date. My node has been running fine up until the last reboot.

andrew@andrew-Inspiron-530s:~$ python ~/p2pool/run_p2pool.py -n 82.196.8.44:9333 -n 146.185.183.227:9333 <username> <password>
2014-06-04 04:53:52.347693 p2pool (version 13.4-24-gf0eeb48-dirty)
2014-06-04 04:53:52.347840
2014-06-04 04:53:52.347932 Testing bitcoind RPC connection to 'http://127.0.0.1:8332/' with username 'xxxxxxx'...
2014-06-04 04:53:52.349553 > Error while checking Bitcoin connection:
2014-06-04 04:53:52.349666 > Traceback (most recent call last):
2014-06-04 04:53:52.349720 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused.
2014-06-04 04:53:53.351541 > Error while checking Bitcoin connection:
2014-06-04 04:53:53.351698 > Traceback (most recent call last):
2014-06-04 04:53:53.351770 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused

You have any restrictions on the number of connections allowed to your bitcoind process?  Did you try stopping/restarting bitcoind?  Does Ubuntu 14.04 have some kind of built-in security that you need to allow port 8332 traffic (sorry, don't know that distribution well enough)?  Can you telnet into that IP/port successfully?

Sorry I'm new to Ubuntu, it has been running fine for the last month, I rebooted as there was a Ubuntu update and then I got this error. I have re formatted re-installed Ubuntu, Bitcoin Qt and p2pool so now have a fresh install but still getting this error. How can I see if Ubuntu is blocking port 8332 and if bitcoin is restricting a number of connections. When I first installed it it ran perfectly so not sure why I'm getting this now.

andmax,

are <username> <password> the same you have inside .bitcoin/bitcoin.conf's rpcuser/rpcpassword keys ?

spiccioli

Yes username and password in bitcoin.conf are the same as on my command line to start p2pool, thanks for your help just want to get it back up and running again as I'm in Australia and no p2pool nodes close by to hook into.

[spiccioli]

Can anyone help me I rebooted my p2pool node running on Ubuntu 14.04 and I get this error. Bitcoin Qt is running and up to date. My node has been running fine up until the last reboot.

andrew@andrew-Inspiron-530s:~$ python ~/p2pool/run_p2pool.py -n 82.196.8.44:9333 -n 146.185.183.227:9333 <username> <password>
2014-06-04 04:53:52.347693 p2pool (version 13.4-24-gf0eeb48-dirty)
2014-06-04 04:53:52.347840
2014-06-04 04:53:52.347932 Testing bitcoind RPC connection to 'http://127.0.0.1:8332/' with username 'xxxxxxx'...
2014-06-04 04:53:52.349553 > Error while checking Bitcoin connection:
2014-06-04 04:53:52.349666 > Traceback (most recent call last):
2014-06-04 04:53:52.349720 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused.
2014-06-04 04:53:53.351541 > Error while checking Bitcoin connection:
2014-06-04 04:53:53.351698 > Traceback (most recent call last):
2014-06-04 04:53:53.351770 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused

You have any restrictions on the number of connections allowed to your bitcoind process?  Did you try stopping/restarting bitcoind?  Does Ubuntu 14.04 have some kind of built-in security that you need to allow port 8332 traffic (sorry, don't know that distribution well enough)?  Can you telnet into that IP/port successfully?

Sorry I'm new to Ubuntu, it has been running fine for the last month, I rebooted as there was a Ubuntu update and then I got this error. I have re formatted re-installed Ubuntu, Bitcoin Qt and p2pool so now have a fresh install but still getting this error. How can I see if Ubuntu is blocking port 8332 and if bitcoin is restricting a number of connections. When I first installed it it ran perfectly so not sure why I'm getting this now.

andmax,

are <username> <password> the same you have inside .bitcoin/bitcoin.conf's rpcuser/rpcpassword keys ?

spiccioli

Yes username and password in bitcoin.conf are the same as on my command line to start p2pool, thanks for your help just want to get it back up and running again as I'm in Australia and no p2pool nodes close by to hook into.

and server=1 ? do you have it inside bitcoin.conf?

and rpcallowip=? do you have it/what value has it?

as you can see I'm thinking about a misconfiguration between bitcoind and p2pool.

maybe it is something else entirely.

spiccioli

[mdude77]

Updated list to include FSC (fusioncoin):

To help other p2pool ops that may be interested in sharing their merged mining income, I have dedicated addresses you can send to that I'll then convert to BTC and feed back into the pool:

DVC: 1f56VqR9ajX3K42qSaDezvKXFmruSDg1B
IXC: xaNQ54gxowcwHyxqGtFM4vwCfS84V6fmKF
NMC: N1XhWNmvGhFL145zmQGQv7Vug6mThNh1iQ
I0C: jMDtRnMAk2WxaoAw8HUceMaxPPqAuZ8AEN
FSC: Fjhv8Sk8iC7AF76CTJbKo1zkHLUbTTTBs2

(I haven't given up on this yet... despite the fact that it doesn't seem be going anywhere.)

M

I checked out some of the exchanges and there's pretty much no activity on any of them for FSC.  Not sure if you even could convert to BTC.  I've currently got 139,000 FSC (well, that is the balance in my wallet, not all of it's confirmed yet) that I can send if you want to combine them with whatever you've got.

I've got about 100,000 or so here.  I'll keep them stashed away until/if the day comes they have some value.

M

Just fired 150,000 over to your donation address.  Transaction ID: 6351b47af29579dcbdac7fc8a7d042534a9ddde1684a87e4b99f08088595b4f6

Just got it, thanks!

M

[norgan]

Can anyone help me I rebooted my p2pool node running on Ubuntu 14.04 and I get this error. Bitcoin Qt is running and up to date. My node has been running fine up until the last reboot.

andrew@andrew-Inspiron-530s:~$ python ~/p2pool/run_p2pool.py -n 82.196.8.44:9333 -n 146.185.183.227:9333 <username> <password>
2014-06-04 04:53:52.347693 p2pool (version 13.4-24-gf0eeb48-dirty)
2014-06-04 04:53:52.347840
2014-06-04 04:53:52.347932 Testing bitcoind RPC connection to 'http://127.0.0.1:8332/' with username 'xxxxxxx'...
2014-06-04 04:53:52.349553 > Error while checking Bitcoin connection:
2014-06-04 04:53:52.349666 > Traceback (most recent call last):
2014-06-04 04:53:52.349720 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused.
2014-06-04 04:53:53.351541 > Error while checking Bitcoin connection:
2014-06-04 04:53:53.351698 > Traceback (most recent call last):
2014-06-04 04:53:53.351770 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused

You have any restrictions on the number of connections allowed to your bitcoind process?  Did you try stopping/restarting bitcoind?  Does Ubuntu 14.04 have some kind of built-in security that you need to allow port 8332 traffic (sorry, don't know that distribution well enough)?  Can you telnet into that IP/port successfully?

Sorry I'm new to Ubuntu, it has been running fine for the last month, I rebooted as there was a Ubuntu update and then I got this error. I have re formatted re-installed Ubuntu, Bitcoin Qt and p2pool so now have a fresh install but still getting this error. How can I see if Ubuntu is blocking port 8332 and if bitcoin is restricting a number of connections. When I first installed it it ran perfectly so not sure why I'm getting this now.

andmax,

are <username> <password> the same you have inside .bitcoin/bitcoin.conf's rpcuser/rpcpassword keys ?

spiccioli

Yes username and password in bitcoin.conf are the same as on my command line to start p2pool, thanks for your help just want to get it back up and running again as I'm in Australia and no p2pool nodes close by to hook into.

My node is in Sydney and performs really well. Check out my dig!

[jonnybravo0311]

Can anyone help me I rebooted my p2pool node running on Ubuntu 14.04 and I get this error. Bitcoin Qt is running and up to date. My node has been running fine up until the last reboot.

andrew@andrew-Inspiron-530s:~$ python ~/p2pool/run_p2pool.py -n 82.196.8.44:9333 -n 146.185.183.227:9333 <username> <password>
2014-06-04 04:53:52.347693 p2pool (version 13.4-24-gf0eeb48-dirty)
2014-06-04 04:53:52.347840
2014-06-04 04:53:52.347932 Testing bitcoind RPC connection to 'http://127.0.0.1:8332/' with username 'xxxxxxx'...
2014-06-04 04:53:52.349553 > Error while checking Bitcoin connection:
2014-06-04 04:53:52.349666 > Traceback (most recent call last):
2014-06-04 04:53:52.349720 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused.
2014-06-04 04:53:53.351541 > Error while checking Bitcoin connection:
2014-06-04 04:53:53.351698 > Traceback (most recent call last):
2014-06-04 04:53:53.351770 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused

You have any restrictions on the number of connections allowed to your bitcoind process?  Did you try stopping/restarting bitcoind?  Does Ubuntu 14.04 have some kind of built-in security that you need to allow port 8332 traffic (sorry, don't know that distribution well enough)?  Can you telnet into that IP/port successfully?

Sorry I'm new to Ubuntu, it has been running fine for the last month, I rebooted as there was a Ubuntu update and then I got this error. I have re formatted re-installed Ubuntu, Bitcoin Qt and p2pool so now have a fresh install but still getting this error. How can I see if Ubuntu is blocking port 8332 and if bitcoin is restricting a number of connections. When I first installed it it ran perfectly so not sure why I'm getting this now.

andmax,

are <username> <password> the same you have inside .bitcoin/bitcoin.conf's rpcuser/rpcpassword keys ?

spiccioli

Yes username and password in bitcoin.conf are the same as on my command line to start p2pool, thanks for your help just want to get it back up and running again as I'm in Australia and no p2pool nodes close by to hook into.

and server=1 ? do you have it inside bitcoin.conf?

and rpcallowip=? do you have it/what value has it?

as you can see I'm thinking about a misconfiguration between bitcoind and p2pool.

maybe it is something else entirely.

spiccioli

A couple more questions...

When you reinstalled your BTC node, did you build it from source, or install a pre-built package from somewhere?  Did you make sure that wherever you installed it, it has permissions to read from the directory in which the .conf file resides?  Did you double/triple/quadruple check all of your settings in the .conf file, and ensure that all permissions are set properly?  Did the Ubuntu upgrade cause any of the dependent packages to break/malfunction?  Did you upgrade all of your installed packages after you did the base Ubuntu upgrade?

[IYFTech]

Would love to put my 350-400TH back on p2pool if the scalability issues and the problem connecting with stratum proxy can be resolved.

Don't hold your breath. I & a few others have been harping on about this for over a year now with no success whatsoever. Looking back over the thread, the last update to p2pool was over 6 months ago, and the changes were minimal and mainly cosmetic - there has been no major development to p2pool for much longer than that, the last major improvement being adding support for stratum, which itself was about 4 months too late. Your reasons for not joining p2pool are valid, and demonstrate perfectly why p2pool is stuck at the lower end of the user scale instead of at the top - it should be the biggest & most used pool by far.

Many large scale miners like yourself stay away from p2pool for exactly the reasons you point out, as well as potential smaller miners, it has been like this for over a year now, and tbh, I can't see it being addressed any time soon, if at all. The lack of development at p2pool is legendary, as is it's unwillingness to address any issues it feels it can get away with. I see more & more potential p2pool users setting up their nodes and openly cancelling the donation to dev option, and rightly so, because there isn't any - it's a wasted payment. People who want to use p2pool are severely restricted as to what hardware they can use due to various incompatibility problems - it simply shouldn't be the case.

Even p2pool.info hasn't worked properly since the dev here took it over, it's down right now in fact and has been for a few weeks, so any potential miners are unable to see any global stats - which will only put people off using p2pool even more, why would anyone want to use a pool if they can't see the global stats/graphs? Yes, each node has it's output - but that's not enough for the majority of users.

Rant over. Having said all this - I use p2pool & have done since getting into mining, mainly because I am lucky enough to have bought hardware that can work with it, but the frustration of seeing such a brilliant idea fail so miserably due to lack of development is killing it. I've said it before & I'll keep saying it until something is done:

Quote from March 17, 2014:  "P2pool needs to start helping itself before it can expect help from miners. There are issues with the software that have remained unsolved for many, many months due to a complete lack of development, not to mention a lack of support in the p2pool thread. Unless there is some development soon, p2pool will remain at the bottom of the pool ladder, before dying completely. This is what happens to all software that is not constantly developed & improved.
Bitcoin is moving mainstream, but p2pool is stuck in the "nerd" culture: it's far too complicated for the average new user to setup, tweak & get running correctly. New users want to be able to install it & forget it - it should be capable of installing all the necessary dependencies itself as well as discovering the optimal settings needed for the machine it is being installed on - a simple wizard setup or similar. The average noob does not use command line - they want a "pretty" GUI from where they can adjust all software settings, choose what coins to mine, etc, etc.

I believe in p2pool, I use it - but it's been abandonware for quite a while now....... "

[Carlton Banks]

The last that was heard from the lead developer was that a pretty significant redesign was on the way to fix the high variance problem for smaller miners. I would assume he's still working on it.

I think the point is that p2p pooled mining is a relatively hard problem to solve. Centralised pools can make use of known, easily implemented infrastructure designs, but p2p mining needs innovative software to make the network topology viable for the purpose. This design may not now and may never be perfect, but it's a very good choice for owners of large hashrates, and even for those with smaller or middle sized rigs that already feel confident they will profit on their investment.

[jonnybravo0311]

Updated list to include FSC (fusioncoin):

To help other p2pool ops that may be interested in sharing their merged mining income, I have dedicated addresses you can send to that I'll then convert to BTC and feed back into the pool:

DVC: 1f56VqR9ajX3K42qSaDezvKXFmruSDg1B
IXC: xaNQ54gxowcwHyxqGtFM4vwCfS84V6fmKF
NMC: N1XhWNmvGhFL145zmQGQv7Vug6mThNh1iQ
I0C: jMDtRnMAk2WxaoAw8HUceMaxPPqAuZ8AEN
FSC: Fjhv8Sk8iC7AF76CTJbKo1zkHLUbTTTBs2

(I haven't given up on this yet... despite the fact that it doesn't seem be going anywhere.)

M

I checked out some of the exchanges and there's pretty much no activity on any of them for FSC.  Not sure if you even could convert to BTC.  I've currently got 139,000 FSC (well, that is the balance in my wallet, not all of it's confirmed yet) that I can send if you want to combine them with whatever you've got.

I've got about 100,000 or so here.  I'll keep them stashed away until/if the day comes they have some value.

M

Just fired 150,000 over to your donation address.  Transaction ID: 6351b47af29579dcbdac7fc8a7d042534a9ddde1684a87e4b99f08088595b4f6

Just got it, thanks!

M

Sure hope those FSC become worth something at some point... I just sent another 120,000 to your donation address.  Transaction ID: 4f70d52884c169eab88a8be4865e7c7dbb440902dc79f17d10edd7d388877586

[mdude77]

Sure hope those FSC become worth something at some point... I just sent another 120,000 to your donation address.  Transaction ID: 4f70d52884c169eab88a8be4865e7c7dbb440902dc79f17d10edd7d388877586

Thanks!

I looked briefly yesterday and I think I had 0.04BTC worth. 

M