SegWit (segregated witness) **has already activated** and for P2Pool to continue working without producing invalid blocks, everyone needs to upgrade. At 50% of our hashrate upgrading, P2Pool instances will start displaying a warning saying that an upgrade is required. Reaching that point as quickly as possible is very important. And then, at 95%, users that have not upgraded will be excluded. If non-upgraded users aren't excluded soon enough, P2Pool users will be subject to paying other users for invalid work - effectively a withholding attack.

Due to SegWit already activating upgraded users of P2Pool must not mine SegWit transactions as they are incompatible with older P2Pool versions. After v17 shares activate a new release will be made which removes this restriction.

So, please upgrade to 17.0 now and also tell everyone else to.

P2Pool is a decentralized pool that works by creating a P2P network of miner nodes. These nodes work on a chain of shares similar to Bitcoin's blockchain. Each node works on a block that includes payouts to the previous shares' owners and the node itself. There is no central point of failure, making it DoS resistant.

Make a new file named bitcoin.conf (not bitcoin.conf.txt! You might have to go into Control Panel > Appearance and Personalization > Folder Options > View and uncheck 'Hide extensions for known file types'). Paste this into it:rpcpassword=<A LONG RANDOM PASSWORD THAT YOU DON'T HAVE TO REMEMBER>server=1

Dependencies for running FROM SOURCE:

Bitcoin 0.5.0 or higher

Python 2.5 or higher

python-argparse for Python 2.6 and lower

Twisted (Ubuntu package python-twisted)

Additional options of interest: -w PORT: Listen for workers on a port other than 9332. -a BITCOIN_ADDRESS: Mine to this address instead of requesting one from Bitcoin.

In the time since P2Pool's original announcement it has evolved considerably. I thought having to wade through hundreds of pages of inapplicable cruft about old versions of the software to get to useful information was a disservice to people here, so I split off the old discussion to a separate archival thread.

P2Pool has come a long way since its humble beginnings: It's now a completely realistic solution for a great many miners. The software is still rapidly developing but it is reliable, featureful, and, of course, P2Pool is critical for the health and welfare of the Bitcoin system: Our trust in the Bitcoin system depends on it being highly decentralized. P2Pool prevents the centralization that non-distributed pools create. This is important enough to people that P2Pool miners are currently being paid by Bitcoin users to participate. P2Pool pools payments but mining decisions are still left to all the miners just as bitcoin was intended to work.

This "pool" (really a decentralized/distributed network just like Bitcoin) is still attractive even for people who aren't thinking about the health of Bitcoin overall. P2pool's decentralization is accomplished without compromising on miner profits and, unlike solo mining, while still allowing stable income. The things which p2pool can't do, like provide the utmost low variance (PPS) are offset by the lack of fees and by removing the risk of cheating by pool operators (which is almost undetectable if only done in moderation).

P2Pool isn't ideal for low speed (e.g. CPU) miners, and may never be— but it's absolutely a no brainier for anyone who would even consider solo-mining and a good majority of the people in between.

Everyone should start using p2pool. It's the most innovative things since bitcoin itself. It bothers me that Gavin has try to convince Tycho (of deepbit) of his multi-sig proposal before he can implement it, because if deepbit decides to not use the new code, it's dead in the water. And that's so wrong. So people, wake up and use p2pool.

I see the same error when running p2pool and bitcoind on the same (fairly underpowered) system, an asus eeebox with intel atom cpu.There are load spikes every now and then where bitcoind and p2pool together peg the cpu at 100% and then these errors appear.

It seemed to cause more than average orphans and dead shares in my case so I now run p2pool and bitcoind on a faster system, and I've never seen the error there.

but the graphs do not work, from what I have read it seems the problem is not having rrdtool, however I'm having trouble finding a current win32 version of rrdtool, it is also not in activestate.

Thanks

bitcoin, 2nd most popular currency used by criminals.bitcoin, 2nd most popular currency used by criminals.bitcoin, 2nd most popular currency used by criminals.bitcoin, 2nd most popular currency used by criminals.bitcoin, 2nd most popular currency used by criminals.The probability that you too are a criminal, is very high.

does the higher acceptance rate of the git version affects client in any way? if a lower difficulty solution is found does it still look for another one (because the lower difficulty solutions dont really count as shares)?

I see the same error when running p2pool and bitcoind on the same (fairly underpowered) system, an asus eeebox with intel atom cpu.There are load spikes every now and then where bitcoind and p2pool together peg the cpu at 100% and then these errors appear.

It seemed to cause more than average orphans and dead shares in my case so I now run p2pool and bitcoind on a faster system, and I've never seen the error there.

I have noticed it does occur when the cpu spikes to 100%.. would a sempron 145 and 2 gigs of ram be considered underpowered?