No one should be using anything but 0.5.9 now!

The Transparent Forging phase 2 will be activated at block 47000 which is approaching. Those still using older versions will be left out on a fork. Those using 0.5.7 are broadcasting malformed blocks and transactions and will be blacklisted. 0.5.8 is ok, but 0.5.9 is much more stable, there is no excuse not to upgrade.

I reserve the right to run 0.6.0 myself.

I also got that one, but the browser recovered after page reload, and there were no errors in the log, only the Re-scanning... notice. So it is working well.

Which error, the negative recent blocks? Any exceptions in the log?

It is the Borg collective... nothing to worry about.

Has anyone experienced at least one error with 0.5.9? I mean, a real exception stack trace in the log, other than due to corrupted .nxt files on startup? I haven't even seen a single blockchain rescan in the last two days, only the occasional "generated incorrect block" message, so I don't know whether rescans still cause exceptions, or rescans don't happen anymore, or complete without errors?

It is getting boring, no bugs to fix... need to focus on the refactoring. And no, no new feature requests until I am done with it.

If you want to support competition and alternative clones of Nxt, then, after the source code becomes open in April, the tools or know-how needed to generate a genesis block should also be published. But there is no reason to personally help FC in particular. Based on his attitude, I just ignore him. I doubt any good developers would want to work on a project led by someone with his personality, so NEX will get nowhere, if it ever launches.

Not me, that's for sure. With all respect to minusbalancer for his work, I think it is a dead end. What's the point of having a reverse-engineered, incomplete client that will run on windows only? We have a Java server that is getting better every day, what we need is a well designed and fully cross-platform GUI for it, not an alternative implementation.

Assuming 0.5.9 is as stable as I hope it is and there are no critical bugs, my next step will be a major refactoring of the code, 0.6.0 will no longer be a single java file. Next, I will add persistence of blocks and transactions in a database instead of using serialized files, and will no longer keep all of them in memory. If minusbalancer used decompiled sources to base his .NET implementation on, he will have to catch up with my changes and bugfixes, and come up with his own solution for the blockchain persistence. And spend time and efforts tracking down and fixing bugs that are already fixed in the Java version, and introduce his own bugs in the process. I really don't see the point.

I uploaded my key to keys.gnupg.net and keyserver.pgp.com a few weeks ago, did you really not find it there?

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.4.12 (GNU/Linux)

mQINBFK/WG8BEADQVgMRtEYR7tdfFXQHHh84x4sbU27G8DZYJw3WulV9ZSKlJu/R
T1l4Sb5B+myilAvEGX8QzCE6YJnOqQoG5RLxl68MMfD4i5Qd1zlGkXJpDWN2QAvi
adbmjmx7/NkpC8JXBZ4mnTLwBTBCnyDW/NZZd0DJO3nTllOVHomT8Xcd23Z58hq2
gOd8k29mfOXJXB2LMSn+TqqA+/pB38qENVU7ZgublwiyZO2OrVnvxXRWfFYzgHbJ
wPCug9DM9eQFHYBDuztfPzDjIUQk+RNJeLlUTq6sprzLc0AoTr36QB/db8MiEhG0
MJIUs0y+OVsuhn7fYuT1/LqIR9uG6Npv3U/n++gxw1CBEHk9MLK2HxVKx6cqYd6o
0tV1+PM2dZkPf9yc9WmXc1F/Sdg+taCOjOPFHBawzHSy0yMn3JC1SPQyYSay8vJk
e5r2XEU90yabP23ycZrIvIM9XgR2xylUbYtODpQI+DSgqIjR+z3uHCK9RDIMdNuH
ICBIJo1EEKOQfRe3rsCdCigOMBdjx/Nsk4bNsrtURJuSwFWlZ/aOaObCkZmuwspX
GcZhpcnUUNG08WBy5CpH62k59awRQbRrJVEeWfTPLLDkV5KXF7gjCAjC67n4329p
4cDgbd4itsb7Qx0hv0U/HjGOTk4lxDzu5WJ65KL2JyXE+2D2xyFd/y1T1wARAQAB
tElKZWFuLUx1YyBQaWNhcmQgKExlYWQgRGV2ZWxvcGVyIG9mIFRoZSBOeHQgR2Vu
ZXJhdGlvbikgPGpscDY2NkB5YW5kZXgucnU+iQI+BBMBAgAoBQJSv1hvAhsvBQkB
4STxBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRDO8fSp/yoZ+l0qEACMaRyq
kFDRsuNUWmll1kq3ixDNrgBtlCkk8pY+pATNOBbyPCGvWrBHqh4n7nx/U+yP5aVY
1GGaMMQrg2svvjHr7DWCPG56wIs8UFXWYA+xq/6/uleCnutZb55a0TM3En4KtT/b
vc0pKFDnEEYDxKYsChAONORp4rHme3sS1BJPqViYeq10Fl/9buCENebW0mlE/Py9
4om5Jmcp4Q6nEmovvJKA5mHsassjXlR4GML4s77vw7hxg5mqAhplCwHODd/ML3V7
/BvsG1BqWjQqII2kN16fOp0BXOdP9Gbf4NP+k7BrjzH8bbMtDvRHFJS5nrRE4+W0
dkyJLOxYJArTP46SjrG8j81xRyq8iTk0Q95C610u2I73/Gbpxrhawyaqh/SHo/jk
GNBq4ghQzuaItD2bXtUb4WNZaweckZqqd+MCgWLEKZxgqcyZgCexTvXq5ZCwgWo6
07+7mVIo+n2RJVs0FiuuFnPjpbmnzVf5/WtfW9s0VY3Dt5doZN+MtBMF6bFA4NV5
72L1RecZFvFC8Mc7fcGhtvVF6rSdkm/yg3u/glVK7CP6s05qq1RNhqhHBhK+/UH+
KfOCJTy5/2nPkhc1Skr/4DiAdYcXMA8RPBF/9+WBuL0wlBA8aX2CcojjU9AGb6kL
ECIES0LO+61moj+dV/GJ6hIPssfSNLnGCGXoGbkCDQRSv1hvARAA9XO8oo+nMoyI
ioziXCtKdWDmNLer4j+eiAiwYJeR2+z5Jlxkp+r4/X7PEouuPeuEvz30E1ohhAdJ
4RejajKMx+KC/1xiyr0M84kDLC5EabQVtFTgw4F3krvVES3Ul58mucpuDroUuDoq
BA9pXvrY8oVM77csTVQKT1bMqV5fPfeJtNnCpWg+GoD3R71P1SzXr/J51vlHRI8Y
U+SaxnXEqdh0/lC9L5FcANw4la62PwqhoH0TJNSPpNfmdrZ1ipLnDVPiwCKB28xx
8oIZrG5uKE0Lcl8uIGq/RC1evCdZumpvG3hLhKI4ou6lDHcO5ccJTPpcnI+qHvuf
xYLT48Z4n2MyljlG7myFl9T6tny16A95R3uIm7WQizgRSIncRWqyydO9mmGI3wNA
Q62mGgirHG6TOCRhY7uogvVE10N30UzKQVBoDpHOzO1oMIDlcjqhQ7ZhsDZOkV+h
1PcwGRYyXZtUlUc20ByR4sPU1Wl1xf4EvbJxcrZMupV1R+LDsOmj0Iby9UTbKKuM
1xr7HJNevPKpKcE9RwPAP2Bb2p3xsIUYVpG18BNaC1KvxloHHH3tbQkb+wEXFTHf
aXTxhppYcnVUglky71pXh9LIuaTyBtXREalipNv/oBa1jyh3oJR9fOv5goGHnTCn
PHeTE+0GK9lk5X9PtMo42+tGIJ+IursAEQEAAYkERAQYAQIADwUCUr9YbwIbLgUJ
AeEk8QIpCRDO8fSp/yoZ+sFdIAQZAQIABgUCUr9YbwAKCRBTocl3O/ntgB8pEADK
HCW6M+vwI1f3RVsLs7oUVwJ0KJruMiRWKRC2B/unI7PuVkB8U2BuGoao79DvwfgZ
ERLZ4MQUCfre20JeVbvTvrcp9qW4D4CepiiPECXv5Zg693zMOmn37zeQXZoeqEn8
skCEThWzgO2HmqpRA/EnUgmqP015gtyi2g7wsCtPUnQItDcded5rIMi3Ed6yxhLb
WHBTFJYxsC8wMjB/4En6Mtj8mZsh8gjvTWVLV7GiR3ihlJlXtcMTnpgKhunu6uZy
+q88Sm44kgtt6nqDZoqg0qjFJyBXji3dbe36f4knlk2JvwxhbRSabe6AquauqlRN
e049dfj3xyAXV3qUpwwQNzIXjTbctuqr4F1WDunRZpR7IV78DriaQeQk9p5xn+xP
cHhKuIboeZ0fhnXWChM7c4ClEyWWEMWAJlttS2XzX/YH2XP7tv+M/ah7RCqK5+/F
4EMGh6OUVYD88h4rVG//TMTSDLusHCNO1GD/6pgboN0iEFWta39eP3zd/AGNZLJZ
Z0EOoPzbJCtT6bE6g+M1bkuNiVZrFRdJA4njCY5BmDOXh+v1bxvBUugs+eIup5yI
JIs8LPIBZrRAC9XDerfz4Nb6CvYPTXwa3M3ne83FGkWL/4iLpTtm81LFQeQPGlq3
KY3gsEubktNkvWnpqWHF/XbJbBQZrmkkw5CC1WKNIXCtEACZoN+5Cok/5DyNuX/Q
zXgcyVsnHHhsX/M6989+ukYNvVegYaUoGEmu/UEIJuYkZ9gDXpjY6x1rrWMoIsk0
VsClRB+RIi1K4h9R0LYLM3XdZWmDflJnX03d4b21dRpXaA2AFJBZrrkP0QLHxNsk
f+nPiIoQsQe/34j8EtpjF1eQMefELaaqoJhXWfG7t/Lj9F2/TVe6EZYkRmJNZx74
zRXLTfmNhsJ/5IkmXQ7+0wGp+HdYIToHFjgPJooMVljDrFr1mPI2UXmOVkeMYYkj
HTz7HrJZwZxoVTW7fPYcgkBlDGW3mAXQwxzcDm2V5VaGEIDNsoDeQ9IBFORpz7qH
Gh5sXz0H8oH3l3sr2wMxyUoFWJgT2Q1WTWMfBuAVPtWWGgBEqt+tGF0DUUGrs7xO
n25jQzwQMYjvqgG7IiEJOpBmFzw2Wdv6vmFKhRKJ5FHoa+t80zU6c3DXTdkUBqFo
11/+cwQLYarKlvBFVuBe59c8Hu/XZUcdMoHK6nZDfqmYzGHtLGlMOFX72V2Ghplr
sagbyazyjvbp92Zy1c5Pz+ZjIYrCB4t5OmHL1sC1UBhSkYap6IKtt/uRIGLRPAdT
eTtUBgPqZMZjiGDNO9hSXxE3jKXSwyR8Ok/O5FisFMb47+qudgeSrcXj7tOa2MHA
xFodLyNhRl0/NHPvMlRAy/9OSA==
=z8Nv
-----END PGP PUBLIC KEY BLOCK-----

No, except there is a custom readObject method for the Block class. I have never tried that deserializer tool.

Does it print out anything else after that? It should log the stack trace of the exception that caused the error.

Restarts? What restarts? 0.5.9 will need to be restarted only when 0.6.0 is released!

Ask the jetty experts. I don't know why those warnings are needed, and how to disable them. They appear whenever a system property is defined in the jetty conf files, but the only simple way to disable the noisy jetty warnings is by defining the system property org.eclipse.jetty.LEVEL=OFF. I also use system properties nxt.debug and nxt.enableStackTraces to control our own logging.

You need to thank CfB for that, he is the one working on adding APIs.

I also want to repeat my advice to use private browsing mode, or a separate browser profile, when accessing the Nxt server at localhost. It is a known issue that localhost url's containing the user secret phrase are retained in the browser memory cache. Could a malicious javascript planted on some website access and retrieve those?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Release 0.5.9:

http://download.nxtcrypto.org/nxt-client-0.5.9.zip

sha256: 35e0454c0eba551637674fa0e607774b864b0f428b5618f0d14f1ddc8d42cb62

Change log:

Resolved all remaining thread concurrency issues in the block and
transaction handling. All reported null pointer exceptions, division by
zero, and related bugs should not happen anymore. If you see any
errors in the log at all, please report them in our bug database:
https://bitbucket.org/JeanLucPicard/nxt-public/issues

Added Asset Exchange related APIs:
getAskOrder, getAskOrderIds, getBidOrder, getBidOrderIds,
getAccountCurrentAskOrderIds, getAccountCurrentBidOrderIds.

Prevent the Recent Blocks tab in the browser UI from growing beyond
60 blocks. This should help avoid browser slowdown and freeze during
downloading of the whole blockchain from scratch.

Added transaction re-broadcasting. To make sure a new transaction has
been received by the network, it is broadcasted every minute, until
it shows in the list of unconfirmed or confirmed transactions.

The debug logs are quiet now, in fact I haven't seen any exceptions in
the last 24 h of testing this release. Everybody should give it a try as
I hope this is a really stable release. In particular, peers still
running the buggy 0.5.7 will get blacklisted if they don't upgrade,
because they keep broadcasting malformed JSON blocks and will be treated
as zombies.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJS27ABAAoJEFOhyXc7+e2ApRwQAKU7kVb+2alcHMFONiNNO1Jo
6IRIX+m76dDgL8af1Ini+I19nl//gaAKY9yIrynCkcGtVQ94NlJPU9DSW9BeqS8N
hsF51n1bX37znv05LAqJ9E8qLARATaerh5jGaA/vRgNLFUQAlH2u+mDvUbPKX5lr
tq6LTqjbo6JXSDlr3by0ngCxQP/yAfxWAUOU5psZdd8NzemlyR4tV5HOCkU2KpYL
4PLp/QFKgbAbILcYU3/nOexscUziLF+DX9uW0geU4Dvd8rcpLOG8T5q17fZwB+oB
jE6nuLZfQ3O+h1iBSJKE2OXFVSbiTCdBd+MkXOHyX9LFgPd9P1mp+7QUqUb9wEJl
Y+CyrGfymdNhAI3IMnrmBY9XVH+WPHqUwKjDLdof8Queti+FAO/YM32QES6z0srA
aPwOKHtSBjZB+zAW0lurN8wSNFZW+K7uv0XZVRvyBisUrpvjywO0YKhIPVzyfC3M
lq0YWcWlXAWMCklNQqC4cODwYvWeE0siyouqGZbZInDabzHrMzZUupL8METe0ZQ0
HPZMLYxwt6h0BSzNGvZtq+rJbMGDQ56Ep68MJUDmnDS8hVvp1Zbr2C1rDtSwsXnR
4w34P8jY1hkM5MsIrZxGcn32JaGeEhgVrKJysCIQKydWhU0qkPpe1JdAV+dEWn2R
Zohlvsnq9PdQOchaWFJQ
=EHOk
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Release 0.5.8:

http://download.nxtcrypto.org/nxt-client-0.5.8.zip

sha256: 4f0ceb4583ba50a7b791635586249868958c90899d7a5033d2c763c701b859d5

Change log:

Fixed a thread concurrency issue which is the likely cause of the
OutOfMemory errors some have experienced. This is a critical bugfix,
users of 0.5.7 should upgrade to 0.5.8.

Added "type" and "subtype" filters to getAccountTransactionsIds API.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJS2DptAAoJEFOhyXc7+e2AQicQAIhfxm6B8EghfpdIIXlzK0KO
MNAXhURrahleSi0TtAL/MMRt3GmhiNeLp3+75ffG40CsQENF5uepYLUd9Fdm5TKM
wt1C8N5+ZLwm6pJFdwtm/RvAPnsmMnpZyqAyBjs3rg8OidqyjClDMESq5/XwB8eI
wsWcPLreyCRBUZkpuZH8l3sfiDNI3LMJ0EWLdRWNKhxQJ3Dmmeiqta3bKWUfhbcY
/0pO5yPZjEhfl5q1TIkc3G0ytZiKqjZbEkpij/GYZiljlj6OPG/D97FRKgQ7AojL
Xpb5NRnP8ZDYgOFXHwSM6EgFqQHP+o05KRZ7x0lGdHxVH0YS/0rZ95aLELQrXORk
OGnRrQ0S6ZVhEhX96J3LEblK2+WtgOI/3eCHjvKWyQWDYWY+eMVcpfReq0l7wAuy
7b0VE6LzfoZ22w7rRat/3ogsoGJvllZMM9FRkryzsbwThpqlf6CjQCYWMAqrH7A7
UwuuyGsKhUTlcNeC7eXzJFLD49n243b039otg4GNkUkiQdvqAZnc7G2qNz+sK9/Y
R13r79o/8saIb/6rG9VYF4vfGk1nejcvJB6kMTEAmF1UoNLEByTvb6MOfAEbiD7Z
W9ALRF8L9ZmiiJ/vCLtv2HIb/WCxWB0TH2vaN/fIalB8SNxBEcym6JkGqzEUvkFE
yxBRoSLbe1gNIAZQ8mC5
=cVPw
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Release 0.5.7:

http://download.nxtcrypto.org/nxt-client-0.5.7.zip

sha256: 20002edeaaf0ffab97ab2f969969acb4f8a9df35fe489361b44e5291d95a33a7

Change log:

After the optimizations in memory and CPU usage, this release is about
optimizing the networking. Instead of sending to all peers, data are
pushed to only 10 peers by default. The number is configurable in
web.xml, the sendToPeersLimit parameter. This should reduce the network
traffic, and should also significantly reduce the waiting time the user
experiences when sending out a transaction. Furthermore, sends are now
done in parallel, using a pool of 10 threads, which means slow peers
will not delay the sending to the rest.

A few of the exceptions found from the debug output have been fixed,
and some more networking exceptions known to be harmless will now be
ignored. The logs are much more quiet now even with debug enabled, so
I have decided to enable the nxt.debug parameter by default in nxt.ini.

Transparent Forging phase 2 starts at block 47000. Everybody should
update to at least 0.5.7 before this block is reached, otherwise we
may see forks.

Added Wesley's send message tool, message.html.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJS1u5wAAoJEFOhyXc7+e2AZAcP/jjVP4jf0F41akVq+SIsFmdV
bwPY5UjSt7dWqMCDX74RngvL2XRXJr2Bgicdgdm5Ei/EN7l2oYUgKMjcHRJ7ZQJa
1uXuqhFv/3pD9VhNIxmV4k93aBw6pggQ67aNBw76zTq8BNUT0j9zPjqBAXZ99caf
Mtf2G51YmW2mbDKJreuxxJBcdNKeVyemDj83Mtj55doo3Bd8bmTrYZY1fB1bfrgQ
JRF8XUymSO7udI2dCTE7JGeqf909fnKRKQhS6wksuoPpPSVondZ0d36r8o5yMxVR
7QTW7c89+DohUK1jbeBeQ9mp4bCuB9XSL+KlvR9G3JhlCF+QTrKYKp3HGLFC7PNe
N4+r7uMbuj5px6zXsbQKdbcqbD8gC9qdtQeuIl2K2kyRc1dDEf6QzK1HTLwpDU8C
QYE7A4BrwVP3wndS/tZXHKgxsDA6qbuEkrJA9HZuvBpmyRG+VhUuPYyud5NlrS7a
yhclmQSlKUxxlSaSY+xMbVyHhs0ubhj/UJqOYy2HLTwHi+St1wvVCfGS9Wa5tkT7
MH0xJyVA7aUhLng+Z3gA88gDVJKMES7/A26FcFIBGXw7/EX4aEhrflChuBD92ocx
uufA7QON4KyQPCWfsiw0XlSFN+cibJVJmiGc4JN4pDoG8Fncivxnwiz5O4B19vFG
Jn1t6HSHVOzHAe8YP9qa
=tTJo
-----END PGP SIGNATURE-----

This is good, and if he ends up needing additional API calls, I will certainly work on adding them. But as a core developer I don't have the time to get personally involved in the integration of other services with Nxt, so somebody else will have to volunteer if Bit777 needs help getting started with it.

In general it should be the community that decides what projects are important, I don't see why such business and marketing decisions should be referred to me.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Release 0.5.6e

http://download.nxtcrypto.org/nxt-client-0.5.6e.zip

sha256: 680490992bc853bcfb988683f7c4de2d41e44636f4911a95544fd44f2d663762

Change log:

Cleaned up error logging and exception handling. There are now two system
properties that can be set to enable additional debug logging: nxt.debug
and nxt.enableStackTraces. Those are defined in start.d/nxt.ini:

   # Enable debug messages
   #-Dnxt.debug

   # Also enable exception stack traces
   -Dnxt.enableStackTraces

   # Disable all jetty warnings and info
   -Dorg.eclipse.jetty.LEVEL=OFF

By default, nxt.debug is disabled. If you watch your log, please do
enable debug output by uncommenting the -Dnxt.debug line in nxt.ini,
and report any bugs using our JIRA issue tracker at Bitbucket:

https://bitbucket.org/JeanLucPicard/nxt-public/issues

Please avoid submitting duplicate issues, check if a very similar bug
has already been reported first.

The nxt.enableStackTraces parameter activates printing out exception
stack traces in the log, independently of the nxt.debug setting, you
should leave it turned on.

With nxt.debug commented out, Nxt will still print some messages to
the log, but much fewer. If there is a critical exception, it will
be logged even if nxt.debug is not enabled.

The noisy Jetty logging of warnings is disabled and the log should be
much cleaner now. If you enjoy seeing the Jetty warnings, comment out
the -Dorg.eclipse.jetty.LEVEL=OFF line in start.d/nxt.ini, but don't
report those as bugs.

The reason this release is considered experimental is that I have
upgraded Jetty from 9.1.0 to 9.1.1.v20140108. People are encouraged
to try it to see if there are any incompatibilities with different
systems and Java versions.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJS1FVSAAoJEFOhyXc7+e2AjIoQAJmgchgVxOkuHzqE7dFud4Wc
VoIbNCan4oCACJ6b3w0YX47PDwAqy6KfzqMqYncEFoL60Ch9kV38/mv1WrxF6s5v
7a3bAO8vIZlnlqQHuDQ8O6VnaMDUlSksZov903kDJapN2ylPtBuV8jvFI5gFEHBY
AWtEZjbrUK7b6HNbenOv3ZpPjYUaUt5VIQvOGl968yZIoi0hsYygBSKUi1sL3sC7
wsB5FVmw3b7oyWjWdFGvtkAupbtO6mIfrUxdy3DyYfezKM+yLRxrQqDcJpFgTD2J
gSCDEnHs4HljbB/UEcxR1C55e+pduetbxbDNf79aI7Pu3i7iStYNG7N+h6KAf0s7
cYUdzjdu8EwKFfxI3U3kFs7hrKkj72NW7AP0YKt7yokrF8rJnqMNHw0flcZ9M6Hj
w7rwywMudTvb1dzvuqBVXhshlCquMyA37w9j+NsiZfxIj6KI68VZzg3txAfIq4zM
76raRNrgFl2Q1JrP3oOFXdhOzLHyzaA9JP2vRP7zRPNnkVslyY2ME0q5vRh/0thX
wgdXs3+P5MO8hAVpVvUCo9HrdGhKv1lzkMWyhuo8X2xP6csfYGOovJEi3wzlKilW
FB88fR9kuTHjQutQF1yzsJoK1czbVUy5iqiITgR6jR865+jB4EszrSD/YQMrsUD0
u7NABXELevQF6t9oPcCJ
=ce/5
-----END PGP SIGNATURE-----