tyz
Legendary
Offline
Activity: 3360
Merit: 1530
|
|
April 17, 2015, 02:26:28 PM |
|
Thanks for bringing NAS up again. I've just reactivated my client and everything seems to work fine. Great job! Keep it up!
|
|
|
|
|
|
|
|
"Bitcoin: the cutting edge of begging technology." -- Giraffe.BTC
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
User1397367406
Newbie
Offline
Activity: 51
Merit: 0
|
|
April 17, 2015, 10:19:52 PM |
|
Just a quick update: my second node successfully synced with the current network, from scratch, in one go, only "nas.wellKnownPeers" was set.
|
|
|
|
|
tyz
Legendary
Offline
Activity: 3360
Merit: 1530
|
|
April 18, 2015, 09:17:25 AM |
|
After everything is settling up again, what are the future plans for NAS? Any roadmap and are there any unique features planned?
|
|
|
|
xyzzyx
Sr. Member
Offline
Activity: 490
Merit: 250
I don't really come from outer space.
|
|
April 18, 2015, 03:29:18 PM |
|
Congratulations on reviving NAS!
|
"An awful lot of code is being written ... in languages that aren't very good by people who don't know what they're doing." -- Barbara Liskov
|
|
|
Kozan
|
|
April 20, 2015, 01:08:32 PM |
|
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.
|
|
|
|
tiker
|
|
April 21, 2015, 04:50:08 PM |
|
Kozan, we can't get you your NAS back if it is stuck between exchanges. Only the administrators of those exchanges can help.
The current plan for NAS is to get it patched with all of the security fixes NXT has applied. Since the updates would probably require a hard fork in the block chain, we'd need to schedule it ahead of time when it's ready and start a new thread on the forums here since we can't update the first post of this thread with new client information.
What happens after the security fixes is going to depend on how much time we have. We all have busy lives so I can't say what and when things will happen at this time.
|
|
|
|
patapato
Member
Offline
Activity: 93
Merit: 10
|
|
April 24, 2015, 03:03:18 AM Last edit: April 24, 2015, 01:23:40 PM by patapato |
|
Nas is Open Source now !!, we got the source code of NAS ClientI proudly announce that I was able to recreate the source code of the current Nas client. It is not exactly the same, it works slightly better because I deeply reviewed and tested all the changes from NXT version. And there is now also a core of 3 people with programming skills who will try to get Nas working and evolving: User1397367406, tiker and me, who worked together during the recent blockchain attack (a fork war), as well as we was the users who more contributed to revive the network, and we maintain independent trusted forger nodes. Everyone who join effort and skills will be welcomed. I pointed to the idea of recovering the sources long time ago. I repeated it after we got the blockchain synchronized, and several days later I wrote a brief plan, and I thought to do it myself: 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.
Now the point 2 is done. I named the new version 1.1.3.N2, as our current working version is 1.1.3(N1). As corrected things, for example, you can notice that your current version doesn't show properly the incoming transactions information when you click on an account link, but it is properly displayed on this new version. Ports are also corrected to be different of NXT ones, using 7871, 7872 and 7873 for peer, UI and API servers. I started a public repository in order that everybody can get the sources, compile them, review them, and of course, modify them (either by pull requests here or by his own fork). So NAS is Open Source, at last! You can view and edit a Wiki for Nas, as well. Repository: https://bitbucket.org/patapato/nasIf you are not a developer, and you just want to update your client, you can get it ready from the Download menu, or by clicking this direct link: Download: Nas Client 1.1.3.N2You have to unzip it replacing your current instalation, it will keep your current database directory and file, nas/nxt_db/nxt.h2.db, as well as your custom config file, nas/conf/nas.properties). Or better you can do the opposite, to unzip it in a different location and then copy those 2 files into it. That way you keep your original installation if you want to get it back (take care not to overwrite the new default config file, nas-default.properties). If you don't have a custom config file, I recommend that you create it with the next lines, filling the first 2 if you want to announce your internet address, the third if you want to be a trusted forger, and the last one if you want to log debug information. I let the old UI enabled by default (I like it), but you can disable or enable it here too. File nas/conf/nas.properties: nas.myAddress= nas.myPlatform=PC nas.myHallmark=
nas.wellKnownPeers=cb2.flipflop.mooo.com; funkyvps3.funkymonkey.org; patapato.ddns.net nas.knownBlacklistedPeers=
nas.enableUIServer=false nas.debug=false
Lastly, if you are curious about the detailed changes from NXT to NAS in this version, read the contents of the changelog file here. I'm running and forging with the new client for more than one day. You can see it on the public server of tiker. This is a screen capture of it: (EDIT) Donations are appreciated: NAS: NAS-H5AW-7J9F-7VCY-DJ8NB NXT: NXT-H5AW-7J9F-7VCY-DJ8NB BTC: 3Lgn75BAFS2yfmTzKmcD174ikXeYM5a2hC
|
|
|
|
lexicon
|
|
April 24, 2015, 03:14:51 AM |
|
Damn you guys are serious??
Well, good luck to you. It a very steep uphill climb, but I wish you the best!!
|
|
|
|
patapato
Member
Offline
Activity: 93
Merit: 10
|
|
April 24, 2015, 04:09:07 PM |
|
Nas Coin creator, profile name Nas_Coin, is not dead. He renewed his domain, nascoin.org, 19 days ago, on April 5, after expiry date March 24. Surely he is following progress of Nas here. Domain Name:NASCOIN.ORG Domain ID: D171574393-LROR Creation Date: 2014-03-24T12:07:51Z Updated Date: 2015-04-05T09:55:06Z Registry Expiry Date: 2016-03-24T12:07:51Z Sponsoring Registrar:GoDaddy.com, LLC (R91-LROR) Sponsoring Registrar IANA ID: 146 WHOIS Server: Referral URL: Domain Status: clientDeleteProhibited -- http://www.icann.org/epp#clientDeleteProhibited Domain Status: clientTransferProhibited -- http://www.icann.org/epp#clientTransferProhibited Domain Status: clientUpdateProhibited -- http://www.icann.org/epp#clientUpdateProhibited Domain Status: autoRenewPeriod -- http://www.icann.org/epp#autoRenewPeriod Registrant ID:CR164143577 Registrant Name:nas coin Registrant Organization:nascoin Registrant Street: 1 Registrant City:Texuas Registrant State/Province:Texas Registrant Postal Code:10000 Registrant Country:US Registrant Phone:+1.200200200000 Registrant Phone Ext: Registrant Fax: Registrant Fax Ext: Registrant Email:nascointeam@gmail.com
|
|
|
|
TwinWinNerD
Legendary
Offline
Activity: 1680
Merit: 1001
CEO Bitpanda.com
|
|
April 24, 2015, 10:31:57 PM |
|
Nas Coin creator, profile name Nas_Coin, is not dead. He renewed his domain, nascoin.org, 19 days ago, on April 5, after expiry date March 24. Surely he is following progress of Nas here. Domain Name:NASCOIN.ORG Domain ID: D171574393-LROR Creation Date: 2014-03-24T12:07:51Z Updated Date: 2015-04-05T09:55:06Z Registry Expiry Date: 2016-03-24T12:07:51Z Sponsoring Registrar:GoDaddy.com, LLC (R91-LROR) Sponsoring Registrar IANA ID: 146 WHOIS Server: Referral URL: Domain Status: clientDeleteProhibited -- http://www.icann.org/epp#clientDeleteProhibited Domain Status: clientTransferProhibited -- http://www.icann.org/epp#clientTransferProhibited Domain Status: clientUpdateProhibited -- http://www.icann.org/epp#clientUpdateProhibited Domain Status: autoRenewPeriod -- http://www.icann.org/epp#autoRenewPeriod Registrant ID:CR164143577 Registrant Name:nas coin Registrant Organization:nascoin Registrant Street: 1 Registrant City:Texuas Registrant State/Province:Texas Registrant Postal Code:10000 Registrant Country:US Registrant Phone:+1.200200200000 Registrant Phone Ext: Registrant Fax: Registrant Fax Ext: Registrant Email:nascointeam@gmail.com if he had money loaded on his account or a CC on it, this works automatically. Also I think if he chose the 2 year option at the start, it would look like that.
|
|
|
|
tyz
Legendary
Offline
Activity: 3360
Merit: 1530
|
|
April 25, 2015, 11:11:03 AM |
|
i want to use some of my remaining server capacity to run another Nxt-based coin node. Are there any community rewards for running a NAS node?
|
|
|
|
patapato
Member
Offline
Activity: 93
Merit: 10
|
|
April 25, 2015, 11:54:23 AM |
|
Nas Coin creator, profile name Nas_Coin, is not dead. He renewed his domain, nascoin.org, 19 days ago, on April 5, after expiry date March 24. Surely he is following progress of Nas here. Domain Name:NASCOIN.ORG Domain ID: D171574393-LROR Creation Date: 2014-03-24T12:07:51Z Updated Date: 2015-04-05T09:55:06Z Registry Expiry Date: 2016-03-24T12:07:51Z Sponsoring Registrar:GoDaddy.com, LLC (R91-LROR) Sponsoring Registrar IANA ID: 146 WHOIS Server: Referral URL: Domain Status: clientDeleteProhibited -- http://www.icann.org/epp#clientDeleteProhibited Domain Status: clientTransferProhibited -- http://www.icann.org/epp#clientTransferProhibited Domain Status: clientUpdateProhibited -- http://www.icann.org/epp#clientUpdateProhibited Domain Status: autoRenewPeriod -- http://www.icann.org/epp#autoRenewPeriod Registrant ID:CR164143577 Registrant Name:nas coin Registrant Organization:nascoin Registrant Street: 1 Registrant City:Texuas Registrant State/Province:Texas Registrant Postal Code:10000 Registrant Country:US Registrant Phone:+1.200200200000 Registrant Phone Ext: Registrant Fax: Registrant Fax Ext: Registrant Email:nascointeam@gmail.com if he had money loaded on his account or a CC on it, this works automatically. Also I think if he chose the 2 year option at the start, it would look like that. But, from expiration on March 24 to update on April 5 is almost 2 weeks, it is too much for an automatic renewal service, which should be done the same day of expiration or before (I think). But maybe you are right. i want to use some of my remaining server capacity to run another Nxt-based coin node. Are there any community rewards for running a NAS node?
We need forgers to make the network trusted. And forgers are people with a balance, whose big reward will be to get NAS on exchanges again. But, if I would want to pay you for a node, which would be the agreement?, what do you guarantee?, for how many time?, will you forge or just run a node?.
|
|
|
|
powerfull
|
|
April 26, 2015, 09:08:13 AM |
|
thank you man for all your hard work , if dev can come back to be with us ,that's better....
|
|
|
|
patapato
Member
Offline
Activity: 93
Merit: 10
|
|
April 28, 2015, 08:31:40 AM |
|
NAS version 1.1.6.N1As I told before, once we got the sources of Nas for one version, it is easy to update to further versions of Nxt. So I updated the Nas Client sources to the last of 1.1.* series in Nxt, which is 1.1.6. Client download: Nas Client 1.1.6.N1Sources repository: https://bitbucket.org/patapato/nasThis is the last version which can be updated without modifying the blockchain database structure. The next version of Nxt was 1.2.0e, which introduced the new feature Digital Goods Store, needing to update de DB. It would mean that everybody would have to update their clients before a predetermined block height. But it would be dangerous for the weak Nas network, with few nodes working now, and it would be a mess for the exchanges, which has not even synchronized the blockchain now. Version 1.1.6.N1 is not dangerous, you can test it and go back to 1.1.3.N? whenever you want, as the blockchain structure is exactly the same (anyway, it is always recommended to do backup of the blockchain file before running a different version). Thanks to all the people who gave encouragement!.
|
|
|
|
powerfull
|
|
April 28, 2015, 01:21:26 PM |
|
NAS version 1.1.6.N1As I told before, once we got the sources of Nas for one version, it is easy to update to further versions of Nxt. So I updated the Nas Client sources to the last of 1.1.* series in Nxt, which is 1.1.6. Client download: Nas Client 1.1.6.N1Sources repository: https://bitbucket.org/patapato/nasThis is the last version which can be updated without modifying the blockchain database structure. The next version of Nxt was 1.2.0e, which introduced the new feature Digital Goods Store, needing to update de DB. It would mean that everybody would have to update their clients before a predetermined block height. But it would be dangerous for the weak Nas network, with few nodes working now, and it would be a mess for the exchanges, which has not even synchronized the blockchain now. Version 1.1.6.N1 is not dangerous, you can test it and go back to 1.1.3.N? whenever you want, as the blockchain structure is exactly the same (anyway, it is always recommended to do backup of the blockchain file before running a different version). Thanks to all the people who gave encouragement!. thank you
|
|
|
|
tiker
|
|
April 29, 2015, 02:08:19 PM |
|
Why do you think that the network isn't strong enough to continue updating NAS? Anyone who's running a node is either not watching this thread and still forked from the attack and going no where, or are watching this thread and will know that a new version will be coming out and will update.
If Bter hasn't fixed their node, it might be easier (less work) for them to just download the new client and download the chain cleanly from the network again. Otherwise they'll be wiping the client, downloading the data, bringing their node offline when the new version comes out, possibly download the chain again, etc.
There are some major bugs that are fixed with newer versions of the NXT client. I don't think that stopping the NAS patching at 1.1.6 leaving the rest of the bugs in place due to the fear of nodes not updating is a wise decision.
|
|
|
|
patapato
Member
Offline
Activity: 93
Merit: 10
|
|
April 30, 2015, 02:17:58 PM |
|
Why do you think that the network isn't strong enough to continue updating NAS? Anyone who's running a node is either not watching this thread and still forked from the attack and going no where, or are watching this thread and will know that a new version will be coming out and will update.
If Bter hasn't fixed their node, it might be easier (less work) for them to just download the new client and download the chain cleanly from the network again. Otherwise they'll be wiping the client, downloading the data, bringing their node offline when the new version comes out, possibly download the chain again, etc.
There are some major bugs that are fixed with newer versions of the NXT client. I don't think that stopping the NAS patching at 1.1.6 leaving the rest of the bugs in place due to the fear of nodes not updating is a wise decision.
Well, maybe you are right. But the attack that we suffered was not because a bug, and we lost the only exchange that was available, Bter: "NAS deposit is disabled 因技术维护,虚拟币充值暂停,感谢您谅解和支持。" If we are going to update further, we need to decide and agree on a block height at which the new features will start working. After that, the current clients will not work. The WinNAS client will also not work with greater version updates (I know, nobody is using it, but it works ) I would like to read more opinions, in favor or against. Do you, people, want NAS to be a full updated clone of NXT?, would it be an incentive for new users and exchanges?, are there any other ideas for the evolution of Nas?.
|
|
|
|
Kozan
|
|
May 02, 2015, 07:00:48 AM |
|
What about dgex? It holds lot of NAS.
|
|
|
|
tiker
|
|
May 07, 2015, 01:28:41 PM |
|
BTER's node appears to have returned. Hopefully this is a good sign.
|
|
|
|
|