Well, the problem, as I understand, is that lcharles123 has the power of forging with my balance for 1440 blocks, and his fork entered in a loop without end.
Maybe it is not correct to ask others for blacklisting anybody. In that case, the solution by myself will be based on the same thing than the problem, that is, the fact that my forging power is > 80%. So, here is what I can do:
- I setup another node, while keeping my original node intact
- I blacklist my original node patapato.ddns.net, and put nodes of lcharles123 and tiker as wellKnownPeers, in order to ensure that my new node sync with the other fork
- I wait to fully synchronize the forked blockchain
- I wait for the blockchain going back to the block 277935, the block in which lcharles123 forging power begins, as this fork is repeatedly going back to that block height
- In that client, in that moment, I transfer all my 22 M Nas stake to another account of myself, in order to take out all the forging power from lcharles123 in that fork
- I stop forging on my original client, in order to not conflict and let the block height grow in the forked chain
- I wait to the end of the leasing on that fork, at block height higher than 278461
- I restart forging on my original client (on this blockchain I didn't transfer my stake)
In that moment, the loop in that fork will be over, and I will not forge on it. So, it will be a fork with much less forging power and much lower block height. Anyway, the network should resync to one of both forks, and this time, if any forger try to go back with an old saved blockchain file he will not success.