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

Release 0.8.4e

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

sha256: 9778318546c73f5585669a560ab07af483d0b1ac5c30e3580ebf8524acae1825


Change log:

Several changes in the calculation of unconfirmed balances and
unconfirmed asset balances. This is an attempt to fix the
negative unconfirmed balance bug and "Not enough funds" error,
but hasn't been tested, this is why this release is experimental.

Enabled use of testnet just by setting nxt.isTestnet property
in nxt.properties. No other changes are needed.

When switching to testnet by setting nxt.isTestnet=true, peer
port becomes 6874, UI port 6875, and API server port 6876.
Those values are hardcoded to prevent mistakes and take
precedence over any custom port values in nxt.properties.
Also, when NOT using testnet, the server will refuse to start
if peer port is set to 6874, again to prevent accidental
mixing of real and test blockchains.

For testnet, a new subdirectory for the test blockchain will
be automatically created, nxt_test_db.

You need to set nxt.testnetPeers to a list of known public
test nodes. I have set up bug.airdns.org with the 0.8.4e code,
and a copy of the testnet blockchain, as obtained from holms.
I hope other people will also set up test nodes and announce
them on the forum.

In this release, when switching to test net, the Voting and
Asset Exchange features will be automatically enabled. On the
real net, they will still be disabled. The NRS UI client
however doesn't support those features, so you would need to
use a different UI, or use the http API directly.

Added nxt.knownBlacklistedPeers parameter, for manual
blacklisting of peers in the nxt.properties file.

No longer overwrite the peer address with its announced
address in the Active peers panel, use only the IP to uniquely
identify a peer.

Allow disabling of the DoSFilter for the peer networking
server. Added nxt.peerServerDoSFilter.maxRequestMs=300000
parameter, because the default value for the DoSFilter
maxRequestMs forcefully closes peer requests taking longer
than 30 s, which breaks blockchain downloads for slow peers.
This is very likely the cause for the Jetty error warnings
we had back in 0.5.x days.

Added Generator.getAccount method, and START_FORGING and
STOP_FORGING events, of interest to Java API clients.

Added run.bat script for Windows users.

Source code is now included in the release package under
the src directory. The compile.sh and javadoc.sh scripts
can be used to compile the source, and regenerate nxt.jar
and the javadoc documentation.


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

iQIcBAEBAgAGBQJTFP4qAAoJEFOhyXc7+e2AVEgQAIWNSlu5YCNt5UiwbCF0qVbR
EpU1k2fQfbQPfIa5EFw48gEU/5yc9NuVfLZ2EM1OWIxaWLgR38uKy6XR8WaT8UlJ
tTicbrHoZA6Ffiy0YqYWySzJvDJ5Dhj11I253yZh9Lql+/8t8xKMlX06gJNwV1jZ
a+2rhpEVB8VFSBORGQQgaiRhqVX417/7nYENd5P/5KuEhP+u/5GxVKlEXccLAmsW
yJT9A2oxLECkEEb5iLVeWLm7sJuqfL7uFG/mwnV5tzwruo+hG3Ow2vNu20Bv1FuX
I3qnm0ZNzs2CdiOUvUU3Ev3tCfHdCpMqJk2Nsk5eIQfAF74swL+0MpDx/run5w91
4zYiOIUcu85CC1lwZ+12pBo5bMGrbzGD1gYjnZBQBnO+2We1DRTXq3lQTjk116FA
TwStx4gvEZfnU62+j3pNcZ279rb83EbFa/9fJHRQbUcwCuqFh/rOElSBfQLdeB6I
IpGleo9sNELPsXxr/e+fEY/4J9g2/bP7Rg/SV1+Vy0bRqV7MRryaTGt1mj4WxgyR
FkG9stBdojcad7v8CCsTLFCkxvUm4tI5ast9qS3LpSacmuHYG3gGwOh6Vxkb/49y
hxpEoRLXtRspEliLKO2VBGhorG4H+7r9iAr4Q/n2e+6KtTzbQ9bfKePK1SxKhgvU
s46Hl1xUl8KOUXxUOu7o
=o/W0
-----END PGP SIGNATURE-----

I will explain in the release notes for 0.8.4e, hopefully later tonight.

I am setting up a test net server that I will be maintaining myself. I will need people to run additional test nodes, so that we have a real test network, not just one or a few servers. Perhaps some of our existing public nodes can be switched to test net instead.

run.sh assumes you are inside the nxt directory, so all paths in the classpath are relative to it. If not, you have to use absolute paths, and in the example above also do that for "conf", assuming it is under /mnt/nxt:

java -cp /mnt/nxt/nxt.jar:/mnt/nxt/lib/*:/mnt/nxt/conf nxt.Nxt

I dropped this field because it has nothing to do with the server state. It is very specific to the NRS client UI only and represents the number of its user sessions. But it does not reflect users using clients that connect through the http API, or through the Java API.

As for the status of testnet and holms.cloudapp.net, CfB should know, I don't work on that.

This is what I plan to do next:

1. In 0.8.4 I am adding the ability to easily switch between real net and test net. First, this will allow anyone to use the test network with just a single change in nxt.properties, no need for a different client (of course for features like Asset Exchange one will have to use Wesley's client, but the Nxt core code will be the same). This will allow many more people to participate in testing. Second, by having the test network and the real network run exactly the same code, with the only difference being at which block height features like AE and Voting become enabled, there will be no risk of additional bugs introduced in porting, or any need for porting of code from test server code to main code.

2. We need to get the Asset Exchange feature rolled out. There is one remaining critical bug, the wrong calculation of unconfirmed asset balances, which I have tried to fix in the latest 0.8 code, but haven't been able to test yet because the test net was still on 0.7.6. Thus the importance of the previous point about having test net in code sync with the main one.

3. Before actually enabling Asset Exchange, I need to make the transition from storing transaction amounts and fees in Nxt to nano-Nxt (0.000000001 Nxt), or whatever fits in a Java long, given that the max possible balance or transaction amount is 1000000000 Nxt. I previously thought about adding a new transaction type, but this will be more complicated and ugly in the long run, so better do it right. At first this is just about increasing the precision at which amounts are stored, enabling actual usage of fractional amounts and fees will be done at a later step. But this has to be finished before the AE is turned on, it will be much more difficult after that. And it will have to be very well tested, so again we need a reliable test network.

4. I need to move the remaining classes that are still stored in memory only - Account, Alias, Asset, Order... into the database. It is not critical yet, because they don't take much space, but has to be done before it becomes a problem, especially with the Asset Exchange that currently needs to keep all open orders and trades in memory.

I have made the current source code repository public:

https://bitbucket.org/JeanLucPicard/nxt/

Master branch is still 0.7.6, develop is 0.8.3 plus latest unreleased changes.

I apply for the NXTtechdevfund. I have been working on the Nxt code since Dec 25, 2013, and have taken it from a single java file to where it is now. I am much more comfortable writing code than managing projects, but I will certainly have an opinion about the directions in which the Nxt core should be developed, and so I should be involved in deciding what projects make sense to be funded, and estimating the efforts needed to complete a project given the current state of the Nxt core.

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

Release 0.8.3

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

sha256: 9a59c60336e01e87a3a1484697dd35a57d8782747145f8049496e19cbffdd537


Change log:

Fixed UI problems with display and updates of My Transactions.
Consistent counting of transaction confirmations. Transactions included
in the last block are considered having 0 confirmations.

When a block is pushed, the BLOCK_PUSHED event is now emitted before
the REMOVED_UNCONFIRMED_TRANSACTIONS and ADDED_CONFIRMED_TRANSACTIONS
events.

Added BlockchainProcessor.RESCAN_BEGIN and RESCAN_END events, triggered
before and after a re-scan (not the regular start-up scan).

Fixed a few null pointers caused by bad peer data.

Improved handling of peer addresses and hallmarks.

Added blacklisted status to peer info.


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

iQIcBAEBAgAGBQJTDkldAAoJEFOhyXc7+e2Ag+AP/2Loj424Fy7FWFC3Nr8xD9Y2
RaMaG8qSX6sKnSmvzp6ogLQF9RwNRdR+7ebhUjOB4NaObT2VcVFP6GUHpzXEQH+J
v44pV/odFTzlnRCgGWREzteUmjG01xyoSpp7CEaqd8ZSnvFuLg0MCq2viHhCIg0M
/tEYLK7RmrcGMrsPOUutg3xME1ERoRC1YjuMPCCJSSP9JHm2L7D2S4LxvH+xQT8x
OwPoKXmgsMn8nXsudMRWMyVAwzpYT4AkgUqXYzsLBMeVKcLePfbwgqzMT6Z9IKUR
MTStGn3dXYsm7+2n2zP+oDy1ob3FKGlnMmqa/BaHZySpwTLD0kebPLRVjkgoj3eD
2apwugeeP84eLVKy7o1LApRXrVSYdw3MW/ZIDe2H/8LF3HaHuINNXSAgX3aslvyR
kJxkcRyAFl9C7nT0mSH2vUAHk3n3hA/1meuJ4rCOw03JxI3wMjJGjR4sHtWO4ik3
r7I4UywzG89ABXZOAM9Q7ItO3NL5HdrcGfsDSc0hVZehqKYDHOZSdrPpb03rJont
NOYxo4oEsf8DGOLFiLtYGN9zCtWkjsVl3fKMvVmRIqutz/VqSXL2kQIdVR6oUI9k
QMBXMUfzXAiEcOdYPx0VjqaJmbitLVF0qXL+TByTkROzP7TRYqJHWdCzqiAA3Jr3
9UpvYGW111MyHY53Hcyf
=7618
-----END PGP SIGNATURE-----

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

Release 0.8.2e

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

sha256: cd0ceda97fd1752d6fa2877bd4a343570f8b62ae1de2009cd7688087c619c3d4


Change log:

Mostly minor fixes for problems reported with 0.8.1e.

Fixed hallmark string in json peer info.

Improved Logger, added removeListener methods.

Don't set Content-lenght headers when using XMLHttpRequest to send POST
requests.

Added jetty-security jar.

Moved worker_sha256.js to tools.

Also add random mynxt.info nodes to default wellKnownPeers.


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

iQIcBAEBAgAGBQJTDNiwAAoJEFOhyXc7+e2A1lYQANcxMSCbyzTkzYKLwGFtphxe
3gtZfbN+PW/KZrvp3am4pRKiP2HsEVxKzk8UjC2dRUYkbNKc/K79ck9o+qkIprqF
+oOnj5VgjT1LmUrBg0sQrScxyDELLmF4A89dk4WFre+JRdGYManLdEsCRfbCf2jC
uOwhIrtej5gEP8FMj6NG2UiY59xdc2UMtSdGYUaSsYZhQNjS6514LQPtwlKGXUfh
bZNqaRut4ZoegbDEtNfVJOI+BzZB3OOkReEl371YeCBSkhAkboZm1Zhzi+oLwni0
3nENhzCk0LurufoBIzFW/sKr0HyMhJYAXfSKsGRb3blJO1KeVNIStjAwWJgcqcNF
agyL/5aciBMvTj6eu6wl/TqtB1pSwQzks3DPfUT79vAlECkb+5JnYQxFtuseKV44
IaSRUMNXfcfn2LjHU7Pz1Hrhfmc525fUHcD1V0S8ANVlb6Ig0X0snxPCSli2SmQL
atABusbXjaFxDRh7bbGTdQGWlu/6cN5AIuNjuDFElrRnmf/ItyxwpHweeEdV3f5j
2dJz8vQ3AJyuTC+hCqUcYgrPGFpEKuknK5T/4uI4yADSmBH6LnOJkG76yNwMugBu
swu5INrushwQZkL4rxmnQMFN+r57VRXy+2hA7bbWW/+G3DPq7DW7SaWi3umyZV61
Obqrmy8qIs1siIy2rmva
=Zg4G
-----END PGP SIGNATURE-----

This is the problem, you cannot have multiple addresses there. You have to put the network interface on which to accept UI requests - 127.0.0.1 if localhost only, 0.0.0.0 if all interfaces.

No, no, no, don't do that! There is nothing safe about kill -9. You have to use kill -15, and should see "Database shutdown completed" in the log before shutdown.

I will remove the setting of this header. There were no such errors in firefox. And I just copied that from an example about how to do POST with XMLHttpRequest I found on the web... I guess another obsolete or wrong advice:
http://www.openjs.com/articles/ajax_xmlhttp_using_post.php
I first tried submitting the forms in admin.html directly using send(new FormData(form)), but this didn't work, couldn't figure out why. So I had to manually encode the parameters and set request headers.

Should be https://localhost:7876/nxt . It is the "nxt" that maps the url to the API servlet which accepts both POST and GET, the top level url is served by the jetty default resource handler for static files which does not support POST.

Why don't just set the shareMyAddress to false then? Your node will function fine with incoming connections completely disabled.

I don't want to complicate the configuration by adding yet another boolean parameter whether to start the peer server or not, in addition to shareMyAddress.

The thresholds only apply for outgoing connections from your node. For rejecting incoming ones, only blacklisting works.

You need to set nxt.uiServerHost=0.0.0.0 , by default it is 127.0.0.1 so localhost only.

Try port 7876.
http://localhost:7876/

I added two more properties to the defaults:
nxt.apiServerEnforcePOST=false
nxt.uiServerEnforcePOST=true

Port forwarding is only needed if you do want to receive connections from others. You can always make outgoing connections and this is sufficient. If you don't want to set up port forwarding and receive incoming requests, set nxt.shareMyAddress=false, so that you don't unnecessarily run a peer server on port 7874.

Yes, you can use POST for all requests.