The issue is when you search to see if they work the first results say they don't
Because people who don't know what they are talking about keep repeating it. Soon the hardfork will take place, and p2pool will be compatible with all ASICs. Now is the time to break this meme.
I could understand your point if it was a comment by a random user but when it was a BFL Engineer what else can you be expected to think - They can not be classed as not knowing what they are talking about.
Will the new units have the same problem as the old Singles where it wouldn't stop working on a problem for 5 seconds making it useless for p2pool?
The answer is yes.
Regards,
BF Labs Inc.
So to clarify when using P2pool it is your local bitcoind that is issuing the response to the getwork request that is then relayed through the p2p node and then to your miner?
The point I am trying to make here is this - If for example you are mining against a traditional PPS pool and you have written a proxy that sits between your miner and the pool. This proxy checks the difficulty of the solved block before forwarding it to the pool. If the proxy receives a solved block that meets the difficulty it then forwards it to your local bitcoind. The local bitcoind will reject this solved block because the Merkle tree is different for the two bitcoind servers preventing you from "stealing" the block.
What I am trying to understand here is when using p2pool if your local bitcoind is issuing the getwork then using the proxy to intercept a solved share of required difficulty from your miner and sending that straight to the local bitcoind and not back to the p2pnode why would it not be accepted and the wallet be credited with bitcoins and the p2pnode would be none the wiser. So effectively you would be getting paid for shares and then take the full reward for yourself?