Soooo... , I suggest you, @tiker, to blacklist the node of lcharles, as he is "ilegally" forging with my balance and confusing the network. And I ask you, @lcharles, to stop forging with my balance, as my leasing already finished on the longer fork of the blockchain. Otherwise I have to think that you asked me by PM a balance to forge with in order to just attacking the NAS network.
Chances are, lcharles' node is stuck at a block near mine. That's the only reason why lcharles' node would continue trying to forge blocks with your lease. That node hasn't reached a number where the lease ended. That could be why my node is trying to accept blocks forged by lcharles' node and why signature errors are appearing for blocks you forge with your account - my nodes think that you should not be forging with your balance yet and thinks it's still with lcharles. I still don't understand why leasing your balance to someone else with an unstable node could cause this issue. In theory, it shouldn't. |
|
|
|
I think the bter.com node is stuck with my nodes. The peer list from my public node: Address Weight Downloaded Uploaded Application Platform
cb2.flipflop.mooo.com 0 47 MB 71 KB NRS 1.1.3.N1 CubieBoard2
99.227.137.145 0 1 MB 1 MB NRS 1.1.3.N1 PC
patapato.ddns.net 0 64 MB 205 KB NRS 1.1.3.N1 Win7-64b
106.187.102.227 0 4 MB 4 MB NRS 1.1.3.N1 PC
cb2.flipflop.mooo.com 1'972'503 80 MB 125 KB NRS 1.1.3.N1 CubieBoard2
If you look at the downloaded MB counts, 3 nodes which agree are all 50+ MB and are constantly trying to update my public node with their block chains. My local node (99.227....) and bter's node (106.187...) are both under 10 MB which makes me think they're in agreement with my public node's chain and are trying to continue from there. We need to find a way to get the nodes to resolve the issue on their own. I won't be good for us if we ask bter to reset their node... I'll start forging on both nodes again. The account on my public node will be forging with about 8 NAS and my local node will be forging with a little over 5000 NAS. Another thing to point out... The consoles for both nodes are reporting signature errors for the blocks. I've also noticed that the hallmarked nodes are not showing as hallmarked nodes all the time. (Weight = 0 in the list above.) I have seen evidence of a signature generation problem from my public node when I attempted to send out a transaction in the past. There might be more to this problem than just a forked chain. |
|
|
|
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 nodes are stuck at 277935. They are sticking with block 277934 and attempting to link 277935 to it. At first when my node was forging, it was trying to stick it's own forged block there but other nodes didn't agree. A block forged by NAS-3S5R-Q4ZL-QUEA-BWAP2 was there for a short time but it removed it because other nodes didn't agree. My nodes keep destroying all blocks from 277935 and onwards and trying to rebuild them. That is why you now see your transaction in that block but it'll be destroyed soon as it attempts to rebuild it again. 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. I had shut down my local NAS client over night and just started it up again. I'll see what it does. I just hope bter's node isn't suck like mine. It won't be good if it is. |
|
|
|
Both nodes have started following a fork with a 1.5 day gap in the middle... 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 %
|
|
|
|
|
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.
|
|
|
|
Both of my nodes seem to have gone off on a fork or something... Recent blocks: 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: [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 do not like their wallet has a very ugly look, hopefully in a way NFDteam it.
That's one of the things on the list. The new client which was forced upon everyone is buggy, bad appearance, bad fonts (I can't read the text on my client so I don't know if someone sent me 1.456 HZ or 1456 HZ), etc. For those with a different taste is an alternative nxt-like gui for HZ available: https://bitbucket.org/MattWo/hz-nxtgui/downloadsMuch better! Thank you!  |
|
|
|
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. |
|
|
|
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. |
|
|
|
|
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.
|
|
|
|
|
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.
|
|
|
|
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. |
|
|
|
|
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).
|
|
|
|
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. Thanks. I see the transaction but I'm not able to send them to the account as asked. The client is returning an error "Could not verify transaction bytes (server side).". Keep forging if you can. I'm hoping it just needs a set number of confirmations before sending but if not I'll poke around a bit to see if I can figure out why. Odd... The error above appears when I attempt to send NAS from funkyvps3. When sending from my local node, it worked. Transaction ID Date Type Amount Fee Account Confirmations 10231787055063096754 19/03/2015 12:06:58 Ordinary payment 10 1 NAS-AXUZ-74SZ-9SB8-5SFUT / 1252390869854816059 19/03/2015 06:07:50 Ordinary payment 111 1 NAS-H5AW-7J9F-7VCY-DJ8NB 221 10 NAS has been sent to NAS-AXUZ-74SZ-9SB8-5SFUT as requested. 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? |
|
|
|
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. Thanks. I see the transaction but I'm not able to send them to the account as asked. The client is returning an error "Could not verify transaction bytes (server side).". Keep forging if you can. I'm hoping it just needs a set number of confirmations before sending but if not I'll poke around a bit to see if I can figure out why. |
|
|
|
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. |
|
|
|
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. |
|
|
|
The top right corner of that page contains a link to "wiki docs" sending you to https://wiki.nhzcrypto.org/wiki/Nhz_API but this page no longer exists. I'm not sure if the page has been moved due to the re-branding work or if it will be but someone else closer to the project can answer that. For now, I'd suggest that you refer to the NXT API documents for the HZ APIs that exist. |
|
|
|
|
Show Posts
