Okay, this is probably an idiot question, but here it goes. I really support the whole concept behind P2p, so I tried to mine in this pool.
I had low ping with coincadence.com, so I pointed my miner their...
now, all I did was point my miner their via cgminer.... if I'm pointing to a node, do I need to run an instance of p2p and bitcoind local?
On the stats page I was getting a hashrate, but on my cgminer output I was getting "share accepted" once every blue moon, and instead I was getting a lot of "stop work requests".
I found a small non-p2p pool with low ping and pointed their, and saw cgminer start spitting out accepted shares constantly.
NOw, I assume this is because the p2p pool has a a bajillion users, whereas the non-p2p pool I found has ~200, so my miner was really only getting a smaller amount of work on the p2p pool (
)
But the more I look into p2p, I'm thinking I may have done something wrong.
Not stupid questions at all...
If you point your miners to a remote node (like windpath's), you do not need to locally run an instance of p2pool or even bitcoind. All you need is a valid bitcoin wallet address to which your portion of the block reward can be paid when a block is found.
The reason you see "share accepted" only once in a blue moon on a p2pool node vs all the time on a regular node has to do with the share difficulty. If you connect to a p2pool node using only your bitcoin wallet address, you will be assigned a share difficulty by the pool. The pool determines share difficulty based upon its total hashing power. You can override this if you want by using +XXXX at the end of your wallet address. For example, if you put 1DevLdogN52pHdjZnsgi4HzreFDB4ZHVre+500 as your username, you're telling the node that you wish it to consider all shares from your miner of difficulty 500 or more. The lower that number, the more "share accepted" messages you'll see.
Remember, however, that those low difficultly shares mean absolutely squat. Their only purpose is to give you visual reassurance that your miners are actually submitting work to the node.
A typical traditional pool will assign you a variable difficulty. For example, if you were to mine on ckolivas' solo pool, that pool dynamically adjusts the share difficulty based upon your hash rate. Again, and especially on his solo pool, those low difficulty shares mean nothing. There are other payout methodologies and share difficulty settings in use, so it can get confusing.
Back to p2pool, the only share you submit that matters is one that at least matches the target difficulty of the share chain. If it does, then your share is added to the chain and if that share happens to be in the payout list when the pool finds a block, you get your coin. Right now, that difficulty is just about 10 million. P2Pool constantly adjusts the share difficulty to try and maintain an average of 30 seconds per share added to the chain (just like Bitcoin adjusts its difficulty every 2016 blocks to try and keep the average block time of 10 minutes).
People have different views on how much hash rate you should have to be mining on p2pool. A good rule of thumb I use is "do I have a high enough hash rate to expect to find 1 share in the average amount of time it would take p2pool to solve 3 blocks". If yes, then you would expect to have at least 1 share on the chain for every block p2pool finds. If we use this rule, we can figure out how much hashing power constitutes the entry point:
Difficulty * 2^32 / hash rate = expected time to find a share
10436491.83 * 2^32 / hash rate = 179100
hash rate = ~250GH/s
Keep in mind that the difficulty is constantly changing and the p2pool total hash rate is constantly changing. For example, while I was typing this reply, the expected time to block for p2pool went from over 16 hours to under 15. This has an effect on the above calculations, which in turn changes the baseline for how much hashing power you should have.
So, how much hashing power should you really have on p2pool? An S3+ typically does it... an S2 is better... an SP20 even better still. If you've got anything under an S3 (like an old S1), then expect to see a ton of variance where you'll go for a number of blocks with no payout at all because you haven't found any shares. This is one of the primary issues p2pool has - the more hashing power the pool has, the greater the variance experienced by individual miners. As you can see from the first post on this page, people have been trying to find a solution for a long time.
Sorry about the long-winded post. I tried to give you as much information as possible to help you better make a decision on whether p2pool is the right choice for you.