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

[User1397367406]

Congratulation on the successfull experience

What is a little bit odd is that you can't really see the leased amount.
The account information still says:

Code:

Account NAS-2FQK-TGQK-QZR6-BKDJZ Info
The account has a balance of 5 NAS. 

You can only see it in the transactions tab of the account informations.

[1715068581]

1715068581

[1715068581]

1715068581

[1715068581]

1715068581

[tiker]

Yay!  More forging!  

You'll need to use the API to see the leases against an account.

http://funkyvps3.funkymonkey.org:7873/nxt?requestType=getAccount&account=NAS-2FQK-TGQK-QZR6-BKDJZ

"effectiveBalanceNXT" will show the amount of NXT from the account and everything leased to the account once the lease is active.  You also should see the accounts leasing to this account here once the lease is active as well.

[tiker]

It only took them a week but my bter.com NAS withdrawal was completed.  It showed up on our little network and there's now a new node on the peer list. 

[MadCow]

So where is this headed ... can NAS be taken seriously without a dev? Good job in getting the chain back up and running!

[patapato]

It only took them a week but my bter.com NAS withdrawal was completed.  It showed up on our little network and there's now a new node on the peer list. 

Oooooh!!!, that is big news!! . 

It is a great first success on the rebirth of NAS that one of the big exchanges operates with NAS again. Thank you, BTER!. More stability for the NAS network to have Bter node synchronized and working.

Very good to have the opportunity of withdraw / deposit NAS, very good that people can enter to, or exit from NAS again. A coin without a market is not really a coin, NAS is a coin again .

[Kozan]

That's great, congratulations!
But no surprise that I don't see my NAS on bter because it was sent from poloniex. Can they resend using working blockchain, or maybe rollback and return NAS to balance?

[User1397367406]

It only took them a week but my bter.com NAS withdrawal was completed.  It showed up on our little network and there's now a new node on the peer list. 

That's great news 

My node was offline for the most part today, had to manualy re-boot the modem/rooter in order to connect.
Synced fine with the network.

[tiker]

That's great, congratulations!
But no surprise that I don't see my NAS on bter because it was sent from poloniex. Can they resend using working blockchain, or maybe rollback and return NAS to balance?

I don't see the transactions on our fork.

I don't know if Poloniex can re-broadcast transactions or not.  Depends on their code if it's customized, etc.

Even if they could, I don't see them spending the time and effort bringing up a node and doing an audit to see if the transaction went through on our fork or not if they don't plan on supporting NAS in the future.  Obviously the transactions did go out on a fork at the time since you have transaction IDs for them.  That fork is most likely gone now.

[patapato]

With Bter synchronized, Poloniex should also synchronize with us, no option for the opposite. I think that Poloniex will only set up a synchronized NAS node if they see new development.

So our next priority should be to reconstruct the source code for version 1.1.3(N1) from the sources of version 0.8.13, and to make it publicly available, in order to have a starting point for further Open Source development.

[powerfull]

With Bter synchronized, Poloniex should also synchronize with us, no option for the opposite. I think that Poloniex will only set up a synchronized NAS node if they see new development.

So our next priority should be to reconstruct the source code for version 1.1.3(N1) from the sources of version 0.8.13, and to make it publicly available, in order to have a starting point for further Open Source development.

yeah,dev should release the source code but not keep it cover under the his dirty pc .....

[pizza77]

With Bter synchronized, Poloniex should also synchronize with us, no option for the opposite. I think that Poloniex will only set up a synchronized NAS node if they see new development.

So our next priority should be to reconstruct the source code for version 1.1.3(N1) from the sources of version 0.8.13, and to make it publicly available, in order to have a starting point for further Open Source development.

yeah,dev should release the source code but not keep it cover under the his dirty pc .....

The old dev must still read the forums and have noticed the activity with NAS.

Please release the source code dev.

[Kozan]

The old dev disappeared long ago and he is reading nothing here.
I have an idea, what if PM everybody in this thread and tell that NAS is reviving?

[MadCow]

The old dev disappeared long ago and he is reading nothing here.
I have an idea, what if PM everybody in this thread and tell that NAS is reviving?

good idea

[powerfull]

The old dev disappeared long ago and he is reading nothing here.
I have an idea, what if PM everybody in this thread and tell that NAS is reviving?

good idea

noway ,the only way is get the source code then make a new start.

[patapato]

I'm working on the recovery of the source code. As a first step, I created a Git repository patapato/nas on Bitbucket whith a branch cloned from NXT reference repository (JeanLucPicard/nxt), and another branch for NAS from the comit previous to version 0.8.13 of NXT (that comit is the one more similar to NAS 0.8.13(N1)).

I started the NAS branch with the unmodified original source files (excluding nxt.jar and html/doc/*, which are generated files). I analyzed the changes in NAS sources from the NXT sources, and I wrote the first changelog file in order to understand the differences between NAS and NXT.

Next step is to debug this original sources, add the improved version of nas-default.properties (mainly to use ports non conflicting with the ones of NXT) and run.bat (to run with newer versions of Java), add merge it with the complete version 0.8.13 of NXT, obtaining a 0.8.13(N2) revision. Next target will be to merge with NXT 1.1.3, maybe with intermediate versions.

This is file nas-client-0.8.13(N1).changelog.txt:

Code:

*******************************************************************
*  Changes in NAS 0.8.13(N1) relative to NXT 0.8.13 (commit       *
*  previous to the labeled one, before "fixed to use a Map").     *
*                                                                 *
*  All the files (except this) are the ones in the original       *
*  distribution of the creator of NAS, Nas_Coin@bitcointalk.com   *
*  (see https://bitcointalk.org/index.php?topic=523187.0          *
*  and search: "0.8.13(N1) Full source")                          *
*******************************************************************

This file explains the differences between NAS and NXT. The important 
differences are the ones which implies a change in the blockchain, 
that is, a change in the database structure. 

- Genesis block ID and signature; initial distribution of coins:
	src/java/Genesis.java
	
- Total amount of coins is 10 billion NAS: 
	src/java/nxt/Constants.java (MAX_BALANCE=10000000000L)
	
- Timestamp origin set to 2014 march 25 12:00:00:
	src/java/nxt/Constants.java (EPOCH_BEGINNING):
	html/nrs/myTransaction.html (bug in month!, Date.UTC(2014, 2, 25, 12, 0, 0, 0))
	html/nrs/orphanedBlocks.html (same bug)
	html/nrs/recentBlocks.html (same bug!)
	html/nrs/unconfirmedTransactions.html (same bug!)
	
- 'BIGINT' instead of 'INT' in DB fields 'block.total_amount' and 'transaction.amount':
	src/java/DbVersion.java
	
- 'Long' instead of 'int' in variables for amounts, postfix 'L' in numeric values:
	src/java/nxt/Block.java
	src/java/nxt/BlockDb.java
	src/java/nxt/BlockImpl.java (buffer size 128 + 4 -> 132)
	src/java/nxt/BlockchainProcessorImpl.java (also: CHECKSUM_TRANSPARENT_FORGING=null)
	src/java/nxt/DbVersion.java
	src/java/nxt/Transaction.java
	src/java/nxt/TransactionDb.java
	src/java/nxt/TransactionImpl.java (also, TRANSACTION_BYTES_LENGTH)
	src/java/nxt/TransactionProcessor.java
	src/java/nxt/TransactionProcessorImpl.java
	src/java/nxt/TransactionType.java
	src/java/nxt/user/SendMoney.java
	src/java/nxt/http/SendMessage.java
	src/java/nxt/http/SendMoney.java
	src/java/nxt/http/TransferAsset.java
	src/java/nxt/http/CreateTransaction.java

- Peer server port 7871:
	conf/nxt-default.properties (nas.peerServerPort=7871)
	src/java/nxt/peer/Peers.java (*_PEER_PORT; also, commented "for" to get random known peers)


********************
Other minor changes: 

- Files removed: 
	.gitignore
	MIT-license.txt
	changelogs/*

- Files added: 
	readme.txt:
	html/tools/*/*
	
- Files modified: 
	run.bat: "NXT NRS" -> "NAS NRS"
	src/java/nxt/Constants.java:
		reset of blocks for alias system, transparent forging and arbitrary messages
	src/java/nxt/http/GetUnconfirmedTransactionsIds.java (bug: should be unmodified):
		added MISSING_ACCOUNT, MISSING_TIMESTAMP, UNKNOWN_ACCOUNT
	conf/nxt-default.properties:
		Rename properties from nxt.* to nas.* 
		nas.wellKnownPeers=
		nas.testnetPeers=bug.airdns.org
		nas.log=nas.log
		nas.debug=true
		
- Files modified as a result of renaming properties from nxt.* to nas.*:
	src/java/nxt/Nxt.java (also: VERSION and log messages)
	src/java/nxt/http/API.java
	src/java/nxt/http/APIServlet.java
	src/java/nxt/util/Logger.java
	src/java/nxt/user/Users.java
	src/java/nxt/user/UserServlet.java
	src/java/nxt/Db.java
	src/java/nxt/DebugTrace.java
	src/java/nxt/VerifyTrace.java

- Only spacing or position changes:
	src/java/nxt/Account.java
	src/java/nxt/Asset.java
	src/java/nxt/Attachment.java
	src/java/nxt/http/BroadcastTransaction.java
	src/java/nxt/http/GetAllOpenOrders.java
	src/java/nxt/http/JSONResponses.java

[lcharles123]

Why exactly you want to revive NAS?
To create this?

WinNAS v0.2: 11:59:59 PM EST Jul 15, 2014

BTC gateway
NXT gateway
BTC BlockDice
NXT BlockDice
BlockLottery

WinNAS v0.3
Advance Chatroom with more funcs(without NAS blockchain)
P2P Bet with reliable RSS and deadline(guarantee and arbitration with NAS blockchain)
Casino Foundation

NXT DGS,AT and more.

[patapato]

Why exactly you want to revive NAS?
To create this?

WinNAS v0.2: 11:59:59 PM EST Jul 15, 2014

BTC gateway
NXT gateway
BTC BlockDice
NXT BlockDice
BlockLottery

WinNAS v0.3
Advance Chatroom with more funcs(without NAS blockchain)
P2P Bet with reliable RSS and deadline(guarantee and arbitration with NAS blockchain)
Casino Foundation

NXT DGS,AT and more.

Not really. I just think of NAS as a clone of NXT with a different distribution. But it could serve as the basis for other developers to implement the original features of WinNAS, or new features not in NXT. By now it is also a techno challenge, the challenge of being able to revive a dead coin.

I think that NAS is the first coin revived after being more than one month without synchronized peers, that is, after being totally dead. It could be a precedent for other coins.

Also, I was very curious about the possibility of reverse engineering a coin with closed source development. This is not exactly the case, as we have an old version of sources, but it is interesting to understand that possibility. Now I think that it will be possible in other coins. The important thing when doing reverse engineering is to understand the blockchain database structure, and knowing the cryptographic algorithms used for hashes and PGP. With that, it is possible to recreate a new software for an existing blockchain without the original source code.

[kennyP]

@patapato, thank you for your efforts. As for why rebooting NAS is worth doing, ask yourself why a musician might write a 'pop song' after so many have already been written, or why make another action movie, or write another romance novel ... because people with talents like to express thrmselves. NAS already has a community and a distribution, and a 'brand'. This reboot might take NXT code in a new direction, and I think talented devs want a canvass to work on, and NXT already has Jean-Luc and others.

Keep up the good work patapato!!

[lovewiki]

Why exactly you want to revive NAS?
To create this?

WinNAS v0.2: 11:59:59 PM EST Jul 15, 2014

BTC gateway
NXT gateway
BTC BlockDice
NXT BlockDice
BlockLottery

WinNAS v0.3
Advance Chatroom with more funcs(without NAS blockchain)
P2P Bet with reliable RSS and deadline(guarantee and arbitration with NAS blockchain)
Casino Foundation

NXT DGS,AT and more.

Not really. I just think of NAS as a clone of NXT with a different distribution. But it could serve as the basis for other developers to implement the original features of WinNAS, or new features not in NXT. By now it is also a techno challenge, the challenge of being able to revive a dead coin.

I think that NAS is the first coin revived after being more than one month without synchronized peers, that is, after being totally dead. It could be a precedent for other coins.

Also, I was very curious about the possibility of reverse engineering a coin with closed source development. This is not exactly the case, as we have an old version of sources, but it is interesting to understand that possibility. Now I think that it will be possible in other coins. The important thing when doing reverse engineering is to understand the blockchain database structure, and knowing the cryptographic algorithms used for hashes and PGP. With that, it is possible to recreate a new software for an existing blockchain without the original source code.

That's what I want to see too. If you could reverse engineer this NAS coin and develop a new software to do it, it will build a totally way reviving other coins.

I have seen so many devs of altcoins just put the initial release to gihub, then release multiple binary updates after that but don't do any updates to gihub.

[tiker]

Both of my nodes seem to have gone off on a fork or something...
Recent blocks:

Code:

Height	Date	Amount	Fee	Nr TX	Generator	Payload	Base Target
277935	06/04/2015 10:18:08	0	0	0	NAS-87P5-WQH2-4E4A-A7G8W	0 B	40498 %
277934	05/04/2015 10:01:21	0	0	0	NAS-5HZF-TPQ5-GSHF-7GV33	0 B	20249 %
277933	05/04/2015 10:00:19	0	0	0	NAS-5HZF-TPQ5-GSHF-7GV33	0 B	19596 %

My local node keep trying to forge block 277935 since it hasn't seen a block since yesterday.  It seems that some of the other nodes are rejecting it.

My VPS is in agreement with my local node.

I'm restarting my nodes now to see if it helps.

Edit:
Patapato:
Are you running custom nodes?  It looks like you or someone else is generating blocks with invalid signatures:

Code:

[2015-04-06 10:26:04.151] DEBUG: Will pop block 5937549519284143825 at height 277935
[2015-04-06 10:26:04.153] DEBUG: Blacklisting 89.247.146.250 because of: nxt.BlockchainProcessor$BlockNotAcceptedException: Generation signature verification failed
[2015-04-06 10:27:06.217] DEBUG: Will pop block 5937549519284143825 at height 277935
[2015-04-06 10:27:06.219] DEBUG: Blacklisting 88.130.194.138 because of: nxt.BlockchainProcessor$BlockNotAcceptedException: Generation signature verification failed
[2015-04-06 10:27:51.778] DEBUG: Will pop block 5937549519284143825 at height 277935
[2015-04-06 10:27:51.780] DEBUG: Blacklisting 89.247.161.67 because of: nxt.BlockchainProcessor$BlockNotAcceptedException: Generation signature verification failed
[2015-04-06 10:28:17.989] DEBUG: Blacklisting 89.247.161.163 because of: nxt.BlockchainProcessor$BlockNotAcceptedException: Generation signature verification failed
[2015-04-06 10:29:01.112] DEBUG: Will pop block 5937549519284143825 at height 277935
[2015-04-06 10:29:01.114] DEBUG: Blacklisting 88.130.194.55 because of: nxt.BlockchainProcessor$BlockNotAcceptedException: Generation signature verification failed