pull down to refresh
I thought you turned them off so I didn't tag you when I found that the default pool was being rerouted. It looked like they were flip flopping between chaintips in the beginning, then they chose the main tip for a few hours, then it switched to BIP-110 for a longer time, then back to the main tip. From a pool perspective, the only moment to defend the 110 chaintip was when they were of equal length. But once it moved past the split, it should have stayed on the main tip. Deviations from that were likely interference, so if you're on Ocean's default pool, you definitely got swapped around.
I don't know enough about how share difficulty targeting works on ocean's stratum (and datum) backend software, because that stack is closed source. What could have happened is that you got too high share difficulty with each tip reset and then needed time with adjusting, but that is me guessing, based on how I've seen Ocean do share difficulty adjustments a little under 2 years ago when I tested it with a bitaxe.
Yesterday I noticed my hash rate had diminished severely. I assumed some of my little miners were off line. When I checked they were all running normally. It was a puzzle to me. I figured it was a BIP-110 problem, but I don't even run datum, so I was confused. Late in the afternoon everything returned to normal. Is it realistic to assume I got hijacked?