Our network is under attack (by lcharles123)
(important Nxt and NEM community members, including main Nxt developer, don't like Nas)

The attack consist of the following facts and steps:

1.- initially, there is a PoS network properly working, but forgers are few and distribution of forging power is: · forger A: 22 M (me) · forger B: 5 M (User1397367406) · forger C: 5 k (tiker) · others: < 1 k
2.- the attacker asks for more forging power to forger A, by PM
3.- forger A leases his 22 M balance to the attacker for the minimum time, 1440 blocks, until block height EoL (End of Lease); attacker is now the forger with > 80% of forging power
4.- attacker makes a copy of blockchain file at the beginning of his leased time
5.- attacker forge blocks below EoL, then restart his node with the previously downloaded copy at the beginning of his lease, and waits for spontaneous fork, which is easy as he has most of the forging power
6.- lease ends on original blockchain, but lease never ends on his fork, as new blocks are rejected and reseted to the beginning of fork before reaching EoL on that fork
7.- main fork also doesn't advance, as his new blocks are also rejected and reseted to the last block with a transaction
8.- the network reaches a never ending situation, with 22 M stake forging on one fork and the same 22 M stake forging on another fork; Nas is fooled and attacker laughs loudly on us:

Quote from: lcharles123 on April 06, 2015, 10:53:17 PM

My node crash.
It works well for a while, but it seems that gives peaks in memory.

The blockchain stuck height 278461, i'll have to download it again. :/

My node is no public:
nxt.servebeer.com

Notice that EoL block is precisely 278461 !, and he is downloading old copy of blockchain before that height in order to not losing his forging power:

Quote from: patapato on April 06, 2015, 10:03:12 PM

I leased my balance to account NAS-VBK9-5ZXA-CJQ8-GEWVU for 1440 blocks (he asked me for it by PM). The lease transaction was 9204069884770967256 at 02/04/2015 22:05:59 (GMT+1), and the lease started from block 277021 until block 278461. The blocks of problem for tiker are in the middle of this rank.

To worsen things, a trusted forger thought that he was on a bad fork, so he tried to reset his blockchain, stopping forging on his original blockchain and getting in sync with the attacker's fork:

Quote from: User1397367406 on April 07, 2015, 11:18:51 PM

I tried syncing a client on my computer from mid march and so far it seems to sync until block 277934 and 277940 :
...

Solutions?:

I ask you, @User1397367406, to please recover your last original blockchain, as you forged in sync with me at least until height 279189 (06/04/2015 21:10:52, GMT+2), while you are currenly going back to 277934.
I ask every forger to blacklist lcharles node: nxt.servebeer.com (46.105.44.4)
I will distribute my account balance in smaller accounts, roughly the size of the next big forger, in order to have a more equilibrated distribution of forging power

Other suggestions, comments, ideas?