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

[patapato]

Thank you, User1397367406. I didn't set a hallmark, I really don't know what exactly it is, but I will read tomorrow how to do it. Meanwhile I prefer to stay without forging, I will start and stop forging occasionally to test it. I can lease my balance to tiker for few days, do you want it, tiker?

I'll need a small number of NAS coins for my account to have a balance and I'll need to send a couple back to put a public key on the block chain.  Once that has 1440 confirmations I'll be able to start forging.

So, if you can send me 3 NAS to the account "NAS-2FQK-TGQK-QZR6-BKDJZ", I'll send 1 back (+1 lost for transaction fee).  That should leave me with 1 NAS coin on the account, a public key on the block chain and able to forge 1440 blocks later.

I'll forge from funkyvps3.

Done, I sent you 111NAS, tx 1252390869854816059, I can see it on your web client. I forged it because I don't see the other forger now. Please, send 10 NAS to NAS-AXUZ-74SZ-9SB8-5SFUT, so that you will keep 100 NAS for you, and your account will get a strong public key. Tomorrow I will lease my balance to you for a short time to test if everything works, then I can lease for more time.

[patapato]

This NAS resurrection is starting to look almost possible, quite impressed. Is there any chance of more dev work, or is your plan so far just to keep the chain going? If you get a new dev then NAS could do OK. Distribution would be quite solid after so long in the crypto wilderness.

Watching with interest

For now, we're just playing around trying to get NAS functional again.  I don't think any of us are serious developers that can take over NAS development.  I'm not even sure if the source for NAS 1.1.3.N1 was made available.

If someone is willing to give it a try though, feel free.

We can get NAS updated to the last version of NXT, I think. The source of NAS 1.1.3(N1) is not available, but we have the source for 0.8.13(N1), it is on post 1 of this thread (I already posted about it 6 months ago). I greatly suspect that it is enough to get the client and server (NRS) updated, as the NAS transactions and blockchain structure should already be developed on this version. We can not get the WinNAS client, that is the part of software which is closed and lost. So, we will not recover the Dice, Lottery and Chat features, but we can get a clone of NXT with coins already distributed, with open source code, and maybe with 1 to 4 exchanges already working.

The plan could be:

• 1. Compare sources of NAS 0.8.13(N1) with sources of NXT 0.8.13, to get which source files are different, and in which manner.
• 2. Implement the same changes to version 1.1.3 of NXT, compile, and test if it works the same as our current version of NAS. I'm afraid that here we will need to review malfunctioning things, like the test network, used ports, up-to-date peers, etc, the same way that I reviewed the config file.
• 3. If we get the source for 1.1.3 running properly, we can try the same changes for the last version of NXT.

If we get success, we will have a starting point for other developers to implement new ideas, maybe the original WinNAS ideas, or we can just try to keep track of changes in NXT and get a continuously updated clone of NXT. I support the later option, people use to say that a pure clone has no interest, but I don't think so.

[tiker]

Done, I sent you 111NAS, tx 1252390869854816059, I can see it on your web client. I forged it because I don't see the other forger now. Please, send 10 NAS to NAS-AXUZ-74SZ-9SB8-5SFUT, so that you will keep 100 NAS for you, and your account will get a strong public key. Tomorrow I will lease my balance to you for a short time to test if everything works, then I can lease for more time.

Thanks.  I see the transaction but I'm not able to send them to the account as asked.  The client is returning an error "Could not verify transaction bytes (server side).".

Keep forging if you can.  I'm hoping it just needs a set number of confirmations before sending but if not I'll poke around a bit to see if I can figure out why.

[tiker]

Done, I sent you 111NAS, tx 1252390869854816059, I can see it on your web client. I forged it because I don't see the other forger now. Please, send 10 NAS to NAS-AXUZ-74SZ-9SB8-5SFUT, so that you will keep 100 NAS for you, and your account will get a strong public key. Tomorrow I will lease my balance to you for a short time to test if everything works, then I can lease for more time.

Thanks.  I see the transaction but I'm not able to send them to the account as asked.  The client is returning an error "Could not verify transaction bytes (server side).".

Keep forging if you can.  I'm hoping it just needs a set number of confirmations before sending but if not I'll poke around a bit to see if I can figure out why.

Odd...  The error above appears when I attempt to send NAS from funkyvps3.  When sending from my local node, it worked.

Transaction ID   Date   Type   Amount   Fee   Account   Confirmations
10231787055063096754   19/03/2015 12:06:58   Ordinary payment      10   1   NAS-AXUZ-74SZ-9SB8-5SFUT   /
1252390869854816059   19/03/2015 06:07:50   Ordinary payment      111   1   NAS-H5AW-7J9F-7VCY-DJ8NB   221

10 NAS has been sent to NAS-AXUZ-74SZ-9SB8-5SFUT as requested.


With the 100 left, I'm thinking of sending 90 to another account for forging.  My local node can forge with the 90 NAS, while funkyvps3 can forge with the last 10 + leased balance.  This will add another forger to the network.

Since these are your NAS coins, are you ok with this?

[patapato]

10 NAS has been sent to NAS-AXUZ-74SZ-9SB8-5SFUT as requested.

Thanks.

With the 100 left, I'm thinking of sending 90 to another account for forging.  My local node can forge with the 90 NAS, while funkyvps3 can forge with the last 10 + leased balance.  This will add another forger to the network.

Since these are your NAS coins, are you ok with this?

You are wrong this time , these are not my NAS coins anymore, these are yours Anyway, I like your idea, it is good for the network.

I would donate 20NAS to few other stable nodes who creates a hallmark and decide to forge, until there is enough stable forgers. By the way, I already set up a hallmark on my node, thank you for suggesting it, @User1397367406. If there were enough small forgers, I don't want to compete against them, I could stop forging, meanwhile I keep forging to keep the blockchain alive (reward without transactions is 0  ).

[User1397367406]

Hey!, I am synchronized again

I didn't stop my node, just I stopped to forge and it synchronized after 5.5 hours, here is the block history of that time (GMT+1):
...
260632 18/03/2015 23:00:54 0 0 0 NAS-5HZF-TPQ5-GSHF-7GV33 0 B 8708 %
260631 18/03/2015 22:59:17 0 0 0 NAS-5HZF-TPQ5-GSHF-7GV33 0 B 5386 %
260630 18/03/2015 16:29:59 0 0 0 NAS-H5AW-7J9F-7VCY-DJ8NB 0 B 2693 %
260629 18/03/2015 16:28:10 0 0 0 NAS-H5AW-7J9F-7VCY-DJ8NB 0 B 1482 %
...

Thank you, User1397367406. I didn't set a hallmark, I really don't know what exactly it is, but I will read tomorrow how to do it. Meanwhile I prefer to stay without forging, I will start and stop forging occasionally to test it. I can lease my balance to tiker for few days, do you want it, tiker?

The network is still not very stable.
I had a WTF moment as the sync occured.

I saw this sync happening and first i didn't realised what's going on, i was in the middle of changing the client html code in order to display more than 100 forged blocks.
The results i got seem to make no real sens as at that time i was sure that my node was forging all the blocks.
After 30+ min i stoped working on the code thinking i was making mistakes, i.e, i didn't get the result i was looking for.
Than i went back to my forging client and saw a totaly different block history then before.

[User1397367406]

This NAS resurrection is starting to look almost possible, quite impressed. Is there any chance of more dev work, or is your plan so far just to keep the chain going? If you get a new dev then NAS could do OK. Distribution would be quite solid after so long in the crypto wilderness.

Watching with interest

For now, we're just playing around trying to get NAS functional again.  I don't think any of us are serious developers that can take over NAS development.  I'm not even sure if the source for NAS 1.1.3.N1 was made available.

If someone is willing to give it a try though, feel free.

We can get NAS updated to the last version of NXT, I think. The source of NAS 1.1.3(N1) is not available, but we have the source for 0.8.13(N1), it is on post 1 of this thread (I already posted about it 6 months ago). I greatly suspect that it is enough to get the client and server (NRS) updated, as the NAS transactions and blockchain structure should already be developed on this version. We can not get the WinNAS client, that is the part of software which is closed and lost. So, we will not recover the Dice, Lottery and Chat features, but we can get a clone of NXT with coins already distributed, with open source code, and maybe with 1 to 4 exchanges already working.

The plan could be:

• 1. Compare sources of NAS 0.8.13(N1) with sources of NXT 0.8.13, to get which source files are different, and in which manner.
• 2. Implement the same changes to version 1.1.3 of NXT, compile, and test if it works the same as our current version of NAS. I'm afraid that here we will need to review malfunctioning things, like the test network, used ports, up-to-date peers, etc, the same way that I reviewed the config file.
• 3. If we get the source for 1.1.3 running properly, we can try the same changes for the last version of NXT.

If we get success, we will have a starting point for other developers to implement new ideas, maybe the original WinNAS ideas, or we can just try to keep track of changes in NXT and get a continuously updated clone of NXT. I support the later option, people use to say that a pure clone has no interest, but I don't think so.

I found this link to a nascoinproject repository at bitbucket some time ago:
https://bitbucket.org/nascointeam/nascoinproject/
Not sure if it's the official repository for the NAS 0.8.13(N1) client.
It has an iteresting history of commits and could show the differences/changes applied to the NXT 0.8.13.

[patapato]

I found this link to a nascoinproject repository at bitbucket some time ago:
https://bitbucket.org/nascointeam/nascoinproject/
Not sure if it's the official repository for the NAS 0.8.13(N1) client.
It has an iteresting history of commits and could show the differences/changes applied to the NXT 0.8.13.

I knew it, I joined as a watcher in Bitbucket. But it seems to be just the source of NXT, without changes, there is nothing about NAS except the file "List4GenesisBlock" with the initial distribution of coins.

[patapato]

I found this link to a nascoinproject repository at bitbucket some time ago:
https://bitbucket.org/nascointeam/nascoinproject/
Not sure if it's the official repository for the NAS 0.8.13(N1) client.
It has an iteresting history of commits and could show the differences/changes applied to the NXT 0.8.13.

I knew it, I joined as a watcher in Bitbucket. But it seems to be just the source of NXT, without changes, there is nothing about NAS except the file "List4GenesisBlock" with the initial distribution of coins.

In fact, it is version 0.8.11, not even 0.8.13. Here is the comparison between the original NXT source and the one on "nascointeam/nascoinproject" for version label 0.8.11, which is the last one available on the later. We can see that the only difference is the list of initial shareholders, "List4GenesisBlock":

[User1397367406]

I found this link to a nascoinproject repository at bitbucket some time ago:
https://bitbucket.org/nascointeam/nascoinproject/
Not sure if it's the official repository for the NAS 0.8.13(N1) client.
It has an iteresting history of commits and could show the differences/changes applied to the NXT 0.8.13.

I knew it, I joined as a watcher in Bitbucket. But it seems to be just the source of NXT, without changes, there is nothing about NAS except the file "List4GenesisBlock" with the initial distribution of coins.

In fact, it is version 0.8.11, not even 0.8.13. Here is the comparison between the original NXT source and the one on "nascointeam/nascoinproject" for version label 0.8.11, which is the last one available on the later. We can see that the only difference is the list of initial shareholders, "List4GenesisBlock":

https://i.imgur.com/b67xTTGl.png

But if you look under "commits" you might get the impression that it's 0.8.13.

Code:

Author 	Commit 	Message 	Labels 	Comments 	Approvals 	Date
Coin Nas	f87464e	M	Merged JeanLucPicard/nxt into master	2014-04-11
Jean-Luc Picard	401e1d8 M	Finish 0.8.13	2014-04-01
Jean-Luc Picard	ffa873b		fixed to use a Map	2014-04-01
Jean-Luc Picard	17d6af9		0.8.13 changelog	2014-04-01
Jean-Luc Picard	7313903		prevent duplicate hash transactions in the unconfirmed transactions	2014-04-01
...

[tiker]

I've been poking around in the 0.8.13 source code that's posted as a .zip file in the original post.  The files here are dated as late as Apr 19th so it appears the zip file contains the latest version available (so far).

[tiker]

You are wrong this time , these are not my NAS coins anymore, these are yours Anyway, I like your idea, it is good for the network.

And thank you sir.

If I ever forge 100 transactions I'll send some back to you. 

[patapato]

@tiker: I leased my balance to you for 1440 blocks, transaction 7174087968811187313 at 21/03/2015 11:38:32 UTC.

[patapato]

But if you look under "commits" you might get the impression that it's 0.8.13.

Code:

Author 	Commit 	Message 	Labels 	Comments 	Approvals 	Date
Coin Nas	f87464e	M	Merged JeanLucPicard/nxt into master	2014-04-11
Jean-Luc Picard	401e1d8 M	Finish 0.8.13	2014-04-01
Jean-Luc Picard	ffa873b		fixed to use a Map	2014-04-01
Jean-Luc Picard	17d6af9		0.8.13 changelog	2014-04-01
Jean-Luc Picard	7313903		prevent duplicate hash transactions in the unconfirmed transactions	2014-04-01
...

I really don't understand why. But there is not a greater version label than 0.8.11 in this repository:



and the files on it are exactly the same as version 0.8.11 of "JeanLucPicard / nxt", except for "List4GenesisBlock" file added. So, it doesn't help, it is not really NAS source code :-( , it means that they never did commit NAS specific code.

Version 0.8.13 was the first version of NXT that was packaged for download, as far as I can see, and it is the last one of 0.8.x:
https://nxtforum.org/nrs-releases/60/
https://bitcointalk.org/index.php?topic=345619.0
Is it casual that NAS first and only source code is also this version?

Comparing date of files between nas-0.8.13(N1) and nxt-0.8.13, it looks that the following 12 files has NAS specific code:

Constants.java
BlockchainProcessorImpl.java
TransactionProcessorImpl.java
DebugTrace.java
Account.java
DbVersion.java
Nxt.java
Asset.java
BlockDb.java
TransactionType.java
Attachment.java
VeryfyTrace.java

[patapato]

@tiker: I leased my balance to you for 1440 blocks, transaction 7174087968811187313 at 21/03/2015 11:38:32 UTC.

It seems that forging with leased balance is not working properly. When I stop forging, my account stops finding blocks, when I resume forging, my account finds blocks again. So, @tiker is not forging with my account, despite I leased my balance to him.

Leased forging is a feature that was not in NXT 0.8.13, it was for first time in 1.0.0.changelog.txt:

Added Account lease events, Listeners can be registered for LEASE_SCHEDULED,
LEASE_STARTED and LEASE_ENDED. This is of interest to Java API users only.

It would confirm that NAS 1.1.3(N1) is not a full update to NXT 1.1.3 features, and it is not well debugged. Anyway, we would have to start with 0.8.13 source code, the only available one, and try to update it to 1.1.3 again.

[tiker]

Balance leasing transactions require 1440 confirmations before they come into effect.  Once 1440 blocks have passed since you issued the balance lease transaction, your client will stop forging and the my account's effective balance will include your balance for forging.

[patapato]

Balance leasing transactions require 1440 confirmations before they come into effect.  Once 1440 blocks have passed since you issued the balance lease transaction, your client will stop forging and the my account's effective balance will include your balance for forging.

Ok, sorry, I waited 1440 blocks from my sending of coins to your account and your first output transaction, I didn't realize about other 1440 blocks to confirm the leasing tx. I wish it works, we will wait to block 264385.

[tiker]

So my node is forging now with your balance leased to it.

I noticed that my two nodes don't agree on a few blocks.

For blocks 264459 to 264466:
funkyvps3 shows account NAS-2FQK-TGQK-QZR6-BKDJZ forged them.
my other node shows account NAS-5HZF-TPQ5-GSHF-7GV33 forged them.

The blocks before the 7 above match on both nodes and all of the blocks afterwards match (block numbers and forger).

Waiting to see what happens with these blocks between these two nodes and to see if one of them will correct themselves automatically.

[patapato]

So my node is forging now with your balance leased to it.

I noticed that my two nodes don't agree on a few blocks.

For blocks 264459 to 264466:
funkyvps3 shows account NAS-2FQK-TGQK-QZR6-BKDJZ forged them.
my other node shows account NAS-5HZF-TPQ5-GSHF-7GV33 forged them.

The blocks before the 7 above match on both nodes and all of the blocks afterwards match (block numbers and forger).

Waiting to see what happens with these blocks between these two nodes and to see if one of them will correct themselves automatically.

Congratulations. My node agrees with your public node funkyvps3 on those blocks.

[patapato]

After the good experience with leasing, I lease my balance to @tiker again for 5760 blocks (should be about 4 days). I did it on block 266249, so it will begin on block 267689, and will finish on block 273449 (if I am right).