No, was actually stale.
I've changed the flagging of it.
On the web it was an immediate orphan coz it was already stale, but any block submitted that isn't worked on is auto-flagged as orphan until I manually check everything then flag it.
I've looked through everything to be sure, but yep it was a stale share.
The share came into the Silicon Valley node at 2017-08-10 20:28:30.533 UTC
But all nodes and the main pool had already switched to the poo block by then.
I've changed the flagging of it.
On the web it was an immediate orphan coz it was already stale, but any block submitted that isn't worked on is auto-flagged as orphan until I manually check everything then flag it.
I've looked through everything to be sure, but yep it was a stale share.
The share came into the Silicon Valley node at 2017-08-10 20:28:30.533 UTC
But all nodes and the main pool had already switched to the poo block by then.
Kano, do you advertise your pool bitcoin IP addresses so that others can connect to it to help with rapid propagation to reduce the possibility of stales? I have a full node running in the SW part of the US that I can force connect to your node if it would help.
M
That's orphans, that are a different creature.
A stale is a share that gets to the pool after the block has changed.
Basically it's just a miner that was working away normally, then a block change occurred, then as the work was coming into the miner, but before it switched to it, the miner found a block.
Really it's a non-event and I don't think any other pool would actually tell you about them
In my case, I show any and every attempt at a block on the Blocks page, no matter what it is or when it gets to the pool.
Yeah I really do probably have the best propagation of blocks of any pool on the network
I've nodes near every Fibre Relay node, and some of those nodes no one mines to coz their job is purely to get the blocks to every relay as fast as possible.
. Actually almost 4 am where I'm at! 
