pull down to refresh
It could perhaps even be the case that the block was found by a pool participant even after Foundry saw the Antpool block, but before they had updated all the jobs. It would still make sense and not be malicious for a pool to mine on their own block when they have one.
Wow you might be right. It seems this is what actually happened.
https://bnoc.xyz/t/two-block-reorg-at-height-941880/97/20
What a massive coincidence though.
Could be.
But even in this scenario I believe the usual bitcoind behaviour is to broadcast this block out to its direct peers.
As I mentioned above, Bitcoin Core nodes will request and store blocks in competing chaintips with the same PoW as their best chaintip, but they will not announce those blocks to their own peers. Even if Foundry had announced it after having found it, the block could have not made it beyond the Foundry nodes’ peers if they all had seen the competing block before it, or it would have possible made it another hope from a few peers before getting blackholed.
But that still seems like a very big coincidence for noone else to have seen the block in time. The direct peers of Foundry should have still seen it when it was found. But so far I haven't seen anyone claiming to have seen the Foundry block 941882 before 15:55:00.