NAS :: Descendant of NXT 100% PoS|More Exchanges|WinNAS is ready! - page 9.

tiker

sr. member

Activity: 459

Merit: 250

Both nodes have started following a fork with a 1.5 day gap in the middle...

Code:

Height	Date	Amount	Fee	Nr TX	Generator	Payload	Base Target
277952	06/04/2015 21:21:49	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	1395 %
277951	06/04/2015 21:21:44	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	2791 %
277950	06/04/2015 21:20:56	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	3488 %
277949	06/04/2015 21:17:45	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	1744 %
277948	06/04/2015 21:17:18	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	3488 %
277947	06/04/2015 21:17:02	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	6976 %
277946	06/04/2015 21:14:45	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	3488 %
277945	06/04/2015 21:14:02	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	4867 %
277944	06/04/2015 21:11:15	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	2434 %
277943	06/04/2015 21:11:05	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	4867 %
277942	06/04/2015 21:10:25	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	7301 %
277941	06/04/2015 21:09:26	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	7425 %
277940	06/04/2015 21:07:58	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	5062 %
277939	06/04/2015 21:07:51	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	10124 %
277938	06/04/2015 21:07:29	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	20249 %
277937	06/04/2015 21:07:24	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	40498 %
277936	06/04/2015 21:07:21	0	0	0	NAS-VBK9-5ZXA-CJQ8-GEWVU	0 B	80996 %
277935	06/04/2015 21:03:50	0	0	0	NAS-3S5R-Q4ZL-QUEA-BWAP2	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 %
277932	05/04/2015 09:59:53	0	0	0	NAS-5HZF-TPQ5-GSHF-7GV33	0 B	39191 %
277931	05/04/2015 09:57:52	0	0	0	NAS-5HZF-TPQ5-GSHF-7GV33	0 B	19596 %

tiker

sr. member

Activity: 459

Merit: 250

My 99.227.... node is always forging with account NAS-87P5-WQH2-4E4A-A7G8W and a balance just over 5000 now. Normally it doesn't forge any blocks because of the other two forging accounts with a much higher balance. Should both of the big forging nodes go offline at the same time, my node should spit out a couple of blocks to keep things going until they return.

For whatever reason, both of my nodes didn't accept any blocks after 277934. My clients probably didn't see anyone forging so my local client attempted to push out block 277935 with the account above.

I've restarted both NAS clients and neither of them have changed at all. Both are stuck at 277934, both think that my local client is correct for block 277935.

A lease going to an unstable forging node shouldn't cause an issue like this. In fact, I don't even see forged blocks from NAS-VBK9-5ZXA-CJQ8-GEWVU so I don't even think it's forging.

I'll leave both nodes sitting for now and see if they correct things on their own.

lcharles123

legendary

Activity: 1697

Merit: 1074

patapato

member

Activity: 93

Merit: 10

Quote from: tiker on April 06, 2015, 09:22:32 AM

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.

patapato

member

Activity: 93

Merit: 10

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

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

User1397367406

newbie

Activity: 51

Merit: 0

Quote from: tiker on April 06, 2015, 09:22:32 AM

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

I think these messages "nxt.BlockchainProcessor$BlockNotAcceptedException: Generation signature verification failed" are because of my node:
* these IPs resolve to my internet provider
* My IP changes every day as i'm on dynamic IP
* The DNS name for my node is updated periodicaly
* the peer name, of my node, displayed on the client resolves to different IP. Don't know if the client stores also the IPs.
* As my IP changes, depending on the DNS update, blocks generated from my node should trigger these messages as the Signature is bound to the provided host name.

The network is still vulnerable to all kind if things, with only 2-3 nodes.
During the last couple of days i had some periodes where my node forged all the blocks.
Not sure if this was the exact network status or if it synced since then.
A couple of days back i had some similar strange things going on as suddenly the last block list updated itself.

My node seems to be relatively in sync with Patapatos:

Code:

279184	4/6/2015 21:03:14	0	0	0	NAS-5HZF-TPQ5-GSHF-7GV33	0 B	14119 %
279183	4/6/2015 20:59:10	0	0	0	NAS-5HZF-TPQ5-GSHF-7GV33	0 B	7060 %
279182	4/6/2015 20:57:52	0	0	0	NAS-H5AW-7J9F-7VCY-DJ8NB	0 B	5430 %
279181	4/6/2015 20:56:41	0	0	0	NAS-H5AW-7J9F-7VCY-DJ8NB	0 B	4589 %

tiker

sr. member

Activity: 459

Merit: 250

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

lovewiki

sr. member

Activity: 271

Merit: 250

Share Love

Quote from: patapato on April 04, 2015, 03:25:07 PM

Quote from: lcharles123 on April 04, 2015, 12:10:42 PM

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

Quote

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.

kennyP

hero member

Activity: 544

Merit: 500

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

patapato

member

Activity: 93

Merit: 10

Quote from: lcharles123 on April 04, 2015, 12:10:42 PM

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

Quote

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.

lcharles123

legendary

Activity: 1697

Merit: 1074

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

Quote

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

member

Activity: 93

Merit: 10

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, [email protected]   *
*  (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

powerfull

sr. member

Activity: 249

Merit: 250

Quote from: MadCow on March 30, 2015, 05:25:05 AM

Quote from: Kozan on March 30, 2015, 04:53:13 AM

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.

MadCow

hero member

Activity: 655

Merit: 500

Quote from: Kozan on March 30, 2015, 04:53:13 AM

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

Kozan

hero member

Activity: 520

Merit: 500

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?

pizza77

newbie

Activity: 51

Merit: 0

Quote from: powerfull on March 29, 2015, 09:07:16 AM

Quote from: patapato on March 27, 2015, 03:27:23 PM

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.

powerfull

sr. member

Activity: 249

Merit: 250

Quote from: patapato on March 27, 2015, 03:27:23 PM

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

patapato

member

Activity: 93

Merit: 10

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.

tiker

sr. member

Activity: 459

Merit: 250

Quote from: Kozan on March 26, 2015, 12:43:07 PM

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.

User1397367406

newbie

Activity: 51

Merit: 0

Quote from: tiker on 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.

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.

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