Trust no-one ... use P2Pool.
Easy.
Wow, thank you for bringing
P2Pool to my attention. I'd never heard of it before, but it's an ingenious idea.
What do you mean:
Just remember to setup a good p2pool mining setup as good as the best ones on p2pool.
Otherwise the other miners on p2pool with a better setup are taking some of your BTC ...
?
... and to add more explanation
A share on the p2pool share chain is pretty much the same as a block on the Bitcoin block chain.
You don't send out a p2pool share and get it every time.
If 2 p2pool shares are sent out, built off the same previous p2pool share, one of them will not be paid.
Add on top of that, the p2pool share chain averages a new share every ~30s instead of ~600s like the block chain, so network connectivity and latency has 20x the effect.
For the Bitcoin block chain, to get the least block orphans, a pool (or solo) must ensure it is well connected, has low block distribution latency to the rest of the bitcoin network, is able to process incoming shares quickly, and, of course, the pool itself isn't struggling to get enough CPU for bitcoind
Thus on p2pool the same issue exists with p2pool share chain shares.
The p2pool nodes with the same attributes above will lose fewer shares.
When you notice that something like 10% of p2pool shares are DOA/Stale you need to realise that is only the average.
So if someone is consistently getting 5% DOA/Stale due to having a good setup, that means 95% of their work is being paid instead of only 90% like the p2pool average.
i.e. they get a better share of each block for the work they submit.
Every new share on the p2pool share chain means you need your p2pool to know about it as quickly as possible and switch your miners to the new work based on the latest successful share in the share chain.
Any delays with those ~30s p2pool share chain updates and that delay represents how much time of the ~30s average you are hashing work that wont be paid.
Using a remote p2pool, of course, exacerbates the latency issue due to the ~30s average.
Using a miner that takes time to switch work also makes that a problem since it is all about what % of ~30s you are working on the latest p2pool share chain share.
...
Also ensure that your miners are submitting stale shares. The standard firmware on Ants for example discards them... Even though they may be valid solutions for a block.
~95% of DOA/Stale shares on p2pool that are also blocks, are valid bitcoin blocks.