NAS :: Descendant of NXT 100% PoS|More Exchanges|WinNAS is ready!

[User1397367406]

Both of my nodes seem to have gone off on a fork or something...
Recent blocks:

Code:

Height	Date	Amount	Fee	Nr TX	Generator	Payload	Base Target
277935	06/04/2015 10:18:08	0	0	0	NAS-87P5-WQH2-4E4A-A7G8W	0 B	40498 %
277934	05/04/2015 10:01:21	0	0	0	NAS-5HZF-TPQ5-GSHF-7GV33	0 B	20249 %
277933	05/04/2015 10:00:19	0	0	0	NAS-5HZF-TPQ5-GSHF-7GV33	0 B	19596 %

My local node keep trying to forge block 277935 since it hasn't seen a block since yesterday.  It seems that some of the other nodes are rejecting it.

My VPS is in agreement with my local node.

I'm restarting my nodes now to see if it helps.

Edit:
Patapato:
Are you running custom nodes?  It looks like you or someone else is generating blocks with invalid signatures:

Code:

[2015-04-06 10:26:04.151] DEBUG: Will pop block 5937549519284143825 at height 277935
[2015-04-06 10:26:04.153] DEBUG: Blacklisting 89.247.146.250 because of: nxt.BlockchainProcessor$BlockNotAcceptedException: Generation signature verification failed
[2015-04-06 10:27:06.217] DEBUG: Will pop block 5937549519284143825 at height 277935
[2015-04-06 10:27:06.219] DEBUG: Blacklisting 88.130.194.138 because of: nxt.BlockchainProcessor$BlockNotAcceptedException: Generation signature verification failed
[2015-04-06 10:27:51.778] DEBUG: Will pop block 5937549519284143825 at height 277935
[2015-04-06 10:27:51.780] DEBUG: Blacklisting 89.247.161.67 because of: nxt.BlockchainProcessor$BlockNotAcceptedException: Generation signature verification failed
[2015-04-06 10:28:17.989] DEBUG: Blacklisting 89.247.161.163 because of: nxt.BlockchainProcessor$BlockNotAcceptedException: Generation signature verification failed
[2015-04-06 10:29:01.112] DEBUG: Will pop block 5937549519284143825 at height 277935
[2015-04-06 10:29:01.114] DEBUG: Blacklisting 88.130.194.55 because of: nxt.BlockchainProcessor$BlockNotAcceptedException: Generation signature verification failed

I think these messages "nxt.BlockchainProcessor$BlockNotAcceptedException: Generation signature verification failed" are because of my node:
* these IPs resolve to my internet provider
* My IP changes every day as i'm on dynamic IP
* The DNS name for my node is updated periodicaly
* the peer name, of my node, displayed on the client resolves to different IP. Don't know if the client stores also the IPs.
* As my IP changes, depending on the DNS update, blocks generated from my node should trigger these messages as the Signature is bound to the provided host name.

The network is still vulnerable to all kind if things, with only 2-3 nodes.
During the last couple of days i had some periodes where my node forged all the blocks.
Not sure if this was the exact network status or if it synced since then.
A couple of days back i had some similar strange things going on as suddenly the last block list updated itself.

My node seems to be relatively in sync with Patapatos:

Code:

279184	4/6/2015 21:03:14	0	0	0	NAS-5HZF-TPQ5-GSHF-7GV33	0 B	14119 %
279183	4/6/2015 20:59:10	0	0	0	NAS-5HZF-TPQ5-GSHF-7GV33	0 B	7060 %
279182	4/6/2015 20:57:52	0	0	0	NAS-H5AW-7J9F-7VCY-DJ8NB	0 B	5430 %
279181	4/6/2015 20:56:41	0	0	0	NAS-H5AW-7J9F-7VCY-DJ8NB	0 B	4589 %

[patapato]

@kennyP and @lovewiki, thank you!! , I agree.


@tiker,  and @User1397367406 (and everybody),
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.

Maybe it was not a good idea to lease my balance to a non stable node , User1397367406 is right, we are very few forgers, any loose of stability is more critical than in a strong network. Anyway, the forked block 277935 in tiker's node was not forged by that address. But I was not forging, maybe User1397367406 didn't forged on that time too, or had "Generation signature verification failed" problems, so the network was without stable forgers for a while, favoring forks.

Anyway, our main blockchain is still alive and healthy, I am synchronized with NAS-5HZF-TPQ5-GSHF-7GV33 (User1397367406 forging account), as we both are forging blocks now on the same blockchain.

I have a list of 25 up-to-date peers on my client, 20 of them connected. But the list of nodes is redundant, many nodes are repeated (I don't understand why). I have 6 non-repeated peers:

cb2.flipflop.mooo.com,
88.193.20.204,
106.187.102.227,
funkyvps3.funkymonkey.org,
99.227.137.145,
222.92.62.194.

There are only 3 peers in tiker`s public node, one of them is me:

99.227.137.145
patapato.ddns.net
106.187.102.227

So, @tiker, the last block on your chain, 277935 forged by NAS-87P5-WQH2-4E4A-A7G8W, does not exist on our blockchain. The previous one is correct. I think (and hope) that your nodes should synchronize by themselves.

[patapato]

My local node keep trying to forge block 277935 since it hasn't seen a block since yesterday.  It seems that some of the other nodes are rejecting it.

@tiker, don't try to forge until your node is synchronized, as you will have rejections, or worst, you will be strengthening your own separated fork.

[lcharles123]

@kennyP and @lovewiki, thank you!! , I agree.


@tiker,  and @User1397367406 (and everybody),
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.

Maybe it was not a good idea to lease my balance to a non stable node , User1397367406 is right, we are very few forgers, any loose of stability is more critical than in a strong network. Anyway, the forked block 277935 in tiker's node was not forged by that address. But I was not forging, maybe User1397367406 didn't forged on that time too, or had "Generation signature verification failed" problems, so the network was without stable forgers for a while, favoring forks.

Anyway, our main blockchain is still alive and healthy, I am synchronized with NAS-5HZF-TPQ5-GSHF-7GV33 (User1397367406 forging account), as we both are forging blocks now on the same blockchain.

I have a list of 25 up-to-date peers on my client, 20 of them connected. But the list of nodes is redundant, many nodes are repeated (I don't understand why). I have 6 non-repeated peers:

cb2.flipflop.mooo.com,
88.193.20.204,
106.187.102.227,
funkyvps3.funkymonkey.org,
99.227.137.145,
222.92.62.194.

There are only 3 peers in tiker`s public node, one of them is me:

99.227.137.145
patapato.ddns.net
106.187.102.227

So, @tiker, the last block on your chain, 277935 forged by NAS-87P5-WQH2-4E4A-A7G8W, does not exist on our blockchain. The previous one is correct. I think (and hope) that your nodes should synchronize by themselves.

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

[tiker]

My 99.227.... node is always forging with account NAS-87P5-WQH2-4E4A-A7G8W and a balance just over 5000 now.  Normally it doesn't forge any blocks because of the other two forging accounts with a much higher balance.  Should both of the big forging nodes go offline at the same time, my node should spit out a couple of blocks to keep things going until they return.

For whatever reason, both of my nodes didn't accept any blocks after 277934.  My clients probably didn't see anyone forging so my local client attempted to push out block 277935 with the account above.

I've restarted both NAS clients and neither of them have changed at all.  Both are stuck at 277934, both think that my local client is correct for block 277935.

A lease going to an unstable forging node shouldn't cause an issue like this.  In fact, I don't even see forged blocks from NAS-VBK9-5ZXA-CJQ8-GEWVU so I don't even think it's forging.

I'll leave both nodes sitting for now and see if they correct things on their own.

[tiker]

Both nodes have started following a fork with a 1.5 day gap in the middle...

Code:

Height	Date	Amount	Fee	Nr TX	Generator	Payload	Base Target
277952	06/04/2015 21:21:49	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	1395 %
277951	06/04/2015 21:21:44	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	2791 %
277950	06/04/2015 21:20:56	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	3488 %
277949	06/04/2015 21:17:45	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	1744 %
277948	06/04/2015 21:17:18	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	3488 %
277947	06/04/2015 21:17:02	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	6976 %
277946	06/04/2015 21:14:45	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	3488 %
277945	06/04/2015 21:14:02	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	4867 %
277944	06/04/2015 21:11:15	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	2434 %
277943	06/04/2015 21:11:05	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	4867 %
277942	06/04/2015 21:10:25	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	7301 %
277941	06/04/2015 21:09:26	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	7425 %
277940	06/04/2015 21:07:58	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	5062 %
277939	06/04/2015 21:07:51	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	10124 %
277938	06/04/2015 21:07:29	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	20249 %
277937	06/04/2015 21:07:24	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	40498 %
277936	06/04/2015 21:07:21	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	80996 %
277935	06/04/2015 21:03:50	0	0	0	NAS-3S5R-Q4ZL-QUEA-BWAP2	0 B	40498 %
277934	05/04/2015 10:01:21	0	0	0	NAS-5HZF-TPQ5-GSHF-7GV33	0 B	20249 %
277933	05/04/2015 10:00:19	0	0	0	NAS-5HZF-TPQ5-GSHF-7GV33	0 B	19596 %
277932	05/04/2015 09:59:53	0	0	0	NAS-5HZF-TPQ5-GSHF-7GV33	0 B	39191 %
277931	05/04/2015 09:57:52	0	0	0	NAS-5HZF-TPQ5-GSHF-7GV33	0 B	19596 %

[patapato]

I created a new account, and I sent it 1000 NAS (transaction 18419636354574564653). I was not forging in that instant. But I didn't get blocks, so I started forging again. In my blockchain it is at height 279190 forged by me, but in tiker's public node (http://funkyvps3.funkymonkey.org:7873/) it is at height 277935 forged by NAS-VBK9-5ZXA-CJQ8-GEWVU (with a balance of 64 NAS).

I am observing in real time how both forks are fighting, as I see the block height going back and forth in both nodes. Interesting.

[tiker]

I created a new account, and I sent it 1000 NAS (transaction 18419636354574564653). I was not forging in that instant. But I didn't get blocks, so I started forging again. In my blockchain it is at height 279190 forged by me, but in tiker's public node (http://funkyvps3.funkymonkey.org:7873/) it is at height 277935 forged by NAS-VBK9-5ZXA-CJQ8-GEWVU (with a balance of 64 NAS).

I am observing in real time how both forks are fighting, as I see the block height going back and forth in both nodes. Interesting.

My nodes are stuck at 277935.  They are sticking with block 277934 and attempting to link 277935 to it.  At first when my node was forging, it was trying to stick it's own forged block there but other nodes didn't agree.  A block forged by NAS-3S5R-Q4ZL-QUEA-BWAP2 was there for a short time but it removed it because other nodes didn't agree.  My nodes keep destroying all blocks from 277935 and onwards and trying to rebuild them.  That is why you now see your transaction in that block but it'll be destroyed soon as it attempts to rebuild it again.

My nodes appear to be rejecting the block 277935 that other nodes are trying to pass to it.  It gives a bad signature message and bans that IP for 15 minutes or so.  That would make me think that my block 277934 is different than the same block number everyone else has.

I had shut down my local NAS client over night and just started it up again.  I'll see what it does.

I just hope bter's node isn't suck like mine.  It won't be good if it is.

[patapato]

My nodes appear to be rejecting the block 277935 that other nodes are trying to pass to it.  It gives a bad signature message and bans that IP for 15 minutes or so.  That would make me think that my block 277934 is different than the same block number everyone else has.

Your block 277934 is the same as ours. It is block 17565891496255612524, its timestamp is 32493681, and its signature is a31e0ae7a1e94c3175271157a43b6cd64eaff47825278bad28fdad6699f46f0147c3b2eea29fb7a a8a0b90cdaf224ddf9e7afbf7d2de3a038b5ef25c87929fef

My node is stuck at height 279190, the one just after my transaction at 13:39:49 (GMT+2), similarly to your 277935. It advances some blocks, then it goes back, sometimes to the previous valid one 279189. I can not see other forgers when I am not forging. I restarted my node 2 hours ago, but it is the same (less peers now).

I told you to not forge, but with so few forgers I'm wrong. It is probably better now that all of us try to forge, and the NAS distributed system will decide. In fact, I created other accounts in order to distribute my forging power leasing smaller quantities to others. I can not do it until the network stabilize to one winner fork.

@User1397367406, I don't see you forging neither on my client nor on tiker's public client, are you not forging now?, or are you in yet another fork?

[tiker]

I think the bter.com node is stuck with my nodes.

The peer list from my public node:

Code:

Address	Weight	Downloaded	Uploaded	Application	Platform
  cb2.flipflop.mooo.com	0	47 MB	71 KB	NRS 1.1.3.N1	CubieBoard2
  99.227.137.145	0	1 MB	1 MB	NRS 1.1.3.N1	PC
  patapato.ddns.net	0	64 MB	205 KB	NRS 1.1.3.N1	Win7-64b
  106.187.102.227	0	4 MB	4 MB	NRS 1.1.3.N1	PC
  cb2.flipflop.mooo.com	1'972'503	80 MB	125 KB	NRS 1.1.3.N1	CubieBoard2

If you look at the downloaded MB counts, 3 nodes which agree are all 50+ MB and are constantly trying to update my public node with their block chains.

My local node (99.227....) and bter's node (106.187...) are both under 10 MB which makes me think they're in agreement with my public node's chain and are trying to continue from there.  We need to find a way to get the nodes to resolve the issue on their own.  I won't be good for us if we ask bter to reset their node...

I'll start forging on both nodes again.  The account on my public node will be forging with about 8 NAS and my local node will be forging with a little over 5000 NAS.

Another thing to point out... The consoles for both nodes are reporting signature errors for the blocks.  I've also noticed that the hallmarked nodes are not showing as hallmarked nodes all the time.  (Weight = 0 in the list above.)  I have seen evidence of a signature generation problem from my public node when I attempted to send out a transaction in the past.  There might be more to this problem than just a forked chain.

[plopper50]

I think the bter.com node is stuck with my nodes.

The peer list from my public node:

Code:

Address	Weight	Downloaded	Uploaded	Application	Platform
  cb2.flipflop.mooo.com	0	47 MB	71 KB	NRS 1.1.3.N1	CubieBoard2
  99.227.137.145	0	1 MB	1 MB	NRS 1.1.3.N1	PC
  patapato.ddns.net	0	64 MB	205 KB	NRS 1.1.3.N1	Win7-64b
  106.187.102.227	0	4 MB	4 MB	NRS 1.1.3.N1	PC
  cb2.flipflop.mooo.com	1'972'503	80 MB	125 KB	NRS 1.1.3.N1	CubieBoard2

If you look at the downloaded MB counts, 3 nodes which agree are all 50+ MB and are constantly trying to update my public node with their block chains.

My local node (99.227....) and bter's node (106.187...) are both under 10 MB which makes me think they're in agreement with my public node's chain and are trying to continue from there.  We need to find a way to get the nodes to resolve the issue on their own.  I won't be good for us if we ask bter to reset their node...

I'll start forging on both nodes again.  The account on my public node will be forging with about 8 NAS and my local node will be forging with a little over 5000 NAS.

Another thing to point out... The consoles for both nodes are reporting signature errors for the blocks.  I've also noticed that the hallmarked nodes are not showing as hallmarked nodes all the time.  (Weight = 0 in the list above.)  I have seen evidence of a signature generation problem from my public node when I attempted to send out a transaction in the past.  There might be more to this problem than just a forked chain.

How do you know bter's node is (106.187...)?

[User1397367406]

@User1397367406, I don't see you forging neither on my client nor on tiker's public client, are you not forging now?, or are you in yet another fork?

I was forging all the time, just re-started my node as i was forging on my own little fork ;(
The branch might have accured arround block height 279182 as from what i saw i started forging one block after another and still was till now (as far as i could tell from the block list).
The Log doesn't show anything too interesting ...
The log has some of the following:

Code:

Failed to analyze hallmark for peer 188.86.*.*, java.net.UnknownHostException: patapato.ddns.net

As far as i can tell, during the last days there where several periodes where my node was forging block after block.
It's hard to tell with the log as there is only the timestamp of a block generated by my node.

[User1397367406]

I stopped forging after the re-start.
Right now i only have these nodes connected:
funkyvps3.funkymonkey.org and 99.227.*.*
patapato.ddns.net comes and goes ...

[patapato]

I think the bter.com node is stuck with my nodes.

But my node is in the longer chain. Several blocks under 279190 were forged by User1397367406 node (NAS-5HZF-TPQ5-GSHF-7GV33), and validated by mine. So, two big forgers with a hallmark agree until block height 279190, while yours is at 277941 now. I also notice that, when I stop forging, your blockchain goes on, gaining height (forged almost all by lcharles123 account), but when I restart forging, your blockchain goes back to near 277935.

I notice another faulty thing, and I am beginning to understand (I'm afraid). lcharles123 has only 64 NAS, but he is forging with ~22 million NAS of effective balance. That is, lcharles123 is forging with my leased balance. But my leasing finished after 1440 blocks!! More properly, my leasing had to finish on block 278461, from block 277021. Here is the admin "Get Account" info of NAS-VBK9-5ZXA-CJQ8-GEWVU:

Code:

{
    "publicKey": "9b4c3453beb2707c7142e67a837dc8783607e209ce3992bcca1c37c7294ae111",
    "lessors": [
        "13029142609628990748"
    ],
    "guaranteedBalanceNQT": "0",
    "balanceNQT": "6400000000",
    "accountRS": "NAS-VBK9-5ZXA-CJQ8-GEWVU",
    "account": "17109047578379265575",
    "effectiveBalanceNXT": 22109012,
    "unconfirmedBalanceNQT": "6400000000",
    "forgedBalanceNQT": "60100000000"
}

Soooo... , I suggest you, @tiker, to blacklist the node of lcharles, as he is "ilegally" forging with my balance and confusing the network. And I ask you, @lcharles, to stop forging with my balance, as my leasing already finished on the longer fork of the blockchain. Otherwise I have to think that you asked me by PM a balance to forge with in order to just attacking the NAS network.

[User1397367406]

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

Code:

Height 	Date 	Amount 	Fee 	Nr TX 	Generator 	Payload 	Base Target
277940	4/7/2015 22:44:05	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	1266 %
277939	4/7/2015 22:44:00	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	2531 %
277938	4/7/2015 22:43:58	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	5062 %
277937	4/7/2015 22:43:46	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	10124 %
277936	4/7/2015 22:43:23	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	20249 %
277935	4/7/2015 22:43:22	1'000	1	1	NAS-VBK9-5ZXA-CJQ8-GEWVU	160 B	40498 %
277934	4/5/2015 16:01:21	0	0	0	NAS-5HZF-TPQ5-GSHF-7GV33	0 B	20249 %
277933	4/5/2015 16:00:19	0	0	0	NAS-5HZF-TPQ5-GSHF-7GV33	0 B	19596 %

Blocks after 277934 appearing and dissapearing ...
Very strange thing and it seems we have, again(sigh) a messed up network.

[tiker]

Soooo... , I suggest you, @tiker, to blacklist the node of lcharles, as he is "ilegally" forging with my balance and confusing the network. And I ask you, @lcharles, to stop forging with my balance, as my leasing already finished on the longer fork of the blockchain. Otherwise I have to think that you asked me by PM a balance to forge with in order to just attacking the NAS network.

Chances are, lcharles' node is stuck at a block near mine.  That's the only reason why lcharles' node would continue trying to forge blocks with your lease.  That node hasn't reached a  number where the lease ended.  That could be why my node is trying to accept blocks forged by lcharles' node and why signature errors are appearing for blocks you forge with your account - my nodes think that you should not be forging with your balance yet and thinks it's still with lcharles.

I still don't understand why leasing your balance to someone else with an unstable node could cause this issue.  In theory, it shouldn't.

[tiker]

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

Code:

Height 	Date 	Amount 	Fee 	Nr TX 	Generator 	Payload 	Base Target
277940	4/7/2015 22:44:05	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	1266 %
277939	4/7/2015 22:44:00	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	2531 %
277938	4/7/2015 22:43:58	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	5062 %
277937	4/7/2015 22:43:46	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	10124 %
277936	4/7/2015 22:43:23	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	20249 %
277935	4/7/2015 22:43:22	1'000	1	1	NAS-VBK9-5ZXA-CJQ8-GEWVU	160 B	40498 %
277934	4/5/2015 16:01:21	0	0	0	NAS-5HZF-TPQ5-GSHF-7GV33	0 B	20249 %
277933	4/5/2015 16:00:19	0	0	0	NAS-5HZF-TPQ5-GSHF-7GV33	0 B	19596 %

Blocks after 277934 appearing and dissapearing ...
Very strange thing and it seems we have, again(sigh) a messed up network.

So your client is stuck where my nodes are.  That means that the blocks creating the longer chain contain something bad that those nodes accepted for some unknown reason.

If a new node is stuck at the same spot as my nodes then chances are we won't be fixing my nodes to reach patapato's block height.  We could try re-syncing again with my nodes shut down to see what happens but that might make things worse for the network.

[patapato]

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:

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:

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:

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?

[tiker]

Blacklisting lcharles node might be a bit extreme.  If it was done by lcharles setting his node then it probably wasn't intentional.  I don't think it's lcharles' blockchain reset because the blocks between 277021 and 278461 would have been forged with his account.  The last 100 blocks or so that I can see on both clients were forged by NAS-5HZF-TPQ5-GSHF-7GV33 (User123456789?).  Even if lcharles forged one fork, reset and forged the new fork, the blocks would still have his account on them from either fork.  I'd almost think lcharles was on a fork before the lease was set, started forging on his own and the rest of us didn't agree and accepted forged blocks from the 2nd highest forger.  That doesn't explain how I got stuck before the rest of you though...

To speed things up in getting this fixed quicker, I'd suggest we find a chat room for everyone with a node, compare chains, find a solution (hopefully without resetting bter) and going with it.  My access to IRC networks is limited most of the time being at work but I can join XMPP chat rooms any time.  If everyone agrees, let's set a time and discuss...

[tiker]

How do you know bter's node is (106.187...)?

I don't know for sure, it's an assumption.  This node became available the same day bter fixed their NAS withdrawals for me to get a few NAS from the exchange.  This IP is also visible on the NFD network which bter also supports.

I could be completely wrong calling 106.187.... bter's node but that's what I call it.