-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Release 0.9.0e
http://download.nxtcrypto.org/nxt-client-0.9.0e.zipsha256: e163a575eaee40bfb001395e53b73f412cc4078a633e449281a675090b5a76c0
Change log:
This is an experimental preview release, which will only run on testnet.
It will refuse to start on main net, so don't try it there. However, all
testnet nodes should be updated to 0.9.0e, so that we can start testing
transactions with fractional NXT amounts.
All transaction amounts and fees will begin to be handled in NQT, 10^-8 NXT,
starting from the NQT_BLOCK, which for test net is set to height 63000.
When we do the transition on main net, it will be done in several steps, to
preserve compatibility with older versions, and of course not to reset the
main blockchain. This should also be tried on testnet first, so expect at
least one more reset of testnet later. But for this release on testnet,
existing assets will again be deleted, blockchain reset back to block 63000,
and fractional amounts and asset exchange enabled immediately at block 63000.
Implementation details:
Internally, all amounts are handled in NQT, using Java longs (64-bit). The
database amount and fee columns will also be converted to NQT stored as
BIGINT. This change is for both old (before NQT_BLOCK) and new transactions.
Only when verifying the signatures, old transactions and blocks are
represented in bytes using int (32-bit) instead of long amounts and fees.
For peer to peer compatibility, transaction JSON for old transactions will
contain amounts both in NQT and in NXT.
To prevent overflows, all additions and multiplications of longs are done
using precondition testing methods, Convert.safeAdd and Convert.safeMultiply,
which check for possible overflow before doing the operation.
All relevant Java APIs have been renamed to indicate that the value returned
is in NQT, except for getEffectiveBalanceNXT which is only used when forging
and there it is needed in NXT.
The http API has been changed to accept amounts either in NQT or in NXT,
with fractional amounts received as strings in the http request parameters
and then parsed directly to longs. The returned JSON objects use NQT only.
All relevant http parameter names and JSON parameters have been changed to
indicate whether they are in NQT or NXT.
Asset prices are also changed to use NQT, instead of NXT-cents. But I have
not tested asset exchange transactions at all, I have only tested simple
send money transactions, so expect bugs.
Fractional asset quantities are not yet implemented.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBAgAGBQJTPKdfAAoJEFOhyXc7+e2AOdsP/jYi8ISGS6r3AAc1Cj7IAFno
JebgFNISnuFRbLK+vVhYrZ7CKN+wi/8Hk8hEgLFVggO9uTHCIyD0tmJ9dgtMr5kQ
J+CyHUd14eEU85Z3VMyPTAap2mo2Pzfffl/oEKgrYHWpLxTnlm+p/Tl5FNvTEseU
2FT+Y6NrEMINiXQqVwSsIR2K+RB9gRCKOJ2dHct7Rgp79a0nuuBaltbGJJkdaL6Y
4u9ohAWwlqjDQxZMszE7W3/xBlAWnQyRsmjhtaRdWXWXkxsbdcrVOzAw/V5VCW2h
nBUcxgDhj3eMSOBjAIQ9eOv3ZWtrCjwiQQNmkDudX8uTC9KbBNWZZ6++OYa+Y2wc
hFg/k3OtlEeGLIVZYtrWMR28md25RfovGIiP60fHkQRxVBN9UtbcQCHjbHCYf8oi
4TkghBhHWJdd+m+f6577oJu6UGr4VzBGW92pst4m1cxj6yT2JAz8JMN/DOBJDwGZ
i9lM3ZvojLQ+pM/wICIyQSydgHSMh0saxsbTHONk7lezHeAjCMKMxgJkaYX2r/Qf
pSRMOT15pcv4nv/pwSxqmmLAWko1buH9SQRx+3LV8r2QoqPHCISu4aa6PqQfS12B
AsilS5sPzRYxoArzqCXg6FT8PV3nBAagYP80SYPHuJL0Hv/oz4VtdljG/3lkxjxv
LwmbyXNQ72KdwNwJeSXo
=atrk
-----END PGP SIGNATURE-----
