I've read there are ways to mitigate this but they aren't implemented yet or are in infancy still.
...
In other words, I strongly believe that in the future, only miners, or Bitcoin businesses, will deal with holding a full copy of the block chain. Of course regular users will always have the option, and I wonder if the size of the block chain will out pace hard drive technology. Somehow I doubt it, but we'll see.
As long as the block chain is growing due to legitimate uses, I don't see a problem. Complaining that something that is innovative as P2Pool bloats the block chain is nitpicking in my opinion. Same as the people who complained that the default subsidy was a hidden fee. If that's all that detractors of P2Pool can complain about, forrestv has done some fantastic work.
Lulz yes I know that 2nd paragraph was directed at me
I guess using about 6 times the blockchain space compared to DeepBit when mining is nickpicking for some
Also note that it means that all that 6 times is in a single transaction that needs to get around the network as fast as possible - rather than multiple transactions queued up before the blocks actually appear - hmm I wonder how that affects latency on p2pool blocks? Have you thought about that? I don't know because ... my next paragraph ... yeah ignorance is bliss for you?
It actually relates directly to an issue that I've brought up a few times already.
Lack of technical documentation.It's all well and good to run a pool and tell everyone to connect to it with a miner, but when that pool is software you must run yourself and thus there are many issues (not all of them the same of course) that other pools spend a lot of effort dealing with to help with performance - that you the miner must consider yourself, then a lack of documentation showing the technical details and the issues and how they are dealt with is certainly necessary long before bitcoin should risk destruction by having everyone switch to p2pool (well as the software stands at the moment the network would crumble and die and that would be a BIG problem for bitcoin in general if everyone switched to p2pool without being able to switch back when the network dies)
Stability is the next issue.
I've no idea why people in here were telling those with issues to run RC releases of bitcoind to solve their p2pool problems.
It seems the answer was to simply get the latest stable 5 release of bitcoind - as it should have been.
If p2pool suddenly has a dependency on a non-stable release of bitcoind then that is indeed a major p2pool stability issue.
What vetting process is there when changes go into p2pool?
But anyway - regarding that first paragraph - hard drive technology will obviously not be the first issue in the near future - RAM will be an issue long before HDD space is.
Think of the obvious, 2TB HDD's are cheap and easy to get - that's over 1000 times the current blockchain size (well closer to 2000 but anyway)
So then think of that in terms of how much memory bitcoind will need to be responsive compared to how much it uses now - which with p2pool becomes an issue since p2pool needs bitcoind running also ...
Obviously to be able to run bitcoind you will need a lot of RAM compared to now if the number of transactions on the network should ever explode ...