 Show Posts
|
|
Pages: « 1 [2] 3 4 5 »
|
My nodes appear to be rejecting the block 277935 that other nodes are trying to pass to it. It gives a bad signature message and bans that IP for 15 minutes or so. That would make me think that my block 277934 is different than the same block number everyone else has.
Your block 277934 is the same as ours. It is block 17565891496255612524, its timestamp is 32493681, and its signature is a31e0ae7a1e94c3175271157a43b6cd64eaff47825278bad28fdad6699f46f0147c3b2eea29fb7a a8a0b90cdaf224ddf9e7afbf7d2de3a038b5ef25c87929fef My node is stuck at height 279190, the one just after my transaction at 13:39:49 (GMT+2), similarly to your 277935. It advances some blocks, then it goes back, sometimes to the previous valid one 279189. I can not see other forgers when I am not forging. I restarted my node 2 hours ago, but it is the same (less peers now). I told you to not forge, but with so few forgers I'm wrong. It is probably better now that all of us try to forge, and the NAS distributed system will decide. In fact, I created other accounts in order to distribute my forging power leasing smaller quantities to others. I can not do it until the network stabilize to one winner fork. @User1397367406, I don't see you forging neither on my client nor on tiker's public client, are you not forging now?, or are you in yet another fork? |
|
|
|
I created a new account, and I sent it 1000 NAS (transaction 18419636354574564653). I was not forging in that instant. But I didn't get blocks, so I started forging again. In my blockchain it is at height 279190 forged by me, but in tiker's public node ( http://funkyvps3.funkymonkey.org:7873/) it is at height 277935 forged by NAS-VBK9-5ZXA-CJQ8-GEWVU (with a balance of 64 NAS). I am observing in real time how both forks are fighting, as I see the block height going back and forth in both nodes. Interesting. |
|
|
|
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.
@tiker, don't try to forge until your node is synchronized, as you will have rejections, or worst, you will be strengthening your own separated fork. |
|
|
|
@kennyP and @lovewiki, thank you!!  , I agree. @tiker, and @User1397367406 (and everybody), I leased my balance to account NAS-VBK9-5ZXA-CJQ8-GEWVU for 1440 blocks (he asked me for it by PM). The lease transaction was 9204069884770967256 at 02/04/2015 22:05:59 (GMT+1), and the lease started from block 277021 until block 278461. The blocks of problem for tiker are in the middle of this rank. Maybe it was not a good idea to lease my balance to a non stable node  , User1397367406 is right, we are very few forgers, any loose of stability is more critical than in a strong network. Anyway, the forked block 277935 in tiker's node was not forged by that address. But I was not forging, maybe User1397367406 didn't forged on that time too, or had "Generation signature verification failed" problems, so the network was without stable forgers for a while, favoring forks. Anyway, our main blockchain is still alive and healthy, I am synchronized with NAS-5HZF-TPQ5-GSHF-7GV33 (User1397367406 forging account), as we both are forging blocks now on the same blockchain. I have a list of 25 up-to-date peers on my client, 20 of them connected. But the list of nodes is redundant, many nodes are repeated (I don't understand why). I have 6 non-repeated peers: cb2.flipflop.mooo.com, 88.193.20.204, 106.187.102.227, funkyvps3.funkymonkey.org, 99.227.137.145, 222.92.62.194. There are only 3 peers in tiker`s public node, one of them is me: 99.227.137.145 patapato.ddns.net 106.187.102.227 So, @tiker, the last block on your chain, 277935 forged by NAS-87P5-WQH2-4E4A-A7G8W, does not exist on our blockchain. The previous one is correct. I think (and hope) that your nodes should synchronize by themselves. |
|
|
|
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. |
|
|
|
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: *******************************************************************
* 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
|
|
|
|
We got to resurrect NAS coin. The blockchain was dead for more than 1.5 months, there was no synchronized peers on the network. But some of the holders got to synchronize the blockchain again and make some transactions, as well as to lease balance to forge with another account. Two days ago, Bter.com synchronized his NAS node, and now it is possible to make withdrawal / deposit, as well as trading: If you like to contribute to the network with a node, here is a quick guide for it: https://bitcointalk.org/index.php?topic=523187.msg10804867#msg10804867About development, there is an old version of the source code available. We hope to be able to update it, as it is mostly a clone of NXT. About the reason to get a dead coin working again, it is just about freedom. The main reason to create Bitcoin was to get more freedom. It is the same for every other crypto-coin: more coins, more freedom. You are free to not accept it  .
|
|
|
|
|
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.
|
|
|
|
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  . |
|
|
|
|
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).
|
|
|
|
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.
Congratulations. My node agrees with your public node funkyvps3 on those blocks. |
|
|
|
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. |
|
|
|
@tiker: I leased my balance to you for 1440 blocks, transaction 7174087968811187313 at 21/03/2015 11:38:32 UTC.
It seems that forging with leased balance is not working properly. When I stop forging, my account stops finding blocks, when I resume forging, my account finds blocks again. So, @tiker is not forging with my account, despite I leased my balance to him. Leased forging is a feature that was not in NXT 0.8.13, it was for first time in 1.0.0.changelog.txt: 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. It would confirm that NAS 1.1.3(N1) is not a full update to NXT 1.1.3 features, and it is not well debugged. Anyway, we would have to start with 0.8.13 source code, the only available one, and try to update it to 1.1.3 again. |
|
|
|
But if you look under "commits" you might get the impression that it's 0.8.13. 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
...
I really don't understand why. But there is not a greater version label than 0.8.11 in this repository:  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://bitcointalk.org/index.php?topic=345619.0Is 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
|
|
|
|
|
@tiker: I leased my balance to you for 1440 blocks, transaction 7174087968811187313 at 21/03/2015 11:38:32 UTC.
|
|
|
|
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. 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":  |
|
|
|
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. |
|
|
|
10 NAS has been sent to NAS-AXUZ-74SZ-9SB8-5SFUT as requested.
Thanks. 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?
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  ). |
|
|
|
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. 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. |
|
|
|
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. 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. |
|
|
|
|
