except sometimes those stales that solve blocks... are, well, a stale right after a block was found. re the shenanigans that go on when switching from one block to another
not sure if p2pool would proceed along it's own chain or not? either way, it's a block that'll most likely be orphaned. that's when the slow getblocktemplate matters
Bullshit.
After heaps of messages on this subject on this very thread (last was mine a few messages ago) you still don't understand that p2pool doesn't rely on getblocktemplate result being available to build the coinbase miners are working on.
p2pool is connected to the bitcoin P2P network and detects blocks
before a getblocktemplate result is available for the new block and present a valid coinbase to miners ASAP. So there's
absolutely no reason a "stale p2pool share" block would have more chance of being orphaned than any other block.
I think you're the one that doesn't understand, lol.
Maybe you should look at the specifics presented.
Listen, there's a reason why so many shares get 'punished'.
ed: since I've disabled the 'punish' feature you'll be able to see all the orphans. most of the time it's just one, the person unfortunate enough to have the share right before the new block, but just wait for a block where you have 2 or 3 orphans coming off of it, some will have a received time after the new block, but still be working on old block.
If you want to be taken seriously present your case clearly "a block that'll most likely be orphaned" is not the same than an orphaned p2pool share. It's a misleading statement at best FUD at worst, don't be surprised to see "bullshit" in response.
I usually don't read your posts in details anymore as I can't understand much of it without disproportionate efforts, but what reads like a risk of orphaned blocks with no basis is enough to catch my attention...