Latest NRS Release

Release 1.5.11

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

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.5.11.zip

sha256:
bd5054abc528099f890051f92557b9cfbb03f7f891861650b37b9da80ab92eb0  nxt-client-1.5.11.zip

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.5.11.jar

sha256:
cdde0dc9dcf3f48611785bb8ec1cf91959e87df7ddfc3d740d6439c790502df2  nxt-client-1.5.11.jar

Change log:

This release removes compatibility with peers older than version 1.5, and no
longer accepts connections from them.

Conditional logic dependent on block 445000 has been removed where no longer
necessary, as block 445000 has been passed now.

Parallel blockchain download using 36-block segments is now the default
regardless of height. Returning more than 36 blocks at a time by getNextBlocks
is no longer supported.

The maximum WebSockets message size and the maximum allowed response size to a
getNextBlocks request have been reduced from 192 MB to 10 MB.

A checksum at block 445000 has been added.

Added isDownload field to the getBlockchainStatus and getState API response,
indicating if blockchain download is in progress. This gets set to true when
a batch of more than 10 blocks at once has been downloaded from a peer, and
gets reset to false when an attempt to download more blocks from a peer does
not result in any new blocks added.

The peer requests getUnconfirmedTransactions, getMilestoneBlockIds,
getNextBlockIds, getNextBlocks, processBlock, processTransactions,
getCumulativeDifficulty, are being rejected while a blockchain download is in
progress, as indicated by the above isDownloading property.

The timestamp of the last connect attempt to a peer is now included in the peer
JSON object.

Added a connect parameter to DumpPeers debug API, to force a connection attempt
to each known peer first, adminPassword required if needed.

The run.bat script on Windows no longer uses the -server flag by default.

Updating nodes of version older than 1.5 to this release will delete blocks
after height 445000, to make sure such nodes are not left permanently stranded
on the 1.4 fork.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJVdgddAAoJEFOhyXc7+e2ABgwP/jIMisZ9jS9up9WeKo4sWgEL
9gVNP5AdVVp9JCiMRnZPl+5Re7znqMdvxVuzK13JC3up3hS5YMWZY9LwzShpRPCU
wtzFDOpbdKomN4hgjm4fTjsEtgwOm7vNbKKz4hSQD3DxfIcQwUQFe2X8lMvusuhv
z0TyQDBdlCAlR+fRtdvka19C/D5bKfGW7FQhusnQEs5uXAAZ+rtMW7EM3PI3yXR3
bh7voLwuL5VHbjdd2T0Rh5r/+vYaR6I3GJ6A6HpwurRzKHWjANL45AJxNi3F64h8
F6r7+n/dJNQc0FxIrWas5pCCkONNojVHELHbxFviorPMF8xcFRus5AvVSJrGo+f3
L1mFFXfSOFNnN7OXKdkDhNDOvZMCxf/FHqYeYXifsf3eEn8fww4KzaADchE8cCcY
9r61WzXK11kYxluh2ehs+wyRvgHLz8t//yOxCG5/BUBI4J2RqEBZlgSy3o6qPB7X
mN7ytM7EDiUVRBiV0QbMucOl1t29Jt4DIfNCf7QmxjuHjLMpJHGdYQJboHGWocE/
vTNsJsL9MiHK4DwT6O/1Vbp4hRU/XG+OCWq7TndJTngKtYJMVu4EYF1y+gPuggro
fagRVAOJFKmJM4pDjpt4o2y4kyA8o5q1fG4CnY8GTLXW7uFTOo0ZBp4hVN9D7ZDl
C5OXG+a03lk8rUvC7h+t
=g7Q3
-----END PGP SIGNATURE-----

NRS 1.5.11 Windows installer

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

Windows installer
https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.5.11.exe

sha256:
6f1d248b9c17cacaf62a5faba96d408cd14c8145952e12383580ea10e7d72795 *nxt-client-1.5.11.exe

To verify the installer executable:
Right client the exe file, in the Digital Signatures tab verify the signer name is "Stichting NXT", you can view additional information by clicking the "Details" button.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJVdrHxAAoJECdelKfYMRZRgiEIAKJCopIM87xQZuDCy+CnFuPD
KWFZFEtHgTsAGzvc73tgTS6jD68FkRe7Ne3IQTrjy1mOwQvX3wik29lBEQa7Y3EY
c2eqfGoZ7MnOJlVpvaLRu2IsRYuxrJgY6gzAclbAx0dIynh6NrtuIsudfMBAHS/S
GZlDnTnSBUWUXNObuRIsE4NIQl+9LrxwZcXf2mH13i18TpHahL/ol5xs2/cYCtZ2
OBw14/NOTlGWYQPTAOuEGsh6l12ehPKKyBUPWax0vn7wWlK2/C8h3tlFv3nI45dq
tbp84EC/lZR6XLp7TPwffPWywOJe77WnyuzPFubDgh3hfE8S+zHlIN73TZ6sh+c=
=rK9M
-----END PGP SIGNATURE-----

NOTE: 
Windows 32 bit users can either install from the zip or from the jar. 'Since we decided to distribute a 64 bit JRE there is no point to distribute a 32 bit executable', writes lyaffe.

Nxtforum NRS 1.5.11 thread: https://nxtforum.org/nrs-releases/nrs-v1-5-11/

Release 1.5.10

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

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.5.10.zip

sha256:
07737a52c843f10067c77171a89342cc6aa613fc87fc2442eaee71fc6448792b  nxt-client-1.5.10.zip

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.5.10.jar

sha256:
6735d643893833319222e64ce40a050bf4acd6ca2dd9716bf574d17270b36193  nxt-client-1.5.10.jar

Change log:

Create installer package for Windows and Linux using the IzPack installer.
See https://bitbucket.org/JeanLucPicard/nxt/issue/283

Added separate linux and windows (cygwin) build and release scripts.

Track and log database query execution times. The new properties:
nxt.statementLogThreshold, nxt.transactionLogThreshold, and
nxt.transactionLogInterval can be used to configure logging of slow queries.

Database performance improvements and optimizations. The account leasing data
has been moved from the account table to a separate account_lease table.
More table indexes have been added or existing ones modified.

Improved JSON encoding performance.

Outbound websockets connections are no longer initiated when using a socks or
http proxy (if system property socksProxyHost or http.proxyHost is defined).

Include expired prunable JSON in API transaction JSON, if available.

To protect public nodes from unneeded extra load, the getState API does not
include counts even if includeCounts=true, unless the adminPassword is either
provided as a parameter, or is not needed.

Added numberOfAccountLeases and numberOfActiveAccountLeases to getState,
showing the total number of scheduled (first lease only) or currently active
account balance leases.

Limit peer details length to 10 characters for version, 20 for application,
30 for platform, and 100 for announced address.

Client UI improvements:

Fixed a bug sometimes not showing notification badge after login.

Improved Bulgarian and Slovak translations.

Fix local signing of upload tagged data and approve transaction

This release will perform a full blockchain rescan on first start.

Updated jetty to version 9.2.11. If unpacking on top of existing installation,
delete the old lib folder first.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJVb3UwAAoJEFOhyXc7+e2AuvIQAIlgBHVUaZ4vQKPtfNC5u6kV
4NQ7L6FDAdlhf3MOsaEoe7s64TjcdhKfem5wTRwyTtipsZXwb0Sj2U8FpPZZtZG1
CN2fheF7NxXciXOavjvlLONAdu2Iskr5b0XLdBQYuQwmHeRjU5ihCGpfry3PK9a2
+9RcXauza1uJ8yWtFCcRZ0n6K572YfPjFA10ZwCscsIbzq4prDlgXfJ2BjK8MpZe
H3MA4HGR5PsBV3jtWkikVJN5IQDX7aBklWS6oVmSndjm776L3B1Ifgf3Vt3g2203
WRyHWGvt4dYV21v7dyLLXgqaD3fwIg3x//EiFIh4mEYTvLcZgEt/Sqh9JLFlOPC2
Sb5oJaRQi6328JEBfMUilRhpr516119M3tUXT7d1BZdkHSJyUjZnaIk2EKPGJlYh
ljHTiVR7MNm9n1+8II5U+aexcdVOa959aSsKRsp8FmsnTgmkc7BO/Q49JYHAHKFf
xbho1n4UAqD5ayiXEasz5x9KtH8mChLnFSf4NKXxBJv82STtKrcu61mjdqSFDd7q
B+IbocEcufRvpA0SFKpW7YSKbtKnNtYU1z03W6EQKDzjXtcSkNuk+mBcX5PufQqE
wr2qyRXp5FrrmaNcOoZF2N5AJZqEepDI4rgcRZeGpzkfbhCpqqN9kr3mxm3jFxaN
bXYneC+0F5YyHUpq0GLA
=XArA
-----END PGP SIGNATURE-----

Release 1.5.9

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

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.5.9.zip

sha256:
144c9ecfc5d2b3540dec4eb0a5d94ac67a9142645be858236315cfee0777a03e  nxt-client-1.5.9.zip

Change log:

Enable Voting System, Phasing, and related new features at block 445000.

This is a hard fork, upgrade to 1.5.9 or later is mandatory for everyone.

If upgrading from 1.4.x, read the 1.5.0e and later changelogs for the
important changes and new features introduced in the 1.5 series.

Peer networking improvements. Peers unreachable for more than 7 days and not
listed under nxt.wellKnownPeers or nxt.defaultPeers are removed from the peers
database.

Updated some translation files, added Bulgarian and Catalan translations.

Other minor bugfixes and improvements.

Important licensing change:

The Nxt core software is now distributed under the GNU General Public License
version 2, with the exception of the client UI code which remains under the
MIT license. Please read the files LICENSE.txt, COPYING.txt and
DEVELOPER-AGREEMENT.txt for more information.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJVZOuIAAoJEFOhyXc7+e2ABEYQAOBEmKG60lzyt9XmhTPM7San
lOT2smcbifc9PgUdl3tZQcktFwWOTI/76VUgNK5F76CVNJOpImGcs5aPFjna3Eu5
ws4w7xMJyx0pCRCuqNaZOjcw3r1vQp5ULk/HMLegURxk/lgmAC6ov333YSb4Ny4u
XvwvCUWBMcS4ionzh4YbJe8sbZC7lKNskSvjlgb3jmWrUnxIMsusHkP4xKo2IvND
lklo0VJlp9AlelKPof/o9hOrw0JR327i5NOaVWrJGuSK1Zykkp0vf8W1gvJkErSl
92Qg7sX+2khDtI+14mmltVN15ZaPgZgyj+6ieWR1NiHnBsp2DWxHvl76J2BVCNs/
IlX5bE0oeL/9eaYm/D0A0uJuPHOa4M0TAsFwmSqB5fd1+OKTIRRe+OTuhboIzVSv
FkAgl5S8qW5OouU059EmnUAViDhFJ4dOU3H78Vsu2+DbtXmD+r5fkCFzSnVNFO9N
cdQscn8FTjesH4pQBD5jZ2NZn6rWo9XA57dda4aZBNwFQvrrqQZFmm+WYs8JqcMD
NdMTELP/1Ap/LZ6P+azOewGexLBtj24O4I/k3UP+kdBKwg1EKqmFpMjovydIuK8Q
CMNR2en+j+npMR1YpBQxBuVD8pKq1n2v+wnpy3rPACkourUDe+UVqLnOYICapO+W
j3eztUng/Du4h0mOvnyA
=n/IH
-----END PGP SIGNATURE-----

Release 1.5.8e

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

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.5.8e.zip

sha256:
f08df2cc050512f5d49cac62767aa7715b4021db4dccec082d68cad8b55ea9f3  nxt-client-1.5.8e.zip

This is a development release for testing only. Source code is not provided.

Change log:

This is an experimental release. It is a required update for all testnet nodes,
but is also possible to run on main net.

Set the content type to "text/plain; charset=UTF-8" when sending http requests
to peers. This is an important bug fix, as the incorrect encoding of outgoing blocks
and transactions containing some Unicode characters can prevent their propagation
and lead to forks. Everyone running the experimental release should update.

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

iQIcBAEBAgAGBQJVVa+5AAoJEFOhyXc7+e2ARxEP/jXqPsR74gDieYXXpkLik+ir
T0w0R53NEQVetuv3PNysLT69z1rsBKqRgdTbnFJ3ttmxB+CQrekzD12bJv6i3I+3
O3YNZM8vweYuClw0OfbVKcCdxjs8r1ipVhUpiLwsrPSvi3h8MppHdnZrZBlcEdFn
g7jJ6ikDH+lGhOvvbp9E7vU8qLIWzpRsMaj1xR9h4ek/+wmuop4UBCdx2lYWlEsT
R+Mr8tj/Lgj5+dpsAMCqLMR6wmVo7h/g0SX7s0uWrFQFU1BXRmBBcuMv3pVEp76S
oQw8Y5u5uMBvGnraeMKuzm5caYtYvQpHzTVIJFcHWb23kYjrO57lyXiWB0i8j4Yy
sFRhWzzDwA06AtbgpWBKHEApM2XlsR+UxUHgMeVnHqGAF1XuG0isvjON1AKi9xAV
GV92ARVgK+5KY6PnNCn0WM0yIp0dMvhsCxq8q0Cxk+Fmvf2gt5BuvCel8JXqHY2E
hU1TBhOpK9A/g9feEC0HGaDGs/NjAysM3utCIPFMxoes0mXcI5khhRYoOL0fTe/y
wj6q9ec6pJwOzgmp1MYbGpyoVGDpbP7UI6xj/6jtOOpKpOMX5bY86Et/9GdXms4a
YPNu9lFN36AAfHYtqhmGOce7H7STnVJaiUnCFMmOnaZYJKKCwFX9TSr/pAhLPWMw
CfKS14VNVxq1DD8IeUxP
=1i9p
-----END PGP SIGNATURE-----

Release 1.4.18

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

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.4.18.zip

sha256:
05e0357f092e372daa03885489b00255bdf4821c797763e1aac04bfcc2fcacf8  nxt-client-1.4.18.zip

Change log:

This is a bugfix release. Everyone is required to update.

Set the content type to "text/plain; charset=UTF-8" when sending http requests
to peers. This is an important bug fix, as the incorrect encoding of outgoing
blocks and transactions containing some Unicode characters can prevent their
propagation and lead to forks.

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

iQIcBAEBAgAGBQJVVZedAAoJEFOhyXc7+e2AyDIP/3VZVodJOO6YAZqLGYIzxxkO
K+TQPhz1Avrq82eWUr/UbN1aAlEU9+cyAkj2Nx4af+lTu/UpR7yKWVStDHtQvwCp
9lvPxtrFhNj4IpYb0MyYRpFBEVsZysfEWR1/zD2kt7Xdw/AJVp9+ICkyYXOy6Fyt
T5zCDdghGAoo6ML9w6G226rvlg+ytDCuGlNeh+sYFKQyD2Dqmm2t2N6rUCO9oHlc
dm30pVFLtHdta5UIChrNFrUnpEQ5pTUXXNh+R3cgLMWUYozeHgEfrRC15ctfj4MA
tusQ3u9Zz1L7pXeLR8Cz1RI0g5PJ44OWx5ZuFHA2r9Le785k21ofiGivL3S01ows
JFwv88mQYTDGnh3XxPKMOVK2nGWbMScC+e/y4k6HUh+grUs5x+7PF837BBsEzIwc
7IFd3vztJOvjQea/DrRxpAFDKziPJLXu5E005T/lX97PvDafyLJXfHkn/m5ZUAns
/x1NoOk1NRTdAYVfd1zMXVmGp+aw9vdDEkdsuj1y8JLobW3m7DGrPqoMGqjOUgpI
Kxs/KY9u/oJAPHehIKwR3ggWJPIUxHfFk4sFinF/+e7qvtVrcbKoxLVPHz34dxRs
4cJmITCnFr21rW05nPzFjpd7Jyyprhy8dn1zgkxV2qZTdjjeWbIx1obKTF61e75Y
Zr1/+bJLrojA+cEa6Juc
=I4Us
-----END PGP SIGNATURE-----

Release 1.5.7e

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

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.5.7e.zip

sha256:
a5e318ee4422a46f1347891b2b71be7553739b1b768398b82696a011fe2b6d05  nxt-client-1.5.7e.zip

This is a development release for testing only. Source code is not provided.

Change log:

This is an experimental release. It is a required update for all testnet nodes,
but is also possible to run on main net.

Added WebSockets support in the peer to peer networking. When connecting to
peers that do not support WebSockets, HTTP is still used. WebSockets can be
disabled by setting nxt.useWebSockets to false (default is enabled).

Implemented parallel blockchain download. After Constants.PHASING_BLOCK (not
yet set on main net), blocks and transactions data will be requested from
multiple peers in parallel, in batches of 36 blocks (when more than 36 blocks
need to be downloaded), instead of downloading up to 720 blocks from the
single blockchain feeder peer. This is expected to reduce the time for full
blockchain download, once most nodes upgrade to support the parallel download
protocol.

Added file upload using multipart form requests to the UploadTaggedData,
ExtendTaggedData and VerifyTaggedData APIs. Added upload file button to the
corresponding forms on the /test page.

Added DownloadTaggedData API, to download tagged data as a file.

Added optional includeData boolean parameter to all GetTaggedData APIs, default
true, to allow omitting the actual data from the result for saving bandwith,
since it can now be retrieved separately using the DownloadTaggedData API.

Improved search by tags. Improved validation of tagged data.

Added includeEffectiveBalance to getAccount and getBalance API, default true.
If false, effective balance and guaranteed balance are not included in the
response, which should improve performance for these APIs.

Added HexConvert utility API.

Improved GetConstants JSON to include an alternative transaction type JSON
representation.

Peers in the nxt.wellKnownPeers list are always kept connected, regardless of
the number of connected public peers or the total number of know peers.

Added GetInboundPeers API, to return all peers that have sent a request to this
peer in the last 30 min.

Added inbound, inboundWebSocket, and outboundWebSocket boolean fields to the
Peer JSON returned by the getPeer and getPeers APIs, to show the inbound status
of each peer and whether it has established an inbound or outbound websocket
connections to this node.

Limit the total number of inbound or outbound connections, using the properties
nxt.maxNumberOfInboundConnections and nxt.maxNumberOfOutboundConnections,
defaults 250 and 50 respectively. The nxt.maxNumberOfConnectedPublicPeers value
cannot exceed the nxt.maxNumberOfOutboundConnections value (if it does, it is
set to nxt.maxNumberOfOutboundConnections).

The getAccountTransactions and getAccountTransactionIds APIs have been
restricted to always return only the non-phased transactions. Those APIs have
also been deprecated and will be removed in 1.6. The getBlockchainTransactions
API should be used instead, which has the same behavior but returns both phased
and non-phased transactions (by default, unless either phasedOnly or
nonPhasedOnly parameters is specified).
Do not simply replace getAccountTransactions with getBlockchainTransactions in
your client code without an understanding of how phased transactions work and
without being prepared to handle them correctly.

Added links to the Wiki documentation for each API request from the /test page.
The links are autogenerated and thus work only for the wiki sections following
the same hash tag pattern, but most of them currently do.

The JavaScript NRS.sendRequest() function no longer accepts a callback function
as its second parameter. Instead, when sending a request with no data, specify
the value {} as the second parameter and the callback function as the third
parameter.

Client UI improvements:

Implemented client side signing of the tagged data transactions.

Added File Upload form, accessible from the settings menu. Allow extending a
tagged data transaction from the transaction info modal.

Integration of current status of client translations for new 1.5 features,
new "experimental" state for languages with translation status at 40-50%+,
added Czech, Greek, Hindi translations in experimental state, updated translation
state for other languages (Beta: 70-80%+, Stable: 90-95%+).

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

iQIcBAEBAgAGBQJVVR4kAAoJEFOhyXc7+e2AhfAP/0TVI6e1ahbCUBAmn/EOAc8s
9TLMf+S6y2peECY0xSxPkIlFbwiTrEXGAeDgXq5kSq1T7n9zkBLzSXNMK6GNDC1P
wOXBj2YKFCWkqcJB1wBOejyLKx3/95QuUZsoVnhJy1JkSGllGG1dVnc0fiaXhTEw
+Gbse61O539bJJNV53j2xhAt24ztLsJVtvw3MZxFSuqOfKpxdyQ7FcLaElUqNQ+e
jBUyICejisLgRUm9y7rxS+iKZeVAyuSszPKzD/O03Zt31YJXNI66VXYaX/+x7sTx
UZ3F36dL42L6GM085XPCBYpnEVG++D+f0KcmhZCGb0tCssS9XnJ3D0wHMmCAUZQH
5sNgEkpwroAyk/0Q6W7c88JFXY+XxkqKJ3oYcxw+FUV5BZwYvbjV0y624yMQijU5
0mPE2+D+cHD+iJ7ji337+CX3JTrMc4pVQ8p78AMIqFOsEAhGJ7Frgu5z0c5zfi0M
JUfIWFx0UFEd38eRmMC0XeqncI7aRn6OrKQThbPsKnCD8iQBYy3c9JwfW0i2Q8kG
6fT5LGZGNWSaO9CI502EgqZzgtS++jQ4zijGunsizEJ9bPaXAeyXI+Wmnpo510Mn
qxkARVVq4W8IVUkdUoVjFvEYSRPjb+gE4u3gnGuiOK0wm7mJZI/yQsAkeJ15Rvaf
LwnUsHHXFMZV2icRl7OY
=wqid
-----END PGP SIGNATURE-----

Release 1.5.6e

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

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.5.6e.zip

sha256:
e9733f755961468bd7684862394bd564c1e80c1a7f1af075c490bf9e54a37985  nxt-client-1.5.6e.zip

This is a development release for testing only. Source code is not provided.

Change log:

This is an experimental release. It is a required update for all testnet nodes,
but is also possible to run on main net.

Peer networking improvements.

Announced addresses are always verified to resolve back to the peer address and
not accepted if they don't. Old peer instances and old announced addresses are
removed when a peer with dynamic IP changes address.

If nxt.maxNumberOfKnownPeers (default 2000) is exceeded, the peers pool size is
reduced back to nxt.minNumberOfKnownPeers (default 1000), keeping the highest
hallmarked peers first.

Peers are only identified by IP address now, not by address and port. Multiple
nodes sharing the same IP address will be treated as one peer, with announced
address and port as of the most recent GetInfo request or response sent out of
or received from this address.

Incompatible change: If using non-default port, the hallmark must also include
that port, otherwise the hallmark is ignored.

Optimizations in unconfirmed transaction propagation. When forwarding newly
received unconfirmed transactions to peers, if their count exceeds 10, the
broadcast is done in multiple batches of 10. When requesting unconfirmed
transactions from a peer, the ids of the transactions currently in the pool
are included in the request, so that the remote node does not need to include
them in the response. The response size is also limited to 100 transactions,
unless the requesting node does not provide such exclude parameter.

Each tagged data can now also have a channel field. The searchTaggedData API
can filter the search results by channel, and a new getChannelTaggedData API
has been added to retrieve tagged data by channel, optionally filtered by
account too.

Fixed the UI for AddPeer and BlacklistPeer to accept admin password if needed.

"Approve Transaction" action is now available in the transaction info actions
tab.

"Reveal Secret" field is added to the "Approve Transaction" modal when voting
model is "By Hash".

Enhanced the /test page to accept and pre-fill the test forms with any parameter
values supplied in the url, e.g.:
http://localhost:7876/test?requestType=getBlocks&lastIndex=10&includeTransactions=true

This release will perform a full rescan on test net.

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

iQIcBAEBAgAGBQJVP+4+AAoJEFOhyXc7+e2ABmQP/3S4AenMy0UX8LHNdvWgVR6r
w680wxxk/vgsGbqdxc+mc5InypXxtlQSjfkGwc8wurFik6zC0ufqNcTizglfoBUx
zuFYEYSIdbls8VLSwwrvFpsi8OFVvCmomUcDIjwwU/FuhiJGOhfq1yxrOPrOwJ8Z
H5R4ekoo7YjtzcyPofiGImZxtXMDtF4fKn5X4pEid7uGdBLGdGpCqjOkebh5azEd
3Oy9fp9hGE/8jgtv5/3e7nHFK7WnUFv0doVZm4xqZquIOL21d+VvoZjhuqyNNuG/
n6T/4U7NjFaRU0SFM/DE55xbEBSaXq6xFEzAVCrSL4epd7y7ojlyHbezNz8qOG82
HPY6Yxi+tpz377RViqlsAxW6/oZPMCs81TTalwizKK/0bEC+fGwTcPlIlihEcqcI
kDuFtyqADdwqMSu2AjcZDz1CnhOFc5q5gro96JFKRm7cLLoWtJbCefRmHpc2keHu
qn1MhA5OuI2sh4QotC1mIK2eqiQXlBwEAn8zRcyp3gTrS/DjRwc04WKgbfKP246T
ShAYk/xciK1LHTREgZuyCey4kLzE5+rOXIGWFdGW+IDxvI8nJ6gXkX5V+JkFvnz/
bYXD1JI+0sDSAVv9McNBfgKFAPOs0k8qvMRH0XNiQTqjVtEjssEKggEkhFqmyG2V
t5xJqhI7RqnnyPIIbew+
=Wl/f
-----END PGP SIGNATURE-----

Release 1.5.5e

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

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.5.5e.zip

sha256:
fdb91461a6b39f7604442d36b341b22692452f60ef1cd329f9254406a8103dec  nxt-client-1.5.5e.zip

This is a development release for testing only. Source code is not provided.

Change log:

This is an experimental release. It is a required update for all testnet nodes,
but is also possible to run on main net.

Fixed processing of unconfirmed ExtendTaggedData transactions.

AddPeer and BlacklistPeer APIs now require POST and admin password.

This release will perform a full rescan on testnet.

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

iQIcBAEBAgAGBQJVOQUQAAoJEFOhyXc7+e2AjgsP/260GZ7MZII7tCixgfYxnQAr
c6l6NidktcAgeBftfLHbsZotWi0VvOrs9Z6aj/apPRd/p1BWCN/PpaojFx+R1VDZ
74NKPbDvsdi1ofIKzgbTyWaQdoPQObCtapEvQ18hSZEufYt9v+TGGTSovpmpz0ep
qKKp+PTf8kaGEIBohwVL8II42R7m3tKagGoGmhNM+gku4KCMY26gyhyRTKoW7N97
/QLb+XJkG6Yk/euX1NBalCLS3re6DEcn5CfG6ovENhaI2GD7BYO69w7v/t2FULzF
nF3o6i0iZ9hAntQllyVJv8eqYq6u9j4DZfHtOmWJvDFzMg59RMJV+Kf9yYZyVesw
OsZhgQtQfq7AY5wCgLkHqOPep1AV84sPLdMDvJRnJaeCFHZfFLaWFLXMk5Bav4nU
8FbKOav9yAFjJGbmySifsbTG7mvE6PQRjOSYrJ2Dc4eNdtjK7xskTSGiCek8I+ik
cdwxDykejzhxU74S9LeiKcFr+geYJy6XsJKuXq9y5CE6sBGn5cvybjGLJeNIIj3j
2TdLoxRzTlGiU77hDoVJwGXxa5SOLU9sjfKZ3S84LLBYrA9MHSrPq7aXlAjQ0REk
JVnwvZ4pjx8C+dj+XtW10yQ/pxTwzKrAWEJouILpRvJCQXIC2ESx/acK3onz+H1X
zJZ/pu6tEqMZG2xAI6Mo
=G0jY
-----END PGP SIGNATURE-----

Release 1.5.4e

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

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.5.4e.zip

sha256:
70876b7b78e1494c4d46597ca9d73858e0c6e6484f238d592e0a02b19644607d  nxt-client-1.5.4e.zip

This is a development release for testing only. Source code is not provided.

Change log:

This is an experimental release. It is a required update for all testnet nodes,
but is also possible to run on main net.

Fixed a bug in parsing ExtendTaggedData transaction json which prevents such
transactions from propagating between peers.

Added permanent message option to most send transaction dialogs.

Other minor bugfixes.

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

iQIcBAEBAgAGBQJVOBU6AAoJEFOhyXc7+e2AJUIQAMApPtEb80YJOSYPeXgDgU1W
wDfmaj0peclkKvB/XzFG4xsr6ZTHicPGBdRCXidKY/qxWx/5pCNT+jMUkXZQJpfT
05JWx2eihAHBVSoibW0GxiFI6lPtkv+fOkiHvOK4y/6BsodzbB41zHh7mfhP9YXJ
zeDfj6z86GsyRz+z+wie8LYtAYCtmK8c2EGYyuDB1+U3A8Z6hpHRI3QtdpaKtI4p
j2+ZkHEaC0CP5nYRnwtLaFLrsmmXFL+rIfE0AWu3EfXHIYknon26xkc+vLoF84fp
aszMca8V3dWoPEenCA7PgIfclxSDPtidAuvfGMj/P+7MV5XJPiDCF9QmLPLO2vzJ
xioxfNWLTPb8bJtCHciKm9Q0hBSpNA5Bfm7MRmWlCF8kfjrffqzpx4vh5YoCw2Hc
Nn6xi65zls4Bal+xaFe5lGcKhy5glliPlebwxIcQMPEBmfQaINRQAtLHBscFcd26
svbdHkS6Ha8EU+tC5pzGckM7ojUff76hJWYXhGKPJ6iUTnEGYR/SymbvHpdpkD8d
gQmKt3qYjqEooZQyHbISWQJumEtzr1zoqyvy7uP5GqZWkiVDaoKytnIifUPIIV7m
wU8HhrswX19KXp0KeeBAtCSjEG17SEyPSdFjddvJ55Z3ICj5vMZ9hpgm4yoLpjRG
2fU+ZAkIbsdJyCETqoZV
=EjZE
-----END PGP SIGNATURE-----

Release 1.5.3e

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

Release 1.5.3e

https://nxtforum.org/nrs-releases/nrs-v1-5-3e/

sha256:
393a71bc869b7dafb2830eef2d29665f24c7c1c64741f3ecc103a088c4f85ac3  nxt-client-1.5.3e.zip

This is a development release for testing only. Source code is not provided.

Change log:

This is an experimental release. It is a required update for all testnet nodes,
but is also possible to run on main net.

This update adds the Prunable Tagged Data feature, planned to be enabled at the
voting system block too.

Prunable tagged data are similar to prunable plain messages with no recipient,
but with additional searchable metadata fields added. This feature can be used
for decentralized and trustless distribution of small (up to 42k, including
the metadata) pieces of data, which are by default stored for two weeks only
(24h on testnet), but can optionally be stored longer or indefinitely by some
nodes, and can be verified against the blockchain even after their expiration.

Currently each tagged data can have the following fields, in addition to the
data itself: name (required), description, tags, type, isText, filename.

Name, description and tags are indexed and searchable using Lucene. All data
and metadata is prunable, after pruning only a single 32 byte hash remains.

Fee for either uploading or extending tagged data is based on the total data
size (including metadata), and is 1 NXT for up to 1k bytes, 0.1 NXT for each
1k above, up to the limit of 42k.

New APIs:

UploadTaggedData - create and broadcast new tagged data.

ExtendTaggedData - extend the expiration time of already uploaded tagged data.
If the data is still available, only the transaction id is needed. If not,
already pruned data can be resurrected by including (in addition to the
original transaction id) all of its fields too, i.e. name, description, etc.
Anyone can submit an extension, not only the original uploader. Each extend
transaction increases the expiration deadline by two weeks (24 h on testnet).
Extending an existing tagged data from another account does not change the
original submitter account id by which it is indexed and searchable.

VerifyTaggedData - used to verify expired tagged data downloaded from another
node, against the hash in the current blockchain.

SearchTaggedData - full text search on name, tags, and description, optionally
filtered by submitter account.

GetTaggedData - retrieve tagged data by transaction id.

GetAccountTaggedData - retrieve all tagged data submitted by a given account.

GetAllTaggedData - retrieve all existing tagged data.

GetDataTags - returns the distinct tags of all tagged data, with the number
of data having each tag.

GetDataTagsLike - prefix search of data tags.

GetDataTagCount - the total number of distinct tags.

All the Get* and Search* APIs above can only retrieve tagged data that has
not been pruned yet.

There is no client UI support for any of these APIs. It is expected that
specialized third party plugins will be developed for specific tagged data
use cases, depending on file type and target user group.

Currently the pruning of tagged data is controlled by the same configuration
properties that are used for prunable messages expiration.

Same as with prunable messages, when using broadcastTransaction API to submit
an already signed tagged data upload transaction, the prunable parts must be
in the prunableAttachmentJSON parameter in case transactionBytes parameter is
used. If submitting transactionJSON, it already has the prunable parts.

New debug APIs:

GetAllBroadcastedTransactions - if transaction rebroadcasting is enabled,
returns the unconfirmed transactions that have been broadcasted from this node
but have not yet been received back from a peer.

GetAllWaitingTransactions - returns the unconfirmed transactions that are
currently temporarily kept in memory during transaction processing.

RebroadcastUnconfirmedTransactions - if transaction rebroadcasting is enabled,
causes transactions currently in the unconfirmed pool to be broadcasted to
peers again, until received back.

Other changes and bugfixes:

Improved handling of invalid transactions during block generation. Fixed
validation of AE order cancellation transactions. Fixed a memory leak in
processing of unconfirmed transactions. Set the default limit on waiting
unconfirmed transactions nxt.maxUnconfirmedTransactions to 1000.

The DGS goods delivery data size will be limited to 1000 bytes after VS block.

Bugfixes in prunable messages processing.

Fixed phasing with whitelisted approval accounts.

On testnet, this release will perform a full rescan on first start with
rollback to height 263895.

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

iQIcBAEBAgAGBQJVNA9YAAoJEFOhyXc7+e2AH/oQAO8GUyGVaqC/64pdO/1AM4Hx
ID0gbtGxPT8hTpifnS9QpKJKo8/YeDtyh4OmGn9pCnjYjO9wl3TyjIqi9sxQOmYX
mjo9p/C/NK2y2JqwAKIfwOTOEqG7I5iseE+kEH6lDFA50jHONJcj7q+UYM0LrfEr
CWZTQkf0jVNCoYqY+oZ5aSOhMS2BPl7tjhX6v3Y7xBgtq5NT/OALJykC3gkcDZ7A
w5B+9Ip/VUwtX2jVStunScQc6vrfT52seUBi8XzduRQAPoa7mNB5OnlTmE52glW1
uXwDFOD1OJgWFHNwDOmPAqmPf+uvXOv4Nir+yKlMlMe/ntRUhV1TenqM2fMSs+bh
YG0CB+0VmPP/VgIERff3CLILXlXr9CpDCFI1wS4BgcNb+BbvrDoJwA+W0ebhcBbG
zIuki3y6HJQ0krTUiURGKrTHMKvuBL9rBq9pbqAfqbTkT6oHtZxj/in+PMycJ1V4
+DDE+qmb8BZuOjsV7iyRwqZpoxnOat/t0Ryri2ByKpgsmMLu91jivi+h59zXOW+i
5ZLdMK8yIuRJEOYKDEOub/pX4PV7R3OkMLAeerFBfZ5ekmOIJpNB4Qc5bBgz+ZOq
MTGM7AzHZ3gISOXsG5JQOorut0ARW9fhW1PDNk3/pmhQMXu6UgYx9Cl1zbglz9S6
Jg/uehgLcHbZ8uHj6FeH
=oJRe
-----END PGP SIGNATURE-----

Release 1.4.17

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

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.4.17.zip

sha256:
baf2eed8fb1b677b735c04a4b34efc506e8e9a091ae0c66e5dab767a31d60f6e  nxt-client-1.4.17.zip

Change log:

This is a critical bugfix release. Everyone is required to update.

Fixed validation of asset exchange order cancellations.

Fixed excessive memory usage in unconfirmed transaction processing.

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

iQIcBAEBAgAGBQJVM1nhAAoJEFOhyXc7+e2AoOwQAKYni5TVfMh6CndO/hkJCT1i
G5Pg+Abqnx/cE8d6l2j/FIov5eCSCN66Sjva65EFh2wxuYWnSDEXHYf+LBO1bxh4
ZSSbOdUECPapQk2S5byggPBYpxW4PnNnyFF5xaxTYWoASs+RUsap3T0ZzyLprq2c
+NdJ4McFyBIwRSQESzY4SDSKD6vI1umby1eJraCa7ES99JJcu3s/3BnjoH8FIf7l
CHmw6t7q7iVnAeQFep3BJxnIe7Pqr7+XlhU2uZ1wyb2WyJBPQj4fSqOISUmtqIhD
ayemgEOWDh0KQAvE949kO9V97Mf13y5DSonkdWzMjcEbE/lAKuUShh9eJ0URnM+9
VKreVgGwm0yCdw0rBw+z/2x6pQbrp+MTU6EShbdCUCJv7dqHCpeIi4h/Gklog/8I
kKjWzCfFcvRCnLRP7U2MGAb8P+zAeYuRRHic1A6xl8Cp1p685dm3fg80ZvahpgQr
0QLHKtrZGEs3cAQwUo/4CrTExFoYjqtyYYX0LuYjQrXrLELWis+yjxKzf8Iq3BDf
oaWHezwb7aLIoWFGSs3Jxv61Zo20YMfMZqom9M/DE8usapShIZ1Gkto93XYjUFkl
r1DyqQPKfSRJHKoYZt42+TnkhnWkkgP1+KAMf/WH6NZTVQ7Pvs7LjSGnwAxyZ0tS
EMzX2idJXJpeqleZmLZo
=5qu9
-----END PGP SIGNATURE-----

Release 1.5.2e

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

Release 1.5.2e

https://nxtforum.org/nrs-releases/nrs-v1-5-2e/

sha256:
464e8d6433ed6cc0051e039d60b914b2cd5ec44477a8841571ef4edd313fc3f1  nxt-client-1.5.2e.zip

This is a development release for testing only. Source code is not provided.

Change log:

This is an experimental release. It is a required update for all testnet nodes,
but is also possible to run on main net.

Added getAllPrunableMessages API, returning all currently available prunable
messages in reverse block timestamp order.

Added verifyPrunableMessage API, which can be used to verify that a prunable
message obtained from another node (a service provider) matches the hash found
in the blockchain, i.e. has not been tampered with.

Show maxPrunableLifetime setting in getState and getBlockchainStatus. Show
current number of prunable messages in getState.

Changing the nxt.maxPrunableLifetime property now also affects existing
prunable messages (next time pruning is run), as transaction timestamps instead
of expiration timestamps are now used.

Reverted DGS goods delivery maximum size to 10 kbytes, same as in 1.4. For
goods of a larger size, a prunable encrypted message should be included in the
delivery instead.

Removed core restriction on 28 byte minimum prunable message length, this will
be checked by the client UI only.

Added nxt.includeExpiredPrunables property, to be able to force to still
include the prunable parts in the returned transaction JSON, even if expired,
as long as they are still available. Can be used to force an archival node to
always return those, thus allowing another archival node that feeds from it to
also get all of them.

Limit the number of unconfirmed transactions that can be brought in memory to
nxt.maxUnconfirmedTransactions, no limit by default. If set, transactions with
lowest fee/size ratio are dropped from the unconfirmed pool first. The ordering
is same as the one used when selecting which transactions to include in a new
block.

Added requeueUnconfirmedTransactions debug API.

Added support for uncompressed non-prunable encrypted messages and encrypted
to self messages, as a new appendix version, to avoid the need to specify the
compression status as a request parameter when reading them.

Added setLogging API, to allow changing log levels without having to restart
the server.

Added eventRegister and eventWait APIs, to be used for registering listeners
and waiting for server events instead of polling.

Changed the parameters accepted by broadcastTransaction. The prunable parts
must be submitted either in the transactionJSON, or, if using transactionBytes,
in a new prunableAttachmentJSON parameter, which has the same format as the
transaction attachment json. The prunableAttachmentJSON is also returned by
the signTransaction and getTransactionBytes APIs now.

Added support for prunable plain and encrypted messages in the client UI.

Added optional buyer parameter to getDGSGoodsPurchases API.

Voting system UI improvements and bugfixes.

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

iQIcBAEBAgAGBQJVLsMrAAoJEFOhyXc7+e2AOWAQAOi7yY1vO+7ipOLi82G97Iqb
E6u2VL6xWQ8mSVgm0BV8aPc1WkDH4kDXKewG6Ka5FPh3bpEMJqeCdz5L/aqLsKGc
+OhfHZv0lYNihx/TMSPKX39/kn0L1USFdNGkFDG4kjKf9b/9q/QckA5IJ6LKqu0B
0QmQZ2snb0rVAM+EzhynzJwim5QSsiQX9J9d9DhZ47cicSGLj2vuFMsBdBVNn6tG
ldNMKr+QOfAOHQSWbPmUPs6MUCefA7ubpkPD6R1ZKI+b9FEDNcnkZWpMVWDZZijH
ou5TTjnowzrMzyuK5JYWG92vep/sKKQ7n6JgfQecqaqKNvbWj8RGVc+hfG8nWmWx
wpDpl+Qdo90VBw/+/jrdiCD3GySNlpbsrVwco2PCPpZCWYghrGm8uLbFdKYf8VBs
NMQ4KZEpyCE/Ndqzdvk0IVKxnU6gHn4EPmJtJBJE2EPMUncQLIsQ8LhisyLGuASW
yt4PbdNEY5XkdwJgySPxBnghhhdxRxXvrp0CtJdRiT0Q2kyv8O2r17yVLr5LpPqj
GtEA9lIhKXnUcTZ2tYeCOdn5mM9t7SumBys4ouyHPDAaupdTvHklcnaUXkHSWJoM
UGlzst0hdQ/yN3GAyV0ZSTtjyq++Oof7S0L9S3v7sxLJU6zraQwD4H9pEav4CGl6
H8VEh1ZxYSmgVEuIz5IY
=aGAE
-----END PGP SIGNATURE-----

Release 1.5.1e

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

Release 1.5.1e

https://nxtforum.org/nrs-releases/nrs-v1-5-1e/

sha256:
7f56babc8bce1ab12117dea86c0225611bb6eb86796de6c7869438a575523722  nxt-client-1.5.1e.zip

This is a development release for testing only. Source code is not provided.

Change log:

This is an experimental release which adds the Prunable Messages feature. It
will be enabled at the same block as the Voting and Phasing features.

This is a required update for all testnet nodes, but is also possible to run
on main net.

New features:

Prunable plain and encrypted messages.

Plain and encrypted messages can now be created as prunable. For a prunable
message, the message data itself is never a part of the transaction bytes.
Instead, only a 32 byte sha256 hash of it is included in the bytes that are
being signed, used to verify the signature, or to generate the full
transaction hash or id. This makes it possible to completely remove the
message data at a later time, keeping only that 32 byte hash, and still be
able to verify the transaction signature and have the transaction hash and
id unaffected by the pruning.

Prunable messages have a predefined lifetime, after which their prunable parts
are deleted from the blockchain. This lifetime is measured starting from the
transaction timestamp of the message. When a node receives a transaction or
a block from a peer, it is only required that the prunable parts of any
prunable message are also included if their expiration time has not yet been
reached. If it has, and a valid message hash is included instead, the block or
transaction will still be accepted.

Currently the minimum lifetime of all prunable data is set to 24 h for testnet,
to allow easier testing of this feature. For main net, it is tentatively set
to two weeks, but this is subject to change before the stable release. Note
that pruning is performed at the same time as derived table trimming, which
by default is every 1000 blocks, so the actual removal of the prunable data
from the database will happen with some delay after their expiration time.

A node can choose to keep prunable messages longer, by setting the
nxt.maxPrunableLifetime property to a larger value. It cannot be set to
prune them earlier. Changing this value only affect transactions received
after the change. Pruning can be disabled completely by setting this property
to -1.

Prunable messages that have not yet been expired, but are past the minimum
lifetime, are only retrievable using the getPrunableMessage(s) APIs, but
are not included as part of their transaction JSON.

If a transaction containing prunable attachments is phased, the prunable
parts are nevertheless saved and available immediately, not at finish height.
If their expiration deadline comes before the phasing finish height, they
will be pruned and not available at finish height.

Fees for prunable message attachments are set at 0.1 NXT per 1024 bytes, with
the first 1024 bytes free (the regular transaction fee depending on its type
still applies). This is again subject to change before the stable release.

The full size of prunable message attachments is limited to 42 kbytes. Note
that the full size is still included for the purpose of calculating the total
block payload, even though only the 32 byte hash is in the transaction bytes.

The size of regular plain and encrypted messages in this release has been
restricted back to 1000 bytes, and will likely be reduced even further, before
the stable release. This will be done in order to encourage users to switch to
prunable instead of regular messages. Fees for regular message attachments
will also be increased substantially.

Creating prunable plain messages of less than 28 bytes is not allowed, as at
such small sizes it is more efficient to store the full message instead of a
32 byte hash of it. There is no lower limit on prunable encrypted messages.

It is not possible for a transaction to have both prunable plain and prunable
encrypted message at the same time. It is also not possible to have both
prunable and regular message of the same type (plain or encrypted). It is
however possible to have a regular plain message and an encrypted prunable
message, or a prunable plain message and a regular encrypted message.

Prunable encrypt-to-self messages are not currently supported as there seems to
be no good use case for them.

Prunable encrypted messages can optionally be compressed before the encryption
(default is to compress). The compression status is stored and does not need to
be specified when decrypting. Regular encrypted messages are still compressed
by default, but this compression can now optionally be disabled. For backwards
compatibility, since their current bytes format does not store the compression
status, this needs to be specified again when decrypting, else an error or
unreadable data will be returned.

New APIs:

GetPrunableMessage - returns the prunable message for a given transaction id,
optionally decrypting it if encrypted and if a secretPhrase is supplied.

GetPrunableMessages - returns all prunable messages for a given account id,
optionally limiting to only those with another account as recipient or sender,
and decrypting them if a secretPhrase is supplied.

Prunable messages that have already been pruned are not returned by the above
APIs.

The UI for those APIs will be implemented in a later release.

TrimDerivedTables - a debug API to trigger a derived tables trim, and prunable
tables pruning.

Changed APIs:

All APIs that create a new transaction now also accept optional
messageIsPrunable or encryptedMessageIsPrunable boolean parameters (default
false). If true, the message or encrypted message attachment, if any, is
created as a prunable message.

To control whether compression is performed before the encryption or not,
the new compressMessageToEncrypt and compressMessageToEncryptToSelf parameters
can be used (default true).

Prunable messages, if not yet pruned, are also returned as part of the
transaction json by the getAccountTransactions API, using the same fields as
the corresponding regular messages, but adding a messageIsPrunable or
encryptedMessageIsPrunable boolean flag.

ReadMessage now also handles prunable message attachments, if any. It takes
an optional uncompressDecryptedMessage and uncompressDecryptedMessageToSelf
(default true) parameters, only used for non-prunable messages (not needed
for prunable ones).

DecryptFrom accepts an optional uncompressDecryptedMessage parameter, and
encryptTo accepts an optional compressMessageToEncrypt parameter, default true.

INCOMPATIBLE changes:

BroadcastTransaction has been modified to optionally accept all parameters that
are needed to create a prunable plain or encrypted message (client side
encryption only). This is required because the data for such messages is never
a part of the transaction bytes themselves, so trying to broadcast a transaction
that has a prunable part by only submitting its bytes to broadcastTransaction
WILL FAIL, unless the corresponding parameters necessary to add the prunable
parts are also supplied. Note that they need to exactly match the original
parameters with which the transaction bytes have been created and signed.

For non-prunable messages, broadcastTransaction behaves as before, but users
are encouraged to start switching to prunable messages in view of the planned
size restrictions and fee increases.

The EncryptedData java class no longer handles compression internally, this is
left to the caller of the encrypt and decrypt methods to do.

Other changes:

GetPolls now supports an optional includeFinished parameter (default false).

Multiple bugfixes and improvements in the Voting System and Phasing UI.

The limit on transaction deadline of 1440 minutes has been removed. It is now
possible to create a transaction with a deadline of up to 32767 minutes. This
has been done because many use cases of phasing require that the transaction
bytes are prepared much earlier than the actual broadcasting of the transaction
to the blockchain.

This release will perform a database upgrade with a full rescan on first start.
On testnet, it will cause a rollback to block 256935.

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

iQIcBAEBAgAGBQJVKXMXAAoJEFOhyXc7+e2ASF0QANeCGGCwaVVDi0i4YWvUVsAD
pUcy8R2NIvInbbL4dbYkfb8ZW2NaSws39hbCs7OPAGmR76JeOXRyTxyqimidGSpH
OAaupcnyEnz2bA3v/+orC8Nphaqh8HlvUffya940vn8G58y9FW5a6bnJYopB1C7x
NgE8NoUq8QnTu18zO/+KtNm7ymtAAwkCd5j25mpG9r2aalH31cf1YQ9NeKe1vO/G
qIfbOGfan0l1e08m3bzP1q71Lk/Brcioq5u6igRu1kRrdew2tg9NqcumsQN9s0YY
m1akOEpHfuAJZY2tjezOaZjRbPfr3JIBzlra7gIdSMcdA0OEFRNpb3cGqLfOQ82S
HPKoOjAQjTgDPzHmzjunFKyJiC7LFTDAtypg/Ko3bMxLghwAuWDtbwZYEptvEDzu
lhMB3UeGwrEYRsZtOVEa5fVXbqsascVtSAI/Zje+TeX+HOMfLob2rkpx1tC1jmBJ
YE6L32BfO+l4qooslgnbGFBCFHf3oyVle2bn+/2RMd6d56CvTQrpTC/pWFK2fpeO
JIPLBtkb/la/uS72AAZi7Uc9MGij+yWsJ9FZt9MKAPSXy8idYf8LcuAjFMflzXWy
ELHYz0U1yx4bciiO4Dx5raff7l1YsZ5j9+gIgo8iDP+pAw7sdU0Gv9e4zqkfyhq7
MK3oyuBnk9cGGwztb+QS
=8f8Y
-----END PGP SIGNATURE-----

Release 1.5.0e

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

Release 1.5.0e
https://nxtforum.org/nrs-releases/nrs-v1-5-0e/

sha256:
da89d5d7641b9dcfba725ad618fd5b98da39254d7bcdad129c2affcc9a3826e8  nxt-client-1.5.0e.zip

This is a development release for testing only. Source code is not provided.

Change log:

This is an experimental release for the Voting System and Phasing. It enables
these features on testnet, and is a required update for all testnet nodes.

It is also possible to run this version on main net, but the block at which the
new features will be enabled has not been set yet.

New features:

Voting System.

Voting System API calls:

CreatePoll, CastVote, GetPoll, GetPolls, GetPollResult, GetPollVote,
GetPollVotes, SearchPolls.

Polls processing is optional. If nxt.processPolls=false (default is true), vote
counting is not done and no poll results are stored. This can be used to reduce
the load on lower performance nodes. It is still possible to get the results of
a poll using getPollResult, as long as the required vote and balances data
hasn't been trimmed yet.

Regardless of the nxt.processPolls setting, votes for polls that finished
before the last trim height (1441 blocks by default) are deleted and only
aggregate results, if processing is enabled, are kept.

Votes are weighted based on the voting model selected, which can be by account,
by balance, by asset balance or by currency balance, and a minimum balance
cutoff can also be specified. The voting model is defined when the poll is
created, however a different voting model can be specified when calling the
getPollResult API, to calculate on the fly an alternative vote counting, as
long as vote data is still available.

Voting multiple times, changing, or deleting votes is not allowed.

The fee to create a poll is 10 NXT for a poll with up to 20 options, with 1 NXT
additional fee for any additional option (max 100 options are possible).

Phasing.

Phasing API calls:

ApproveTransaction, GetAccountPhasedTransactions,
GetAccountPhasedTransactionCount, GetAssetPhasedTransactions,
GetCurrencyPhasedTransactions, GetPhasingPoll, GetPhasingPolls,
GetPhasingPollVote, GetPhasingPollVotes, GetVoterPhasedTransactions.

A transaction of any type can be phased by adding a phased=true parameter and
an appropriate set of phasing parameters. Phased transactions are accepted in
the blockchain immediately (subject to all usual validations), but are executed
only at finish height, if still valid and if the required quorum has been met.
If not approved, or not valid at finish height, they remain in the blockchain
but are never executed, and any changes they caused to the sender unconfirmed
balance are reversed, except that the fee is not refunded.

In addition to the voting models available in polls, phased transactions can
use a whitelist of accounts (max 10) allowed to vote for the transaction.

It is possible to vote for (approve) up to 10 phased transactions with a single
approval transaction. This transaction will be accepted in the blockchain only
if all phased transactions it is voting for are already in it.

Voting multiple times is allowed but has no effect on vote counting, votes
after the first vote from each account are ignored.

It is also possible to make any transaction phased without needing voting for
approval. This can be used to create transactions with deferred execution.

Pay on reveal secret is supported as a voting model for phased transactions.
When this voting model is used, the phased transaction must include the
hash of a secret chosen by the sender (up to 100 bytes long), and an approval
transaction for it is only accepted if it includes the secret that results in
this hash. It does not matter who the sender of the approval transaction is,
unless a whitelist is also defined. Supported hash functions currently are
sha256, ripemd160, and sha256 followed by ripemd160. The codes to specify them
as parameters are available from the getConstants API.

Finally, it is possible to make a phased transaction that is released or
rejected not on the basis of voting, but based on the presence of other
transactions (linked transactions) in the blockchain at its finish height.
To do that, up to 10 phasingLinkedFullHash transaction hashes can be defined
when creating the phased transaction. Note that this does not create a
dependency between the linked transactions themselves. This feature can be
used to implement atomic execution of transactions of any type, provided the
phased transaction is phasing safe. Transactions already in the blockchain
before the acceptance of the phased transaction can also be linked, as long
as they are not more than 60 days old, or themselves phased transactions.

The deferred execution with no approval needed, pay on reveal secret, and
linked transactions features are currently accessible using the API only, the
UI for them will be completed in a later release.

Similar to voting, the phasing data for phased transaction that finished before
the last trim height is also deleted and only the aggregate approval results
are kept.

The fee for making a transaction phased depends on the voting model selected.
For by-account voting with no minimum balance, or no voting needed, it is 1 NXT
in addition to the regular fee for that particular transaction type. For voting
that depends on voter balances, the additional phasing fee is 20 NXT.

The fee for approving a phased transaction is 1 NXT for each phased
transaction included in the vote.

Variable size messages, encrypted messages, digital goods deliveries. After VS
block, messages and encrypted messages will be allowed to be up to 40 kbytes
long instead of 1000 bytes, with 1 NXT fee for each 1024 bytes. Digital goods
deliveries can also be up to 40 kbytes, with 1 NXT fee for each 1024 bytes
after the first 10k. A single transaction is always limited not to exceed the
maximum block payload length, currently 255 * 176 bytes.

Other new APIs:

GetOrderTrades - given an askOrder, bidOrder, or both, returns all trades that
were executed as a result of this order.

GetDGSExpiredPurchases - returns the purchases for a given seller which have
expired without being delivered.

GetDGSTagsLike - returns all Digital Goods Store tags starting with a given
(at least 2 characters long) prefix.

GetAliasesLike - returns all Aliases starting with a given (at least 2
characters long) prefix.

SearchAccounts - full text search on account info (name and description).

GetPlugins - returns a list of all installed plugins.

DumpPeers - returns all active peers of a certain version.

Shutdown - shuts down the server. Takes an optional scan parameter, if true
the derived tables are truncated and a full rescan with validation is scheduled
on next start. The resulting nxt_db folder is smaller, and a node bootstrapped
with this database is going to verify the blockchain and rebuild all derived
tables on start. While this ensures validity of the blockchain and all tables,
it cannot verify that this is the current consensus blockchain and not a fork,
therefore providing such a database for download is still not trustless.

GetLog - returns the most recent log messages, kept in a memory buffer.

GetStackTraces - returns the stack traces of the currently running threads.

Shutdown, getLog and getStackTraces require the admin password.

Changed APIs:

CreateTransaction - to facilitate debugging and to allow preparing transaction
bytes and json even for transactions that are currently invalid, if broadcast
parameter is false, all relevant transaction fields (json, bytes, hash, etc)
are still included in the result even in the case of invalid transaction.
If broadcast=true, those fields are returned only in case of successful
transaction broadcast, otherwise only the error messages are returned.
This change affects all APIs that end up creating a new transaction.

GetConstants - in addition to adding the new transaction types and subtypes,
and the voting models, the format of the resulting json has been changed.

Added optional timestamp parameter to getExchanges and getTrades.

Added optional account parameter and pagination support to getCurrencyFounders.

Always include errorCode and errorDescription in some API results that only had
an error field in case of an error.

Limit number of records returned by all APIs that support pagination to
nxt.maxAPIRecords at a time (default 100), unless the admin password is
provided or is not needed.

AddPeer adds an isNewlyAdded boolean to the returned peer json, indicating
whether the peer was not already known.

Client changes:

Extended UI in the "advanced" transaction modal dialog for every transaction
type for invoking the different variants of phased transactions (to be approved
by a certain number of accounts or balance/asset/currency holders).

New main sidebar item for the Voting System, modal to create the various types
of polls, pages to find active polls and follow polls over time, list with own
polls and votes casted.

Generic notification system for incoming transactions showing the number
of transaction types and total new transactions.

Unconfirmed transactions are only displayed in the "Dashboard" and "My Transactions"
pages and no longer appear in other tables.

Transaction info dialog for AE Bid and Ask orders now displays a table containing
the actual trades mathcing the specific order.

New account login feature for faster login just by Nxt account.

User specific client DB with new logout option to clear user data.

Streamlined sidebar/navigation structure.

Send Currency button added to the toolbar which invokes the transfer currency dialog

Environment information, client settings and various diagnostic information is logged
to the browser's JavaScript console during startup and login.

Phasing tab was added to the transaction info dialog of phased transactions.

Various bug fixes.

Client Plugin System:

Functionality - The NRS client comes with a new plugin system, enabling third
party developers to provide additional functionality for the client. Plugins
can be activated/deactivated on startup, the status of installed plugins can be
seen on a separate settings page. Plugins can hook into the new "Plugins"
sidebar navigation item or provide their own navigation structure.

Security - Plugins are not sandboxed or restricted in any way and have full
access to client functionality including the passphrase. It is essential to only
install plugins from trusted sources and in doubt don't use plugins together
with accounts storing larger amounts of NXT. There are prominent security
warnings both on the login page and within the plugins folder.

Installation - A Plugin is provided as an archived file containing the necessary
HTML/JS/CSS files and can be installed by extracting the file in the plugins/
client directory.

Developer - For a plugin to be valid is has to follow a certain minimal file
structure and be shipped with a manifest.json file with some meta information.
Detailed information can be found in the DEVELOPERS.md file in the plugins/
directory. There is also a "hello_world" example plugin to get an idea how
things work.

Other important changes:

Fixed transaction ordering in AE order matching to always be by transaction
index instead of by id, to take effect after Voting System Block.

Enforce nxt.adminPassword if set, even if the APIServer is listening on
localhost only.

Added nxt.ignorePeerAnnouncedAddress and nxt.cjdnsOnly properties, relevant
only for cjdns users or multihomed nodes.

Default initial peers are now stored in nxt.defaultPeers and
nxt.testnetDefaultPeers instead of being populated by NxtDbVersion on database
creation.

Allow the API server to handle both http and https requests on different ports,
if nxt.apiServerSSLPort is set to a port different from nxt.apiServerPort and
nxt.apiSSL=true. If the SSL and non-SSL ports are configured to be the same,
the nxt.apiSSL property determines whether SSL is used or not. On testnet,
non-SSL port is hardcoded to 6876 and SSL, if enabled, to 6877.

Reduced the default nxt.maxRollback to 800. Also added a nxt.trimFrequency
setting to control how often the trim is run, default 1000.

This release requires Java 8 and will not run or compile with Java 7.

run.bat has been updated to search for a Java 8 installation using the Windows
registry.

Updated Jetty to version 9.2.10 and Bouncy Castle to version 1.52. If unpacking
on top of a previous installation, delete the old lib folder first.

This release will perform a database upgrade with a full rescan on first start.

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

iQIcBAEBAgAGBQJVItxeAAoJEFOhyXc7+e2AGksQAJT0SolvRBp8bUPllvz4MivZ
4JirVpWQbVXaE7u3PKte3qA+UFgcaincMU1YM9YCPsHsbX9K24+fIRhblHHBoG7p
zVrqYNcE/1+uJMS0I1UFV2GDx3aFY+2lM/m4rVp8BXNGuUdNFdvAO6vW8i0bj+Ba
Rbe6Xds58YzGXZbkIuxNDnJHqlL/gBAF1q3yPuvftBx6m8nnGoOdjsVh6UDcrHTh
eeqK2hI4ZGNilwE0Coc99qIzSJi85ReE3/LANlQVac532ggVg4dK21HuB2joVtFo
wvBEcFpoeW4VdFSWWla3DRdxOOMo13OnIpIi07cWgrHH/eIG2VtZxoG3rFSyYe9s
NsVCwuV3iQxcvlU6yd4DzWprauyOKjJy0WQC0500whgJfKEZUVZeFVxlh3vLJVKN
4Jmc0cR2/hfqnpIQ6I13w8s6+UeeLnkQxmFRN9DKRICkX6PSqjejfDNjNEutCqAu
9edJ8QmVlJIUygeOjoMRZLVx4fDuxXG9UZOxu4r8DT9IfvkjX0pt5huI8uHSHIpB
tOKKV3aaELfhh2ybF7n86D+i50UAZsRUz/jSLEYfAawS6Em25hpmxk3SdRtz7Uxs
rhvD8qCyVTWeSbqtztZoUmcgWvPqDvcMqi9DTZjn2WgsoFaIBtBHzRyNjW568NYJ
9KMLLhaV6bZ6eMK3mGle
=rWe6
-----END PGP SIGNATURE-----

Release 1.4.16

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

Release 1.4.16

https://nxtforum.org/nrs-releases/nrs-v1-4-16/

sha256:
6ef76c029d96b9c689298ba1c43f561417779ac6796f94ebdff6b10a93ff871b  nxt-client-1.4.16.zip

Change log:
Updated jetty to version 9.2.9 due to a critical security bug:

http://dev.eclipse.org/mhonarc/lists/jetty-announce/msg00074.html

There are no code changes, only the jetty libraries have been updated.
Delete the old lib folder before unpacking on top of a previous installation.

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

iQIcBAEBAgAGBQJU7QUHAAoJEFOhyXc7+e2AJOAQAKkL4InI3wutmR/bTbA/NV5q
ybbndGa8gXTls41bEtJtJjfTRT2xP4huucfN7Mb9S2wSj+HPpFZkoi2QHxCH8RfP
gmPqshneOO2IYgaDhZ/pG1asBysJReGHq2dW85DiOAG9xgDn+i1GHfjktykPi0Ez
JL87uJ4lU8gfXZmtv83Bucb2GP6Zoqu7T2X+rqLb6YRrECJAD6ppS+8tqbiLgSVT
dPS4rjV67ZF3ynTVoiLeAk6ZhKwZZocPg42pQpmM1G3Yr4/BWhLGlQfIaEiKE+r+
nP1UqOoxX7CzHohb6fcwi5RM6oxQoJPtyUi3majaRuADrcZSZ4sU3HhgzPtu9YAj
rodzcrTpYlDAK3uOKDUw+YZYMapoPsJhpAbZmIx9OU//zV/JyugE8PvZf9/JMb25
kkox+ipLDfmDH/R7TD6SnSESaWsCMUKQVXtOeiopBKypLOybEb2Z0WXx0vkPqJgv
80Hh/Z/mTGEui6k9ITK/5/Q0wewzYqsx6Nyv2CzcCpShokRHXdzKiz10LtKlQvjP
yxklaKhVpEMeReuiqw35QYWWRrkszD7gePgL0yjOjhhBcAxCc0dW5aNHswWX5TXy
p/kCIYWjoJ+k7IHNztcUwQnvkdQQckaP5Y/AHBbbBibN5MerMBpWU/7cPo0/YXPI
V6s1ePALTgzO3u4O3cUC
=dL3B
-----END PGP SIGNATURE-----

Release 1.4.15

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

Release 1.4.15

https://nxtforum.org/nrs-releases/nrs-v1-4-15/

sha256:
17bd3776a5c603fc347e4e492d540d721024f540a8ee29ef40a90b1dfee1d121  nxt-client-1.4.15.zip

Change log:

Possible fix for the invalid CurrencyMint counter exception.

Made URLs in descriptions clickable and fixed potential XSS exploit problem.

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

iQIcBAEBAgAGBQJU3TEQAAoJEFOhyXc7+e2AsNoP/2yrVYakUVwY4mD/AGukhSiP
KWZt7kTtWlHuxEpSkkR39c0jucgXJqXv2I4HMyxGIPWhHpujLZxtipyxPAshT9WP
NVfgi+SOkZeQKaR5aMlEV/0w6WzDI5Jq5rlanqOnUWveS3nsldySUOA28SXryIg4
fk7UcK3DPlZfuJ4yPPuDSzhsTNkK6BywcFTHjeOMEgwkzOBlqwFlK0iKrdjICiO5
QTRrEtJyfFyXV+TIrljlbyOSksw88oH0+rvy7XUnmVW8GtlBFRpul2qyOnRE1mhC
E6UC9q211j9owkFWnJVCgDpA9QjZjdITLXaR7A+QQ/pRV4YQ4LH8FqjAxSrP+ZKe
NHVzEraPx+ocLmunObTRDiLtWsZwPr6IGrFn/2A7G5rF0o38sor8XzoahYLCD8PL
LJRf4gn8cUGmDAPRMfCIJm6CgDQ6nQFnGPQ6BNP43vH3sYmWjOXZNIs1Jf+0iXI1
5PpDjXBpYKgeQBY8yzVaKZdGc4rztaecXuRGMNn+NzuLLtY7poObpgC0CMfn5brk
kU0lWPaT41yCJY/WJ1raPbhLzZ1eroosHKKP6K08jnTbKhNDoC+iW81PgKhaxZvb
Melp10oxCIvMxrel+Ux/6W4KtK1U2SUnlYK60zvUNDhlL2V4AEhtnkkdT8ddwUrv
moff0Bs7d9TvY8PZrB+q
=74IP
-----END PGP SIGNATURE-----

---

Release 1.4.14

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

Release 1.4.14

https://nxtforum.org/nrs-releases/nrs-v1-4-14/

sha256:
dca307494ebf4053572cf02273c76e8046f352f604f834f47360274cca39a70a  nxt-client-1.4.14.zip

Change log:

Added debugging output for failing currency mint transactions.

Reduced default numberOfForkConfirmations to 2.

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

iQIcBAEBAgAGBQJU2gNRAAoJEFOhyXc7+e2A0aEP+wd1tfEvxES+K4BABhB3LyEy
rRMPK9Py2sooxzwvSYe9/2joL3xBTB4gSpWnmsnJummtquuGxiNgxmzyMow1I3wU
piot7HW/8s1RqOIsTMJyu610NzCw2uHiUKGDBAWw7Tg8TEt2AtzGkGRynsxdavIz
Q+C9a4Xk1P5WvL7UcDoFE4UWFUl52r4Xunpv/TR8zoDlnYTaTdjwkeIx3wwLc/hG
ByeBI/g80YbTSkhHZeXVFFzrsvIJqhxwlhNXM2oicFPhtl7iMBPWpMuEEXA46CcJ
xKah42+ybPEHxaSQADlOrte7nKp5BqwE2xPjdhyuyqipSqDG1d+Z+fwmKGxJ0+5G
jr4dmLTYM874OHUPU6lBnRtrE+nhtecYnHbf2WJ8cU1sIeoQycpVvYozunXhRlhR
BROeKKkRwkYsF/qW839RlCWuzs0w973B53hHFnmAjGcW93ggMmsL95J9dScSSMsI
j5VgaFvqgRwiPOrX8iKEBiRDnPgODCscNnVYp8WqAdbUSHEZyG5KahkopE/lLMCc
ZIsytrhMdvqZU1i43krEjvBPvUbLGTT2/6LTKHSXKlppJxk5NVJWpxW54avd4Xuh
iVwDzurf/5f316gVSZxOUQb8+iEfroW4GxgGf2ZeQ2S8gO40zaxnj0ipCJYgIAo/
yv10kcUVIUsM8c2WcEAB
=4/6k
-----END PGP SIGNATURE-----

---

Release 1.4.13

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

Release 1.4.13

https://nxtforum.org/nrs-releases/nrs-v1-4-13/

sha256:
58ab52f0e49e344fde5f2ba7447c43d1f3ab5ff3aaad9c93ba4900bd55ba41ed  nxt-client-1.4.13.zip

Change log:

Peer networking improvements, better logging, bugfixes.

News page now loads correctly when the wallet uses https.
Nxt forum message updates are displayed instead of new topics.
Feed refresh is performed whenever the news page is refreshed.

Minor UI bugfixes.

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

iQIcBAEBAgAGBQJU2Pk6AAoJEFOhyXc7+e2AGuwP/RCh9d+qrf0s22vPYYemmmwP
GBFbrOTeOaOrGb2ITIcPde98Ktb8ipx3lPTKb1OfKdkRO1DPRq0yz0bsZWV09emJ
4sxZaO/lcxMcX+I76qtkR/a1ASFaQqMQsDxuLx91n5QArN8GYV3ngBuGoMMkYLpT
8U2+z3fXUkXNV5Gt7YqIyLVIn9iq8zoygR6ymNeHdHCxxaQoleNKOtCsBm/ZndcQ
IKP4ixYtn0wOrxsb4PzNHdfqTuIbRlRNthHmghtnRqD2DREAjKeV8voCaBeq/LBw
p5T3q5ZfkxdmOiUApsbxnMtOsCwWP7U3c+ytcbxRjpGUUrDyfefAOwCyb1YbuB/8
vWr6eQvBbaeEk5VjqyBdzVpU0WOi8o3Ots8fJjRSAvsHcDfn6cEdFhEjJZxjIV2a
/1OGgFImbvW2yV3RSYxdjbkMuMA9ROg3vIFCIIqyrClBltnWpi6/kMNUgLRg+QIK
cg32NomEn3H86yn/Vjlnzkg7Ldz1XkaygkNYZbJHu3oTyF8LSxGJfC8xLPSYWoMZ
8v8sAAbYQ8zjUq9wYdGu7oHexC29Zgj0JHP4AIWRjHrCH5JTHAqkLejWfFFKEifE
wi1oSnteeKO8kWn64kuSI2xqst2ZfAcR2g/gtg5+2IWHKCr/+HqZyFFi3MhvyNhd
7WN3OUiMDifQLWNpzIJV
=LFnj
-----END PGP SIGNATURE-----

---

Release 1.4.12

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

Release 1.4.12

https://nxtforum.org/nrs-releases/nrs-v1-4-12/

sha256:
cbfe586bc4459efda5f973f32e0c9d8dcef222d9695092aa5b0dcab3c518ec9e  nxt-client-1.4.12.zip

Change log:

Improved fork resolution by allowing a better difficulty block pushed from a
peer to replace the current last block.

When forging, do not accept a peer block with hit time after the next hit time
of a currently forging account (i.e. prevent front-running in forging).

Removed the possibility of a forger to miss his turn. Even if late, the block
will still be generated and submitted.

Delay forging and submission of blocks by 20 s, configurable via the
nxt.forgingDelay property, in order to be able to accumulate more transactions
in the forged block. The arrival of a front-running block from a peer however
cancels that delay and the next block is generated up to 3 s earlier instead,
which can be controlled via the nxt.forgingSpeedup property.

The above time shifts apply to the physical time of block generation and
submission only. Block timestamps are always fixed by the forging algorithm
within 1 s accuracy, and are not possible to modify.

Better logging of peer networking errors. Log, but do not blacklist missing or
malformed JSON responses.

UI for adding and blacklisting peers. Blacklisting from the UI is possible
only when admin password is not needed (disabled or running on localhost).

Database optimization. Moved the public key of accounts, transaction senders,
and block forgers to a separate table, resulting in 15% reduction of total
database size. This change will be performed at first start and will take some
time. A shutdown after the first start is recommended to compact the database.

Forging API improvements: getForging and stopForging now allow access using
admin password instead of account secret phrase. This respectively retrieves
the status of, or stops the forging of, all currently forging accounts. As
with other admin password protected APIs, password is not required when the
API server is listening on the localhost interface only. The getState API now
also returns a needsAdminPassword boolean, to indicate this.

Enforce that the nxt-default.properties file used matches the version of the
current release.

Added currency distribution dialog invoked using a link from the currency
transaction info dialog.

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

iQIcBAEBAgAGBQJU0my/AAoJEFOhyXc7+e2A/XIQAPKv/A6eMhgj3enhmHA3NF9T
2lukDoxpHobcASM7PIeRlQ0Tqm62KK1Q5KxEOK35s6cQQ/xR3SCj8ONEubWT85qt
QmqlELJDX605emIdhtGIwlnj5Oyhp+V3BOH459JUZ9cMERDvDewXZRsHEq9+VinI
j884Eb8WnjUUUtIeFm3PEttjhoeqhAYdBgewSHqbv6xpkCN01j15ZUgT2vkxD2FF
qIFDFdKxA2x69gCI3zV6Pe2w1JaSSVEXuzk6CU+E9v9IjIOzGlxBpbX+/wVpCO91
g7IC8ye2rOZhQCTdmu5VrMyi3cmFQnIgtlT74A6vq7JZjdEZTB4QDW+7H932gXzR
NLvjzkCKQBUaElXiTF0JBY8cdfYnJ6QkirzMzuY5pQYPzjJ35Z1XYolTYUqrNXPx
1Lvh37sUGPV5yeIejvxqwcMtfI27IN8KMXPNuX5SFWd2+DKb5cO7dPy4GEreg8F4
xgUyQOF6qbeyWFGFk9Mc0ItiBY0YT8kEmGMHRuXd11aj4FD7ViW05yUpFHtF7sX5
s5UqTftg8P+zgYhABFD4InAvgTBDc7Ro0Mrd+ivblnW0t1nF1JTi3OX0OFwSaDZG
tNU7gZXlejtVK/PKkUAIYuS6l21DtPOnv3vwfxI7tp9ELjVlm6rxOg6J3EDu6Wdz
DqitzDULV7h3o59VXMy9
=BpAK
-----END PGP SIGNATURE-----

---

Release 1.4.11

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

Release 1.4.11

https://nxtforum.org/nrs-releases/nrs-v1-4-11/

sha256:
c821163d386304e0c5e12ad217e9d28eeb34ad79062b3fb01c772fbfe9071d46  nxt-client-1.4.11.zip

Change log:

Fixed a bug in transaction validation that could break blockchain downloading.
The default (and minimum allowed) value for nxt.maxRollback is now 1441.

Restrict maximum HTTP request and response size in peer networking to prevent
potential out of memory attacks.

Ctrl-C can now stop the server without having to wait for initial rescan to
complete.

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

iQIcBAEBAgAGBQJUx+RYAAoJEFOhyXc7+e2A5LoQAKssZLcFisGOu6PTBYdf7ELt
b1s5hUNmvJ1IIal8HBsy0ERMPDk5LEmvDOFOQ6peA3HG8uG735RICyUza7dGySko
yuGL6wOogzKR5frWAiR5HWZevqu062sBItIyejIzawdj4ms5i2GXj0K/HoHeXM5B
Kr7wmR63f1Nbe0vNA/YCQLyap4LKM4qUNLHpDrhoLpGuY+IQJ3qhB1M8jM5MnlEq
ZP/iL/uKdU2Z4SvaWiiey1sbulLXGp+9jA4utjzd2CWqR+WaREb7BXdCZ2RTs/GJ
/a6QLxu4h2KMQYN8YQfzG8QJVpinQQO4n4JjL4N1n8SGbaqUW/8TcMvX/J0O6Pvc
i2+3qjC2ZxbbP4QhXYzWu4DRwLWdqBCqWr6e0FJCNjQuGXw9cUd9N/ReEg7WRgi7
zQ3sQ/meps7fk5RRgTRH6Op7vxglu1bylDNpgYzPETlC+b7nnvq8VtxIRCTWk7Kk
uhmttaJ3XeFLUtiQTKRlvPqHfszF2H5uPU/ZRU/Mqy0i2mbmuq602Els3K0irfQ+
0xdzA5aTHYTacBOSNQa1yLFpM6vzvW3GA1v2QUXb3XGWHDzBfU56MDnPNK7y2cF7
pVtUo+M6em0vbM8Z8/tlcuEyp+7AbbZx3vKBSdu6DQVX1Ix8EE/sBUalsDoDym/R
taF8NyE2cjaTPstIgLzq
=cYXa
-----END PGP SIGNATURE-----

---

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

Release 1.4.10

https://nxtforum.org/nrs-releases/nrs-v1-4-10/

sha256:
114349601aa8bf9f700a99963677d61ce98cc7fa545295fefea7b44ed2a3beaa  nxt-client-1.4.10.zip

Change log:

Improved display of blockchain downloading status in the client UI.

Added client translations, changed state from beta to stable for the following
languages: Italian, Dutch, Ukrainian.

Fixed a bug in transaction bytes parsing which could cause signature
verification failed errors and break forging.

When downloading the blockchain, require at most one fork confirmation when
still below the last hardcoded checkpoint (currently MS block).

New API calls for peer management: addPeer and blacklistPeer. AddPeer will add
a peer address or IP, optionally with port number, to the list of known peers
and will try to connect to it. BlacklistPeer (password protected) will
blacklist a peer, for the default blacklisting period.

These APIs, and a few others related to peer networking, have been grouped under
a new Networking tab on the /test page.

Peer port handling has been improved to allow different peers to share the same
IP address provided they use different ports.

To prevent overloading a node with invalid peer addresses, the maximum total
number of known peers is limited to nxt.maxNumberOfKnownPeers (default 2000).
Once this number has been reached, new peer addresses are not added, and peers
that have been last connected to more than a week ago are removed from the known
peer list, provided the node has enough connected public peers, until the number
of known peers is again reduced to below nxt.minNumberOfKnownPeers (default
1000).

Improved database performance by storing currency supply and reserve per unit
data in a separate table.

This release will perform a rescan on first start.

Updated jetty to version 9.2.7. If unpacking on top of a previous installation,
delete your lib directory first to remove the old jetty libraries.

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

iQIcBAEBAgAGBQJUxVi8AAoJEFOhyXc7+e2AvWQP/09GHrCDnq1OrqWPVNaFDk1y
GGXsdCgp/cst4GsqozmyVAmEhhIKos60m76DsATLIpW6hPPcXXpRfDdjQWglHpxq
0Emn7AmhMozfzi/S7+yJswBlWwvFAhuhWk7/xZRukuREQAiAXx0Tw0H5bc8MX4+C
neMLEURZgAuLJfWkNDzIeQrXlETbeJz7fELUt05NerIKM3TNAEEM8zgDB4GycH+c
0IZJJ/Rvl0d7vtVNsgKhhOfk/FGJbCgiYEkHW4lHFo3tWKgqNzqFs6f6BuAoKG5l
SuubNCp8mAIOs19X5lK4bjrWCrmqo6FZfeRehVGLlY4Yxdo/f+Bk5JOZfHVOXBMU
nxUcSb/3v1aTSepfOfhKsgbLGKYYAz3ME6uIStnldpRK9B0IYb6CqBgg5fIXR3DV
KxT2fn1LI4Lg+me7q2Vt4Mi5YG1ThUP09DDleyJAk2w6g9K7EoJpx9XpOeMeTRsg
YiC1LicgL94GwX661Ou1gKi6CiuAoQwfwjuCLYJzaOWKIczCkwajbALk73y/klop
XDMI+viD/RfZlv8B4DCFiFm/bZCEEZubLFCgNnyv+uzmkmZNWCCIXP4hNmX8UP0K
C9okjSTpC3I2Fz2199pnYiiTpDssQJaA6QrykGKWhwQDa9wAj27lyFYyRBOwss6m
bB+xbrIoCEkbGQR8SnrE
=5SlO
-----END PGP SIGNATURE-----

---

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

Release 1.4.9

https://nxtforum.org/nrs-releases/nrs-v1-4-9/

sha256:
60137e4b1e3c89a3f646d979d0959cea3caecb9f76ada1a0f4f1fdd104370514  nxt-client-1.4.9.zip

Change log:

Server Logic
============
Password protect the Debug APIs. The nxt.enableDebugAPI property is no longer
used. Instead, the debug APIs which allow direct manipulation of the blockchain
database are always enabled, but are now protected with a password, which needs
to be set in the nxt.adminPassword property. Password is not required when the
API server is listening on the localhost interface only (the default).
The password protection can be disabled by setting nxt.disableAdminPassword=true.

Some refactoring to allow creation and signing of transactions using the Java API
even in the complete absence of blockchain data, as needed for the MintWorker.

Minor peer networking improvement, addPeers and processBlock requests are now
executed in the background.

Improvements in fork resolution. The peer networking getNextBlocks API no longer
limits the number of blocks returned to 1 MB total payload size, but always
returns 720 blocks, if available.

MintWorker
==========
Added nxt.mint.stopOnError property, default false. Minting will now continue,
by default, even after an error occurred when sending the mint transaction to
the server.

Minting transactions are now signed locally and sent to the server using the
broadcastTransaction API. Thus the secretPhrase for the minting account is never
sent to the server, and the server or the connection to it do not need to be
trusted. The secretPhrase is also not logged to the log output anymore.

User Interface
==============
Added second row of info boxes on Dashboard.

Notifications for incoming messages.

Reworked page navigation.

Account leasing dialog now displays the number of blocks until lease expiration.

Fixed named account links on the transaction info dialog.

Client Translation
==================
Added language selection to welcome screen.

Added translations for monetary system for different languages.

Stable: English, Spanish, French, Lithuanian, Portuguese (Brazilian), Russian,
Chinese (Simplified), Chinese (Traditional)

Beta: German, Finnish, Galician, Croatian, Indonesian, Italian, Japanese, Dutch,
Slovakian, Portuguese, Serbian (Cyrillic), Serbian (Latin), Ukrainian

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

iQIcBAEBAgAGBQJUu8LSAAoJEFOhyXc7+e2AOb8QAIe34Kf7dsEwSEA+EAyuW7cj
mszzoN+nPheRg6CbVlwBHTKXLhtUJtBsBrNZHbRtuIR2aQF8t/3oujyMDQc7LjRr
BS0dG5ikaGZYqw/yQSWKthHY/wIZS1SQwQHwDf5+YTRIRTa7oGA1M1C7ivWhiXCB
sgJUZZPdQja5UuEHi0b6cjXIBuX1zBZ4rCD2zejQeJIJcYvt+605Z5+xrABPl+Y3
qzvaOh3YZOi024/+/8aHmz5AG2snFCweAZPkDtsW8ExuCu4jL8CJG5PYIq+iDJj+
nlSUJ/S4fr6LOkdQrAytzCZjUBiurZmp6kA+9jk7mgIo5zjhXM3OlTMVhhjkaOJM
c7mwvlxN+5uu5FoTX0lgNeYmTrW5bDGKUzCUrfg5s8SEbwIECnq0YLdE9JNK8E5G
y5HnMJulFNwjgv7oXdM7sPWeBD9yNZiLaMNEKIPJQ+9CAl+e7+vSXZsKlhMCRJEr
S1QD9vUb62+YaMthcIi1SiG3tkJdcImPdFxwRtLUQDvAtefNkbf9/BG7j8NVDRbb
Knrpn16W7s1bC7gS/0s0pWf3/xstPjBuNOjJn3+w03xOKuDSmDL46vn7JhiN7uRc
nNHEbpM5m918MFEN4lweBnMJog5elZoy14QwjTSG8t7bOj3Ddu1OcYnQ4SlnjvK/
N3YXuWLvcuycZCqoaic+
=NaY8
-----END PGP SIGNATURE-----