NXT :: descendant of Bitcoin - Updated Information

[ricot]

Do we know how to make the NXT server more stable. As it is each time it hangs, for personal use it is annoying, but not that big of a deal. Unless you are racing to the airport and can't send NXT!

What I'd like to know, what developers doing about this? Because if I know they are working on it, I can be patient, but I find it worrying that a few times this problem was bought up, it was simply brushed off as not important, or even nonexistent.

New features are important, some of them I'm very much looking forward to, but these stability issues absolutely should take priority.

There's a thread in this forum about bugs in the code release. After my client had been attacked, I analyzed, what exactly happened and figured out, how the attacker managed to get the clients to basically crash. JLP and CfB fixed that now mostly by 0.5.3, the only thing that is left is the actual browser page. So when you see negative blocks, just refresh the tab in your browser and everything will look normal again. On the server side (communicating with other NXT clients) the server now behaves normally, even if you don't refresh your browser window.
If you want to see what kind of bugs we're finding and that are getting fixed, jump over to https://bitcointalk.org/index.php?topic=397183.0

[1714933766]

1714933766

[1714933766]

1714933766

[1714933766]

1714933766

[1714933766]

1714933766

[slothbag]

Nxt full source code (decompiled 0.5.2).

https://github.com/slothbag/nxt-decompiled

donations: 6683387465452189666

Updated to 0.5.3

[HinnomTX]

Let CfB and especially Jean-Luc think about it.

I already did. There seems to be no progress whatsoever.

I haven't seen Jean-Luc denying importance of this issue. Most likely fixing it seems hard for him now. And he has too many urgent issues to fix.
We should help him to figure out the right and easy way to implement solution. Once he says - "It'll take me two days to implement", nobody will oppose.

First time poster, long time lurker here. I have a possible solution to the CRC problem. See if you can shoot this down.

1) At block 40000, all new accounts should include 64 bit address + 32 bit CRC. The CRC can be hidden to keep the addresses looking short and clean, and the CRC value would be recorded in the blockchain and read by clients for verification.
2) Starting at block 40000, accounts will have a CRC value calculated for them IFF 1 or more NXT has been transmitted from that address to the genesis account.
Basically if you register your account with the genesis account, you receive CRC protection.

Many accounts have already registered aliases, so they get free CRC protection. If the genesis account doesn't hear from an address, it is assumed to be darkNXT.
BTW, it would be even better if the account holder could send a specific 'alias'. let's call it called ADDCRC. If ADDCRC is sent to the genesis account, the genesis account bounces back the NXT to the account holder to make him whole again.

[ricot]

Nxt full source code (decompiled 0.5.2).

https://github.com/slothbag/nxt-decompiled

donations: 6683387465452189666

Updated to 0.5.3

or: go to google, search for "java decompiler", click the first hit, download the program, open the Nxt.class file that is in the NXT-client download

[Vega]

There's a thread in this forum about bugs in the code release. After my client had been attacked, I analyzed, what exactly happened and figured out, how the attacker managed to get the clients to basically crash. JLP and CfB fixed that now mostly by 0.5.3, the only thing that is left is the actual browser page. So when you see negative blocks, just refresh the tab in your browser and everything will look normal again. On the server side (communicating with other NXT clients) the server now behaves normally, even if you don't refresh your browser window.
If you want to see what kind of bugs we're finding and that are getting fixed, jump over to https://bitcointalk.org/index.php?topic=397183.0

0.5.3 been running since released, so far so good. If it's still running OK in the morning that would a new record for me. Can't wait to find out.

[jl777]

There's a thread in this forum about bugs in the code release. After my client had been attacked, I analyzed, what exactly happened and figured out, how the attacker managed to get the clients to basically crash. JLP and CfB fixed that now mostly by 0.5.3, the only thing that is left is the actual browser page. So when you see negative blocks, just refresh the tab in your browser and everything will look normal again. On the server side (communicating with other NXT clients) the server now behaves normally, even if you don't refresh your browser window.
If you want to see what kind of bugs we're finding and that are getting fixed, jump over to https://bitcointalk.org/index.php?topic=397183.0

0.5.3 been running since released, so far so good. If it's still running OK in the morning that would a new record for me. Can't wait to find out.

Running 0.5.3 via NxtMac, on bad branch?
36406      14571285356259793594      January 9, 2014 2:27:28 AM GMT+02:00   
2      0 + 3      305 B   
2      5313834224092465353      74.3 %

2901 orphans, 8651 unconfirmed transactions

[TwinWinNerD]

I guess im pretty unlucky. Forging with 60k-100k for >2 weeks now, no block found...

If you forge non-stop with 60k, and if the total amount of nxt forging in the network is 500million (my guess - is there a way to find out?), then the probability of you forging exactly N blocks in 2 weeks is approx.:

Code:

N=0:  8.898%
N=1: 21.529%
N=2: 26.043%
N=3: 21.001%
N=4: 12.701%
N=5:  6.145%
N=6:  2.477%
N>6:  1.206%

So - if you found no block then you were indeed unlucky. Or did you find a block but it had no fees?

Wohoo, i just found my first block. 0 Fee, but it feels so awesome. !!!!!

[kunibopl]

Im a loyal american veteran who not only served in the desert but went back as a contractor.  I also possess a security clearance.  And I cant find too much terribly wrong with snowden.  Now bradley manning is a different story though. fuck that guy.  except he'd probably enjoy it.

why did you go to this desert? were you curious and wanted to get to know some iraqis or their favorite dish?
if not so, were you alone and depressed and eager to find friends(or partners) in the army?
are you maybe from alaska and did you want to see the sun?

tell me, I am all ears!
I charge 100 NXT for that.

PS. I am from Germany and find it incredible, that their are soldiers, financed from my taxes who drive up the prices for appartments in Kabul, so that Afghanis can't affort them anymore. I find it incredible, that these soldiers, who are freely going to this nonsense in Afghanistan, come back and need psychological help, because they saw a kid die. Fewer kids would die, if they weren't going there.
At least they should pay for this psychological help themselfes.

[TwinWinNerD]

Is there a vanity generator for NXT addresses out there?

This guy got a nice one: 666666817378784428

[ricot]

There's a thread in this forum about bugs in the code release. After my client had been attacked, I analyzed, what exactly happened and figured out, how the attacker managed to get the clients to basically crash. JLP and CfB fixed that now mostly by 0.5.3, the only thing that is left is the actual browser page. So when you see negative blocks, just refresh the tab in your browser and everything will look normal again. On the server side (communicating with other NXT clients) the server now behaves normally, even if you don't refresh your browser window.
If you want to see what kind of bugs we're finding and that are getting fixed, jump over to https://bitcointalk.org/index.php?topic=397183.0

0.5.3 been running since released, so far so good. If it's still running OK in the morning that would a new record for me. Can't wait to find out.

Running 0.5.3 via NxtMac, on bad branch?
36406      14571285356259793594      January 9, 2014 2:27:28 AM GMT+02:00   
2      0 + 3      305 B   
2      5313834224092465353      74.3 %

2901 orphans, 8651 unconfirmed transactions

See if refreshing your browser window helps...

[jl777]

I am using wesleyh's MaxNXT so not sure how to refresh browser in this context. I click lock and login again, but all the same orphans are there.

I can redownload the entire block chain, that is one option and it fixes it for a few hours, then goes bad again. At least it did the first time. I will do it again and see what happens

James

[ferment]

has anyone done work on creating unix scripts to function as command-line operations using the API?  If not then I will create a bunch of scripts

Here's mine in ruby: nxt

To use (assuming you have ruby installed):

Code:

$ gem install thor json httparty
$ curl -O https://gist.github.com/fermentNXT/8327705/raw/3e1f8a1c2276b38f1c77ba4db60ce013eeeef58e/nxt
$ chmod +x nxt
$ ./nxt help

Let me know what other API calls you want and I can knock them out quick.

UPDATE: added getAliasURI and listAccountAliases.

[ricot]

I am using wesleyh's MaxNXT so not sure how to refresh browser in this context. I click lock and login again, but all the same orphans are there.

I can redownload the entire block chain, that is one option and it fixes it for a few hours, then goes bad again. At least it did the first time. I will do it again and see what happens

James

What's that? Why aren't you using the official client?

Well, if it's based on the official client before 0.5.3 (very likely), then you still have that bug...
Solution: Get the official client

[jl777]

I am using wesleyh's MaxNXT so not sure how to refresh browser in this context. I click lock and login again, but all the same orphans are there.

I can redownload the entire block chain, that is one option and it fixes it for a few hours, then goes bad again. At least it did the first time. I will do it again and see what happens

James

What's that? Why aren't you using the official client?

Well, if it's based on the official client before 0.5.3 (very likely), then you still have that bug...
Solution: Get the official client

My understanding is that MacNXT embeds the official client, it says it is using 0.5.3

All caught up:
36420      14571285356259793594      January 9, 2014 3:16:56 AM GMT+02:00   
5      500'000 + 13      691 B   
2      15607836971861154475      188 %

The problem seems to happen after a few hours. I did "update peers" before this redownload of blockchain, so I am hoping for better stability.

James

P.S. I did not change anything from default installation other than Update peers

[slothbag]

Nxt full source code (decompiled 0.5.2).

https://github.com/slothbag/nxt-decompiled

donations: 6683387465452189666

Updated to 0.5.3

or: go to google, search for "java decompiler", click the first hit, download the program, open the Nxt.class file that is in the NXT-client download

Wont give you diffs though!

[ricot]

I am using wesleyh's MaxNXT so not sure how to refresh browser in this context. I click lock and login again, but all the same orphans are there.

I can redownload the entire block chain, that is one option and it fixes it for a few hours, then goes bad again. At least it did the first time. I will do it again and see what happens

James

What's that? Why aren't you using the official client?

Well, if it's based on the official client before 0.5.3 (very likely), then you still have that bug...
Solution: Get the official client

My understanding is that MacNXT embeds the official client, it says it is using 0.5.3

All caught up:
36420      14571285356259793594      January 9, 2014 3:16:56 AM GMT+02:00   
5      500'000 + 13      691 B   
2      15607836971861154475      188 %

The problem seems to happen after a few hours. I did "update peers" before this redownload of blockchain, so I am hoping for better stability.

James

P.S. I did not change anything from default installation other than Update peers

Ah, ok, found a thread about it in some russian forum
Yes, it's basically just displaying a browser window in a different frame, so unless you refresh that browser window, it won't show correct results...
you can try apple+r, maybe that works, depends on how he implemented it.

[jl777]

ricot,

Plz don't worry about me. Your time much better spent coming up with more evil twisted ways to break NXT. I am super impressed so far by your work!

Just wish I was fluent in java instead of C.  I knew that at a high level, getting untrustworthy data to get trusted was the key, but having to lookup every java call, just made me unable to see the forest through all the trees.

James

[TwinWinNerD]

Is there a vanity generator for NXT addresses out there?

This guy got a nice one: 666666817378784428

Java
====
https://bitcointalk.org/index.php?topic=345619.msg3759147#msg3759147


x86  (just exe)
===
https://bitcointalk.org/index.php?topic=345619.msg3735874#msg3735874

thanks,

got: 12345678612257264594

[opticalcarrier]

has anyone done work on creating unix scripts to function as command-line operations using the API?  If not then I will create a bunch of scripts

Here's mine in ruby: nxt

To use (assuming you have ruby installed):

Code:

$ gem install thor json httparty
$ curl -O https://gist.github.com/fermentNXT/8327705/raw/3e1f8a1c2276b38f1c77ba4db60ce013eeeef58e/nxt
$ chmod +x nxt
$ ./nxt help

Let me know what other API calls you want and I can knock them out quick.

UPDATE: added getAliasURI and listAccountAliases.

kickass, well  guess ill have to figure out another little project...  but after apt-get install of ruby1.9.1 and those 4 gems when running your nxt help I get

root@vps1:~/tmp# nxt help
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- httparty (LoadError)
        from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
        from /usr/local/bin/nxt:6:in `<main>'
root@vps1:~/tmp#

[jl777]

What web.xml options add most to stability of NXT server? The stability problems could simply be from suboptimal web.xml settings.

Does the 0.5.3 install use the most stable options in web.xml?
Are there any other files that need to be tweaked?

I am thinking that a lot of the problems in the field could be related to having a wrong set of settings. We are so close to a stable NXT server. I updated my peers list and now it is not going brain dead. Still need more time, but looking good so far.

The only thing that was changed was the list of peers, but I remember seeing a bunch of different tweaks. Has anybody tested the effect of the different tweaks on NXT server stability. So much work has been put into NXT, it would be a shame if a new NXT'er gets a bad experience due to suboptimal settings.

James