[SIGT] pool mining a fork? They mined three consecutive orphan blocks th

[liquid_tension]

Is this pool mining a fork? https://mining-enthusiasts.net/sig/index.php?page=statistics&action=blocks

They mined three consecutive orphan blocks. Then they mined every block since block 86285? Network latency? Blocks are being mined too quickly? Someone trying to reverse transactions? This is a screen shot of the blocks when things started going wacky: https://i.imgur.com/UANnYbF.png

Now this pool is mining every block in its own chain: https://i.imgur.com/z1ay4dv.png

Thoughts?

[Ambros]

Yeah, probably they forked

[liquid_tension]

Yeah, probably they forked

What should I do? Jump on the fork with the most hash, or stick with the baby fork? I'm unclear about what the repercussion might be of continuing to mine on this pool. Thanks!

[liquid_tension]

It looks like the fork is here to stay. Some of the first blocks in the fork are getting 60+ confirmations. Is it possible that this coin could split into two? Should I cut and run?

[Ambros]

It looks like the fork is here to stay. Some of the first blocks in the fork are getting 60+ confirmations. Is it possible that this coin could split into two? Should I cut and run?

I suppose that at some point developers should realise what happened and decide for the longest chain to survive. So mine on the majority chain

[cryptojai]

official statement @discord

SonnysDaytona - heute um 11:38 Uhr
Someone hitting the chain with millions of tiny txs. Floods the seed nodes, they need time to catch up. Not mining different chains, the seed nodes are behind, so that other pool is getting stale blocks. That's the word from Doc.
Pools use different seed nodes, depends how long they take to catch up.