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

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.

Thanks.

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  ).

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?

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.

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.

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.

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.

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.

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

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?

@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.

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?

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.)

@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 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)

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://bitcointalksearch.org/topic/m.10593432

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:

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. 

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

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.

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

Yes, you are right!, that time was the last time that I stopped the server with + 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.