Topic: NAS :: Descendant of NXT 100% PoS|More Exchanges|WinNAS is ready! - page 7. (Read 143776 times)

Glad that NAS is running again!
I can update Russian thread if needed or make Russian translations.
As I said earlier, I'll donate 15 million NAS to whom needed if I get all my NAScoins back: those that on dgex and those that on the way from Poloniex to bter.

Congratulations on reviving NAS!

After everything is settling up again, what are the future plans for NAS? Any roadmap and are there any unique features planned?

NAS blockchain is riding again!!
it's good. 

Just a quick update: my second node successfully synced with the current network, from scratch, in one go, only "nas.wellKnownPeers" was set. 

Thanks for bringing NAS up again. I've just reactivated my client and everything seems to work fine. Great job! Keep it up!

Oops! … I Did It Again 

No, seriously, it was really great teamwork from us three.
I'm glad we did it.

NAS is back on track again 

My main node is connected and forging on block chain fork that the other NAS forgers agreed on.

[User1397367406 make a small wave with his hand] You don't need to see my second node.
This is not the node you're looking for.
...
Wait that's another movie

I'm currently trying to sync a second node from scratch in order to confirm the fork is legit.
Seems to sync all right: block height 87443 and still downloading.
I've put our three node in "nas.wellKnownPeers".
I'll keep you informed.

Well, we stopped the planet from spinning, then reversed the spinning direction to go back in time... wait, that was a Superman movie...

We found that the forked nodes agreed on all of the blocks up to a certain block height which was 277934.
We shut down a node once it deleted the forked blocks back to 277934.
We shut down a second node and deleted the block chain db.

The first node was brought up on an isolated network in a way that peers couldn't connect to it and it wouldn't attempt to connect out to anyone.
The second node was started up with a similar configuration but altered so that it would connect to the first isolated node.
Once the second node had downloaded the block chain from the first node (to verify it would be accepted by a new node) the two nodes started forging on their own disconnected from network under attack.
Transactions that were sent on the network under attack were not confirmed because of the attack.
Those transactions were copied and re-broadcasted on the isolated network and confirmed.  (The ones that were noticed at least with 1440 minute deadlines.)
After a few days, the other NAS forgers (that joined the XMPP chat room posted earlier) compared block chains from the different forked nodes and the isolated node.
After some testing with the different forks, seeing what worked and didn't, checking account balances, transactions sent during the attack, etc. it was decided that the fork running on the isolated network was the best NAS fork to resume working with.
The other forgers modified their clients to join the isolated network hidden from the public network and nodes under attack and ran various tests (forging, transactions, etc.) to verify everything worked.
Once we determined that the isolated network was at a point safe enough to re-introduce to the rest of the public and safe from the attack, we shutdown the nodes together, reconfigured them and started them up together for the rest of the world to access.

That brings us to today.
The NAS forks that were created from the attack will report that forging stopped a few days ago.  This is because the account which caused the problems was doing so with a balance lease that ended at a certain block height.  None of the forging accounts are forging on that chain due to transactions not being confirmed, possible sync issues for new NAS nodes, etc.

Anyone who finds their node stuck at a point where it is not forging or accepting new blocks is on a fork which will not be resolved by the client automatically.  If you are on one of these forks you can either restore a copy of your block chain from a backup taken before height 277934 (Apr. 5th ~14:00 GMT) or delete your node's database file and start over clean.

There is a public node "funkyvps3.funkymonkey.org" which can be added to the "wellKnownPeers" configuration option to get started.  This node is on block chain fork that the other NAS forgers agreed on.  This node also has the GUI interface open to the public at http://funkyvps3.funkymonkey.org:7873 for anyone who wants to login and check things.  This would be a good way to see if your local NAS nodes are on the same fork as the fork the rest of us agreed on.

Hopefully this sort of "attack" won't happen again.  We have learned a few things from this experience.

Well, now it is stable. NXT was running together, but I'm not applying for it.

thank you for your working.

NAS blockchain is riding again!! 

Forging was stable and healthy for 2 days yet, one main fork with several forgers (at least 4). Some transactions were made without problems, with confirmations from other forgers.

I like the old UI to see peers, the peer information is more complete and more clear in the old UI, so I put in my conf/nas.properties:

nas.enableUIServer=true
nas.uiServerPort=7872

and I connect to http://localhost:7872. Next image is what I see now, updating real time, very resdponsive UI. You can take the from here the peers that you want to put on nas.wellKnownPeers, in order that you get your client synchronized with the blockchain.



Compare it with the poorer information on the standard UI (few minutes before):



@tiker or @User1397367406, maybe you want to tell everybody something about how we got the blockchain to survive to the recent attack?

You are welcome


It also set precedents for a defense. I will never rent again, and I will try to take renting out of the Nas software.


In fact, you are not blacklisted long ago, as it was unsuccessful. You earned a good fee for your work of testing the network in a war of forks. Keep it while Nas continue resurrecting, maybe you will buy a new server with it soon


The bigger is the forger, the more trusted he is (because he risks more). But I will partially listen to you, I don't want to forge alone.

Beautiful words.

Then the rent balance may well set precedents for an attack, it seems that the NEM, despite having the remote harvest, the score delegated is separate from node account, and coins found go to respectives account. It is a good substitute to lease balance, but do not know if it is implementable in NXT clone.

The rental period ends in 80 blocks

EDIT: the lease end, you can unblacklist my IP and redownload blocks.

  Funny man you, lcharles123  . Go out from the dark side and join us, the "good guys", we are going to win to the "villain" soon , and the Nas network will work healthy again.

Not bad at all to have this "stress test", as it is being useful to join forces, to understand weakness, failures and even bugs, to strengthen the Nas network, and to have now a core of new developers for the new life of Nas, with different views and criteria than the original ones.

To everybody, wait few time, the network nodes are going to be synchronized again to the stronger and longer blockchain fork.

Lesson learned, leasing balance for forging is not a good feature for PoS, we recommend to never lease again. Maybe we take out that feature from future versions of Nas. The trusting power of PoS is that an attacker needs to put his own stake on risk, but with leased stake, an attacker has nothing to risk, nothing to lose. Besides, the lease feature doesn't encourage more nodes on the network, on the contrary, it encourage the concentration of forging nodes, with the same potential problem as Bitcoin mining concentrated in few big pools.

I just let forging the patapato lease.

My node is lost in own fork, no conections... restarting download of blockchain.
How limit the java cache? My server does not support the war of forks.

Would not divide the coins of the current fork equally among all the nodes to avoid war forks?

We keep trying to get the network in sync. Be patient. Now there are forks and we are very few forgers. But we was in worst situation before February, so keep waiting, Nas network is still weak but not dead, just ill ;-)

At the moment, the network is under an attack by lcharles123.

Any public node will get you up to block 277934.  After that block you'll see the blocks appear and disappear as the network fights with lcharles123.

There is a plan to fix things but it will take some time.

The actual client is still in the first post of this thread - 1.1.3N1.

You'll need to modify the config to add the public nodes.  There's a post about that a few pages back.

Can someone post a link to the current working version of NAS ? This one which synchronizes. Thank you

Thank you User1397367406, I'm glad that you didn't reset your main forging node. I agree that better you stop forging until other forger reach you. I was on that situation before, forging alone ahead of the rest, and my node resynchronized by itself when others reached my block height:

Edit: not correct post, sent very late with obfuscated mind, sorry.