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

[Kozan]

So we need to reach the agreement with exchanges, am I right? To convince them to use the same blockchain and verify the transactions of users. And if they don't find some of withdrawal transactions in a blockchain, then rollback and return NAS to a balance.
But what if there are deposits unconfirmed by new blockchain and then a person sold NAS?
... anyway, in case of Poloniex and dgex, there was no trades. Dgex closed NAS trading a long time ago. If they also did not perform deposits and withdrawals, so any blockchain will do. As for Polo, they can easily rollback at least some of the last withdrawals, after the announsement

[1715001013]

1715001013

[patapato]

So we need to reach the agreement with exchanges, am I right? To convince them to use the same blockchain and verify the transactions of users. And if they don't find some of withdrawal transactions in a blockchain, then rollback and return NAS to a balance.
But what if there were unconfirmed deposits and then a person sold NAS?
... anyway, in case of Poloniex and dgex, there was no trades. Dgex closed NAS trading a long time ago. If they also did not perform deposits and withdrawals, so any blockchain will do. As for Polo, they can easily rollback at least some of the last withdrawals, after the announsement

I agree. But I think that the network is not strong enough yet, we are few nodes, only two forgers, and we are not 24h/7d nodes (at least not me). It would be good that more people, not only exchanges run more nodes, either at home or at hosting.

Come on, people, join us to keep NAS alive!

[patapato]

My node is now synchronized. Sometimes I stop forging, then I see the account NAS-5HZF-TPQ5-GSHF-7GV33 forging, so we are on the same blockchain.

I see just other 5 peers now, 6 with me: 
funkyvps3.funkymonkey.org; 88.130.221.201; cb2.flipflop.mooo.com; 99.227.137.145; 222.92.62.194; patapato.ddns.net

The client say: "0/5 Up-to-date Peers": is it about version number, or about blockchain?, can we correct it?

Looking into the "nas_db/nas.trace.db" file (it is plain text, despite the extension) I have 2 recurring errors, this one:

Code:

03-17 02:05:10 jdbc[3]: exception
org.h2.jdbc.JdbcSQLException: 
Table "VERSION" not found; SQL statement:
SELECT next_update FROM version [42102-176]

and this one:

Code:

03-17 02:16:09 jdbc[3]: exception
org.h2.jdbc.JdbcSQLException: 
Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-176]

Are them normal?, is it due to NAS code changes from NXT code?. I didn't shutdown the server, nor the Java VM, is there something wrong on my node?

@lcharles123, I've just send you all my forged balance, 665 NAS (transaction 8730736024937643212). But, as you need an outgoing transaction *, I ask you to please donate 10 NAS to the account NAS-AXUZ-74SZ-9SB8-5SFUT, who lent me 10 NAS. That way we are testing the network.

*: "The recipient account is an unknown account, meaning it has never had an incoming or outgoing transaction. Please double check your recipient address before submitting."

[Kozan]

OK, can you tell once more how to start NAS? Correct links?

[tiker]

I see both of your nodes fighting to forge blocks which is good.
I see your transaction in block 259461. 

I picked up some NAS on bter.com and tried to withdrawal it but it's stuck.

The response from the support ticket is:

Dear Sir,
We will process the withdrawal as soon as we are possible

Thanks for your patience.

Hopefully this means that bter.com will come back. 

[tiker]

Code:

03-17 02:16:09 jdbc[3]: exception
org.h2.jdbc.JdbcSQLException: 
Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-176]

Are them normal?, is it due to NAS code changes from NXT code?. I didn't shutdown the server, nor the Java VM, is there something wrong on my node?

This error appears for me when I CTRL+C to stop NAS.  I'm guessing that you stopped NAS at that time to clear the block chain and download a new copy from us.

[patapato]

Yes, you are right!, that time was the last time that I stopped the server with <ctrl> + C.

I did the transaction without forging, in order to not forge my own transaction. I stopped and restarted forging several times for testing, but you are right again, now I am forging and I see some blocks forged by the account of User1397367406, it is healthy for the network.

Do you, or anybody with a node, try forging?, I can lease my balance to your account for few hours.

[Kozan]

I'd like to try, but give me a link to client

[tiker]

Do you, or anybody with a node, try forging?, I can lease my balance to your account for few hours.

I'm pretty sure that an account can not forge on a leased balance only.  The account needs to own at least 1 NAS before it can begin forging and make use of leased balances.

[tiker]

I'd like to try, but give me a link to client

Links are in the first post of this thread.  You'll want 1.1.3N1.

[patapato]

OK, can you tell once more how to start NAS? Correct links?

Quick guide to setup a NAS node.
Steps 1 and 5 is for a public node, you can avoid them if you just need the client. This guide is mostly for Windows, but the only point specific for Windows is point 6.

1.- The guide for NXT is quite the same, mainly the paragraph "Public Node from your home" (if you are thinking to do it from home). Take from that paragraph the way to open port 7871 (not 7874, which is for NXT) and use a web service to get a fixed domain name for your variable IP:
http://wiki.nxtcrypto.org/wiki/How-To:CreatePublicNode#Public_Node_from_your_home

2.- The link to download the software is this, taken from the first post of this thread, as tiker said:
https://www.dropbox.com/s/svdjyo4ozdzfdhp/nas_client.1.1.3%28N1%29.zip

3.- You should also have Java installed, you can download it from the original Oracle page:
https://www.java.com/en/download

4.- What I suggest is to change the configuration file before the first run of the node (otherwise, delete the database folder if you want to start from scratch), in order that the blockchain folder and files will be named with prefix "nas" instead of "nxt", and to avoid conflict of ports with NXT. You can take a corrected 'conf/nas-default.properties' file from my post here:
https://bitcointalk.org/index.php?topic=523187.msg10593432#msg10593432

5.- Then, you should have another file on the same folder called 'conf/nas.properties' where you write just the parameters that are not by default, mainly your node IP address and platform label (for a public node), and an initial list of trusted peers (also good for just a client node), like this:

Code:

nas.myAddress=your.internet.address
nas.myPlatform=PC
nas.wellKnownPeers=funkyvps3.funkymonkey.org;cb2.flipflop.mooo.com;patapato.ddns.net;99.227.137.145;222.92.62.194

6.- Lastly, if your Java version is greater than 7 (the default for NAS is 7), you should edit the script file 'run.bat' changing:
  IF EXIST java (
by
  for %%X in (java.exe) do (set IS_JAVA_IN_PATH=%%~$PATH:X)
  IF defined IS_JAVA_IN_PATH (

7.- When you are done, all that you have to do is running this file (in Windows, 'run.sh' in Linux). If you opened the port 7871 on your router and on system firewall, and if everything is working properly, you have now a NAS public node. You can access the client from a web browser by entering the URL (if you are not using my config file, port is 7876 instead, the same as NXT web client port):
http://localhost:7873

But you must wait for the blockchain to fully download from the NAS network. After that time you will have your client and node working. 

[User1397367406]

So we need to reach the agreement with exchanges, am I right? To convince them to use the same blockchain and verify the transactions of users. And if they don't find some of withdrawal transactions in a blockchain, then rollback and return NAS to a balance.
But what if there were unconfirmed deposits and then a person sold NAS?
... anyway, in case of Poloniex and dgex, there was no trades. Dgex closed NAS trading a long time ago. If they also did not perform deposits and withdrawals, so any blockchain will do. As for Polo, they can easily rollback at least some of the last withdrawals, after the announsement

I agree. But I think that the network is not strong enough yet, we are few nodes, only two forgers, and we are not 24h/7d nodes (at least not me). It would be good that more people, not only exchanges run more nodes, either at home or at hosting.

Come on, people, join us to keep NAS alive!

I agree with this too.
More forgers would be great.
I could kickstart/help someone with a NAS donation in order to start a node and also lease some of my balance.

I saw patapato forging today

@patapato
<< The client say: "0/5 Up-to-date Peers": is it about version number, or about blockchain?, can we correct it?
Can't remember having seen anyting other than  "0/x Up-to-date Peers": I think that this is a bug in the NAS client, may be it's related to the database error (i have this only once in the file)

Code:

09-25 22:21:47 jdbc[3]: exception
org.h2.jdbc.JdbcSQLException: Table "VERSION" not found; SQL statement:
SELECT next_update FROM version [42102-176]

[patapato]

I saw patapato forging today

@User1397367406, good to see you yesterday too   But I can not see you today when I stop forging. Do you see me today?, are you forging?, are we on different fork again ?

[tiker]

I saw patapato forging today

@User1397367406, good to see you yesterday too  But I can not see you today when I stop forging. Do you see me today?, are you forging?, are we on different fork again ?

I think you're forked again.  All of the blocks are forged by NAS-5HZF-TPQ5-GSHF-7GV33 on both of my nodes.

(If you ever want to check another node, you can use http://funkyvps3.funkymonkey.org:7873 and check the blocks... just don't use a password with funds... I use "hello" as my phrase when logging in here..)


If you (Patapato) have forked again, how is that possible?  The fork would begin if one of the forging nodes loses connectivity to the other forging node but continues to forge new blocks on its own.  (Example:  User1397367406 resets internet connection so the node continues to forge but on its own since it can't communicate with the other nodes.)  As long as the two forging nodes meet up again before 1440 blocks have passed they should be able to agree on a chain and go from there.  Now if the problem was User1397367406's node going offline and causing the problem then the rest of us would agree with Patapato's node but for some reason we all agree with User1397367406.  Is your node disconnected from the web but still forging for any long periods of time?

(I really wish bter.com would send me my NAS so that we have a more permanent forging node running from funkyvps3.)

[patapato]

I saw patapato forging today

@User1397367406, good to see you yesterday too  But I can not see you today when I stop forging. Do you see me today?, are you forging?, are we on different fork again ?

I think you're forked again.  All of the blocks are forged by NAS-5HZF-TPQ5-GSHF-7GV33 on both of my nodes.

(If you ever want to check another node, you can use http://funkyvps3.funkymonkey.org:7873 and check the blocks... just don't use a password with funds... I use "hello" as my phrase when logging in here..)


If you (Patapato) have forked again, how is that possible?  The fork would begin if one of the forging nodes loses connectivity to the other forging node but continues to forge new blocks on its own.  (Example:  User1397367406 resets internet connection so the node continues to forge but on its own since it can't communicate with the other nodes.)  As long as the two forging nodes meet up again before 1440 blocks have passed they should be able to agree on a chain and go from there.  Now if the problem was User1397367406's node going offline and causing the problem then the rest of us would agree with Patapato's node but for some reason we all agree with User1397367406.  Is your node disconnected from the web but still forging for any long periods of time?

(I really wish bter.com would send me my NAS so that we have a more permanent forging node running from funkyvps3.)

Thank you for your public NAS browser, tiker, and for explanation. I didn't stopped my node since my recent reset of blockchain, I just stopped forging sometimes to test if I can see the other forger. Yesterday I saw him all the day. I think that my connection was alive all the time. It is a dynamic IP, I am using noip.com to get a fixed domain, as suggested by NXT wiki The maximum time to reassign IP to my dynamic name is 5 minutes, or 5 blocks (well, one block is enough to fork , fast blocks of NAS are against network stability).

I have just one node, I think that User1397367406 has several nodes, probably all of them forging, isn't it?, so his forging is more stable against internet or machine problems. Maybe the rest of you has greater chance of finding him, as well. Or maybe just that he is before me on your nas.wellKnownPeers list.

You are right about that our nodes have to agree when reconnecting, but how can just 2 forgers agree?, if there is needed a majority for the agreement then we need at least 3 forgers to keep the network stable, am I right?

[User1397367406]

I saw patapato forging today

@User1397367406, good to see you yesterday too  But I can not see you today when I stop forging. Do you see me today?, are you forging?, are we on different fork again ?

I think you're forked again.  All of the blocks are forged by NAS-5HZF-TPQ5-GSHF-7GV33 on both of my nodes.

(If you ever want to check another node, you can use http://funkyvps3.funkymonkey.org:7873 and check the blocks... just don't use a password with funds... I use "hello" as my phrase when logging in here..)


If you (Patapato) have forked again, how is that possible?  The fork would begin if one of the forging nodes loses connectivity to the other forging node but continues to forge new blocks on its own.  (Example:  User1397367406 resets internet connection so the node continues to forge but on its own since it can't communicate with the other nodes.)  As long as the two forging nodes meet up again before 1440 blocks have passed they should be able to agree on a chain and go from there.  Now if the problem was User1397367406's node going offline and causing the problem then the rest of us would agree with Patapato's node but for some reason we all agree with User1397367406.  Is your node disconnected from the web but still forging for any long periods of time?

(I really wish bter.com would send me my NAS so that we have a more permanent forging node running from funkyvps3.)

Thank you for your public NAS browser, tiker, and for explanation. I didn't stopped my node since my recent reset of blockchain, I just stopped forging sometimes to test if I can see the other forger. Yesterday I saw him all the day. I think that my connection was alive all the time. It is a dynamic IP, I am using noip.com to get a fixed domain, as suggested by NXT wiki The maximum time to reassign IP to my dynamic name is 5 minutes, or 5 blocks (well, one block is enough to fork , fast blocks of NAS are against network stability).

I have just one node, I think that User1397367406 has several nodes, probably all of them forging, isn't it?, so his forging is more stable against internet or machine problems. Maybe the rest of you has greater chance of finding him, as well. Or maybe just that he is before me on your nas.wellKnownPeers list.

You are right about that our nodes have to agree when reconnecting, but how can just 2 forgers agree?, if there is needed a majority for the agreement then we need at least 3 forgers to keep the network stable, am I right?

@Patapato: I'm still forging. Have to verify if i did see you today, unfortunately in the browser the forged blocks displayed are only from the last 2H.
I only run one node full time and forging also with the same one.(only one account)
I have a second client on my PC running from time to time.
Did you set a hallmark for your node Patapato?
I have mine set, this might explain why my node is prefered or choosen first when it came to select the better/best blockchain.
I'm not that much into nxt/nas and the current state of the nas client/server to tell how or why this strange things happen.
It's diffucult with only 2 forging nodes to keep a stable network.

Thank you for your public NAS browser, tiker. It's good to be able to check against another wallet.
Maybe i should get a public node up and running.

[patapato]

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?

[kennyP]

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

[tiker]

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.

[tiker]

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.