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?
Topic: NAS :: Descendant of NXT 100% PoS|More Exchanges|WinNAS is ready! - page 10. (Read 143779 times)
March 26, 2015, 12:43:07 PM
March 26, 2015, 04:23:33 AM
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
. 
March 26, 2015, 12:10:41 AM
So where is this headed ... can NAS be taken seriously without a dev? Good job in getting the chain back up and running!
March 25, 2015, 09:40:23 PM
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.
March 24, 2015, 09:10:12 PM
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.
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.
March 24, 2015, 05:07:40 PM
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:
You can only see it in the transactions tab of the account informations.
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.
March 24, 2015, 03:13:24 PM
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).
March 22, 2015, 10:17:59 PM
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.
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.
March 22, 2015, 08:36:42 PM
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.
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.
March 21, 2015, 01:25:15 PM
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.
March 21, 2015, 01:00:33 PM
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.
March 21, 2015, 12:30:16 PM
@tiker: I leased my balance to you for 1440 blocks, transaction 7174087968811187313 at 21/03/2015 11:38:32 UTC.
Leased forging is a feature that was not in NXT 0.8.13, it was for first time in 1.0.0.changelog.txt:
Quote
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.
LEASE_STARTED and LEASE_ENDED. This is of interest to Java API users only.
March 21, 2015, 09:21:05 AM
But if you look under "commits" you might get the impression that it's 0.8.13.
I really don't understand why. But there is not a greater version label than 0.8.11 in this repository: 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
...
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://bitcointalksearch.org/topic/nxt-descendant-of-bitcoin-updated-information-345619
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
March 21, 2015, 08:28:01 AM
@tiker: I leased my balance to you for 1440 blocks, transaction 7174087968811187313 at 21/03/2015 11:38:32 UTC.
March 20, 2015, 04:31:51 PM
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.
March 20, 2015, 04:29:18 PM
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).
March 20, 2015, 03:59:51 PM
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. 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.
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":
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
...
March 20, 2015, 12:34:43 PM
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. 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.
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":
March 20, 2015, 08:11:48 AM
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. 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.
March 19, 2015, 05:34:05 PM
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
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.
Jump to: