lets explain situation
we discovered again daniels pool and lot hashrate and some wallets on one fork
and much more wallets including reactor but less hashrate are on other fork (different chains)
last time this happend daniels chain was declared mainchain and lot people had to fix their wallet with backup blockchains
this time and there i take full responsibility we choose the majority of wallets are the main chain
which now in fact create the situation that the main chain have less hashrate because danbi pool just had overwhelming hashrate
its night in bulgaria daniel sleep
so we me and alex had to make a call
i was so pissed with the situation (like i guess everyone else too) that the network fork again that i said
lets go the as much decentralized path as possible
so actual situation is the backbone nodes do sync again
and we try this time use addnode and listen=1 everywhere
and let the network consolidate by itself
the reactor and some other big POS wallets are on the chain that is visible here
https://chainz.cryptoid.info/dmd/at least 34 wallets are sync with that chain
danbi pool and lot hashrate is on other chain
please everyone mining in danbi pool stop mining go solomining
once u resynced with correct chain
or just stop wallet and wait after trigger is done and network stabilized
i strong suggest that after trigger before pools go online again they make a agreement about how they can make sure no one of them go over 40% of network hashrate
to avoid that in future 51%+ pool fork themself away of majority of network wallets
in my opinion this last fork was homegrown and no attack
the first one that happend did show clear sign that go far above some random unlucky event
