Nxt Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Nxt Client 1.11.10 - NEW RELEASE: Ardor 2.0.5e TestNet - The Ignis ICO is over!! Ardor genesis snapshots will happen at Nxt block 1,630,000 (expected for 25th December)

Pages: [1] 2 3 4  All

Author Topic: NRS v1.8.1  (Read 14928 times)

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Offline Offline
  • Posts: 1610
    • View Profile
  • Karma: +816/-81
NRS v1.8.1
April 08, 2016, 01:43:05 pm

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 1.8.1

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

sha256:

e084b628afc882a5ac3c85c8983527d398835845203ebae409b6345e31b29280  nxt-client-1.8.1.zip

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.8.1.sh

sha256:

38de94950aa4981002247147e891deeecb1404e397ebfcf99b9f159c3b16062b  nxt-client-1.8.1.sh

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.8.1.exe

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-installer-1.8.1.dmg

The exe, dmg, and sh packages must have a digital signature by "Stichting NXT".


Change log:

This is the first stable release in the 1.8 series. Please also read the 1.8.0e
changelog for all new features and changes since 1.7.5. This release does not
require a hard fork and upgrading to it is optional. It will not do a rescan
either, but once upgraded to 1.8.1, going back to older version requires
downloading the blockchain again or restoring the nxt_db folder from backup.


API enhancements:

Added getSharedKey API, to allow calculating the one-time shared key used for
encryption of messages. Parameters are the secret phrase for one of the
accounts, the other account, and the nonce used in the message encryption.

The readMessage API now also supports decryption of encrypted message parts
using the shared key, as provided by the above getSharedKey API, instead of the
secret phrase. An optional retrieve parameter is also supported to request
automatic retrieval of pruned message parts from archival nodes.

The getDGSPurchase API now supports decryption of the purchased goods, using
either the secret phrase of the buyer or seller, or the shared key from the
getSharedKey API.

The getBalance API now supports an optional height parameter to retrieve account
balance at previous heights, if still available.

The getPolls and getAllShufflings APIs now support an optional finishedOnly
parameter, to retrieve only polls or shufflings that have already completed.


Add-on framework improvements:

Add-ons can now register their own http API request handlers, allowing custom
request types to be supported. Overriding existing client APIs is not allowed.
See the example add-on nxt.addons.PopOffCounter. Such APIs must be tagged with
APITag.ADDONS and will appear under "Add-ons" on the API test page.

The add-on framework supporting custom APIs, in combination with the client-side
plugin system, present an opportunity for developers to add functionality to
the NRS without having to modify core code. Add-on developers should be aware
that the Java API in 2.0 will undergo many changes, and add-ons code will have
to be updated. And users are again reminded to only install and run add-ons
from trusted sources.


UI improvements:

Added pagination to the recent marketplace listings and recent purchases pages.

Added finished polls and finished shufflings tables under the active polls and
active shufflings respectively, with pagination. A "view" action for polls now
makes it easy to view the results of an active or finished poll.

Added full-size image display in a new modal, when clicking on an image in the
marketplace listings or purchase modal.

Other minor bugfixes and improvements.


-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXB6ZFAAoJENqvaxkWiP4ZEVwP/icRYzwyiOfe4GEV2vA0JRoL
QO6kRXvnePeDvYgSxJCMdBDMp3wVrpim1suNdVrko5QGQvXRpYXo3Qo8wY+CXeeG
x4yvaeDnMRWHzhYMhWBWHN2xwYB70OBp3ts06M7Osh6b8G19ILOg/5muJv6K2e4u
KJHklEAFU8pR8J3yYqF1CF7SFe0qMowi5EhG/UEttwvIY4KJvrfZiCFVQa81p1iR
ZC6ybaHBMlWn33A97rq0a1IX8pkSV7hc0Iq/R5lv+U9v6QPfRg4mqb0KXzqZbbxb
74bK79yA82Hr9ylrhJGRPN62Bn+RmjKDPA0neSbNgHxUQJrnLszvluBfvQWEAA/r
nB0zY0ANgMTehSakONdkanUkNZbBfY5FsGzDwGazpuXoOMBj+hmlGeQfTgCiFz7/
xAkA39MRumckJtrTYdhwrfna2IL+R7XY66jjkruNcMnMCl49OdfbtmrMBK21wSM6
FOyRsaPZ2BJB6ZmhqXANqKu+MdCQD9fBOkL+1CymqCGaTWAN0Bcra4oSfkGKj3MI
RsyXigPVw6AH+Trs98y3/E0Q/CogNC3sHG35gGBNeppvWPmyeBte/2eBANX7+sop
whgfuuM+uoaGeqUCvmiSk0erf+SyM4NY+uAS1bKkXAZHip/Dv0mxEqFZN40FevqA
/i9Nqkptsv/4pA41rmag
=CLIg
-----END PGP SIGNATURE-----
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

qq2536007339

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 493
    • View Profile
  • Karma: +41/-9
Re: NRS v1.8.1
April 08, 2016, 01:44:33 pm

Stable release now,that's quick.Thank you!
你送我未来币,我是要的。NXT-DJ68-PG7W-4JEU-2LU5T

yassin54

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 2508
  • I am Homer, Sorry my english is Bad!!
    • View Profile
  • Karma: +240/-14
« Last Edit: April 08, 2016, 04:32:02 pm by yassin54 »

EmoneyRu

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 443
  • techDevComm
    • View Profile
    • Nxt Kit
  • Karma: +30/-2
Re: NRS v1.8.1
April 08, 2016, 03:55:29 pm

I've added `.sh` to the safe nxt dowloader.
« Last Edit: April 08, 2016, 04:11:46 pm by EmoneyRu »

NxtSwe

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 658
    • View Profile
  • Karma: +123/-9
Re: NRS v1.8.1
April 08, 2016, 04:08:58 pm

Works like a charm, thanx!
Check out the NxtLib, the .NET Framework API for the Nxt platform.

sigwo

  • Full Member
  • ***
  • Offline Offline
  • Posts: 129
  • Founder, Darcrus
    • View Profile
    • Sigwo Technologies
  • Karma: +14/-0
Re: NRS v1.8.1
April 08, 2016, 04:09:20 pm

If this is official release, please update the News banner for the download link please.

NxtSwe

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 658
    • View Profile
  • Karma: +123/-9
Re: NRS v1.8.1
April 08, 2016, 05:44:16 pm

I'm curios, is it possible to explain to a non cryptographer, in what situation would the getSharedKey api be of use?
Check out the NxtLib, the .NET Framework API for the Nxt platform.

MrV777

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 979
    • View Profile
  • Karma: +112/-4
Re: NRS v1.8.1
April 08, 2016, 05:53:46 pm

I'm curios, is it possible to explain to a non cryptographer, in what situation would the getSharedKey api be of use?

I believe this was the use case that brought up the idea to create this API:
https://nxtforum.org/index.php?topic=11084.msg214459#msg214459
NXT: NXT-BK2J-ZMY4-93UY-8EM9V
NXT nodes: 209.222.98.250, 216.155.128.10

NxtSwe

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 658
    • View Profile
  • Karma: +123/-9
Re: NRS v1.8.1
April 08, 2016, 06:29:40 pm

I'm curios, is it possible to explain to a non cryptographer, in what situation would the getSharedKey api be of use?

I believe this was the use case that brought up the idea to create this API:
https://nxtforum.org/index.php?topic=11084.msg214459#msg214459
Thanx!
So, each encrypted message is using a separate "shared key" when being encrypted, even though you are using the same secret phrase.
If you want a third party to be able to read this message you could use the API to extract the shared key and give it to them without compromising your secret phrase?

Cool!
Check out the NxtLib, the .NET Framework API for the Nxt platform.

devlux

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 308
    • View Profile
    • Gemspace
  • Karma: +67/-2
Re: NRS v1.8.1
April 08, 2016, 07:20:43 pm

Excellent release!

I plan to build a business around this...
Quote
The add-on framework supporting custom APIs, in combination with the client-side
plugin system, present an opportunity for developers to add functionality to
the NRS without having to modify core code. Add-on developers should be aware
that the Java API in 2.0 will undergo many changes, and add-ons code will have
to be updated. And users are again reminded to only install and run add-ons
from trusted sources.

Will you please give me some buyin on how this is architected between now and 2.0. 
Your plugin API is a great start, but there is no sandbox, and if you're going to redo both I think it might be good to toss me that work since this is the part I can see being the most profitable and also the most mission critical.  Thus it needs to come out solid and stay solid through all of 2.x

FYI I know I come off sounding like an ass most of the time, but try to keep in mind I was raised in the wild west.  We're mostly just fact talkers where I'm from.  Jean Luc, Riker, the rest of the team, you've done good work.
Evolution NEXT D.A.C.
NXTAE:3385321989487982138 (EVOLVE)

Brangdon

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 1310
  • Quality is addictive.
    • View Profile
  • Karma: +219/-25
Re: NRS v1.8.1
April 08, 2016, 08:01:24 pm

Your plugin API is a great start, but there is no sandbox,
Isn't TestNet usable as a sandbox?
NXT-RTYD-LJXQ-EPNJ-H7AQ5. Sponsoring 1 public node at brangdon.duckdns.org.

NxtSwe

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 658
    • View Profile
  • Karma: +123/-9
Re: NRS v1.8.1
April 08, 2016, 09:02:36 pm

One question about the getBalance api, and the unconfirmedBalanceNQT property.
Is it by design that this does not contain unconfirmed balance for the recipient?

Example acc A send 1 NXT to acc B.
When calling getBalance?account=B, unconfirmedBalanceNQT remains the same as before when the tx is not included in a block.
However, when the tx is included in a block unconfirmedBalanceNQT gets the new value.
Check out the NxtLib, the .NET Framework API for the Nxt platform.

Klokan

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 273
    • View Profile
  • Karma: +28/-5
Re: NRS v1.8.1
April 09, 2016, 12:14:10 am

Is there some change with SSL handling in 1.8 series ? I used URL https://name.of.nrs.server:7876 for 1.7.5 (and every older versions), without any problems. But in 1.8.1 (with exactly the same nxt.properties config in conf/, with copied files keystore/mycerts into main nxt/ directory, etc.) Firefox (45.0.1, Fedora) kicks me out with "Secure Connection Failed" warning/error. Chromium is able to work further, but it also cries about unsecure connection ...

Each other things (means NRS "as is", listening on the port 7874/tcp) works fine...

thnx for any hints.

qq2536007339

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 493
    • View Profile
  • Karma: +41/-9
Re: NRS v1.8.1
April 09, 2016, 12:47:24 am

I forget to report a bug in 1.8.0e,I can't import contacts from browser wallet into desktop application.
你送我未来币,我是要的。NXT-DJ68-PG7W-4JEU-2LU5T

ScripterRon

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 457
    • View Profile
  • Karma: +72/-2
Re: NRS v1.8.1
April 09, 2016, 03:20:09 am

Is there some change with SSL handling in 1.8 series ? I used URL https://name.of.nrs.server:7876 for 1.7.5 (and every older versions), without any problems. But in 1.8.1 (with exactly the same nxt.properties config in conf/, with copied files keystore/mycerts into main nxt/ directory, etc.) Firefox (45.0.1, Fedora) kicks me out with "Secure Connection Failed" warning/error. Chromium is able to work further, but it also cries about unsecure connection ...

Each other things (means NRS "as is", listening on the port 7874/tcp) works fine...

thnx for any hints.
I am able to access the SSL port on my node using both Microsoft Edge and Chrome.  There is a problem in 1.8.1 when an absolute path is specified for the keystore in nxt.properties.  What did you specify for nxt.keyStorePath?
« Last Edit: April 09, 2016, 03:36:42 am by ScripterRon »
NXT-XM86-4ZNA-65L5-CDWUE

Klokan

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 273
    • View Profile
  • Karma: +28/-5
Re: NRS v1.8.1
April 09, 2016, 08:24:48 am

Is there some change with SSL handling in 1.8 series ? I used URL https://name.of.nrs.server:7876 for 1.7.5 (and every older versions), without any problems. But in 1.8.1 (with exactly the same nxt.properties config in conf/, with copied files keystore/mycerts into main nxt/ directory, etc.) Firefox (45.0.1, Fedora) kicks me out with "Secure Connection Failed" warning/error. Chromium is able to work further, but it also cries about unsecure connection ...

Each other things (means NRS "as is", listening on the port 7874/tcp) works fine...

thnx for any hints.
I am able to access the SSL port on my node using both Microsoft Edge and Chrome.  There is a problem in 1.8.1 when an absolute path is specified for the keystore in nxt.properties.  What did you specify for nxt.keyStorePath?

I have in conf/nxt.properties :

Code: [Select]
nxt.keyStorePath=keystore
So it's relative, not absolute path, I assume.

allwelder

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 1867
  • NxtChina.org
    • View Profile
    • NxtChina.org
  • Karma: +196/-13
Re: NRS v1.8.1
April 09, 2016, 11:54:11 am

Thanks ,stable version. :)
NxtChina |Weibo |Twitter Donation welcomed:NXT-APL9-66GU-K8LY-B3JJJ

JZA

  • Full Member
  • ***
  • Offline Offline
  • Posts: 147
  • Looking for the NXT big thing
    • View Profile
  • Karma: +18/-0
Re: NRS v1.8.1
April 09, 2016, 01:07:51 pm

Got error trying to install, the hash looks identical but the software reacted like the hash was invalid. I am on 1.7.5.


Anyone experienced something similar?
NXT stufff, NXT-TUAH-6PVY-S2KR-AW4RK

ScripterRon

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 457
    • View Profile
  • Karma: +72/-2
Re: NRS v1.8.1
April 09, 2016, 02:01:07 pm

Is there some change with SSL handling in 1.8 series ? I used URL https://name.of.nrs.server:7876 for 1.7.5 (and every older versions), without any problems. But in 1.8.1 (with exactly the same nxt.properties config in conf/, with copied files keystore/mycerts into main nxt/ directory, etc.) Firefox (45.0.1, Fedora) kicks me out with "Secure Connection Failed" warning/error. Chromium is able to work further, but it also cries about unsecure connection ...

Each other things (means NRS "as is", listening on the port 7874/tcp) works fine...

thnx for any hints.
I am able to access the SSL port on my node using both Microsoft Edge and Chrome.  There is a problem in 1.8.1 when an absolute path is specified for the keystore in nxt.properties.  What did you specify for nxt.keyStorePath?

I have in conf/nxt.properties :

Code: [Select]
nxt.keyStorePath=keystore
So it's relative, not absolute path, I assume.
Yes, that's a relative path.  Which means it will be prefixed with the Nxt user data directory path.  This path depends on the OS and the runtime environment mode.  If -Dnxt.runtime.mode is not specified on the java command, then the Nxt user data directory is the install directory (same as previous releases).  Otherwise, the Nxt user data directory depends on the OS and is the value returned for the user.home system property.  For Linux, this is usually /home/user-name/.nxt.  For Windows, this is usually \Users\user-name\AppData\Roaming\Nxt.  Not familiar with Mac.

Also, it sounds like your keystore is mycerts located in the keystore directory.  If so, then nxt.keyStorePath should be keystore/mycerts and not just keystore.  But that hasn't changed from previous releases, so I probably don't understand something.
NXT-XM86-4ZNA-65L5-CDWUE

Riker

  • Core Dev
  • Hero Member
  • *****
  • Offline Offline
  • Posts: 1732
    • View Profile
  • Karma: +431/-42
Re: NRS v1.8.1
April 09, 2016, 02:18:54 pm

Got error trying to install, the hash looks identical but the software reacted like the hash was invalid. I am on 1.7.5.


Anyone experienced something similar?

Did you try to install 1.8.0e ? How can I reproduce this ?
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651
Pages: [1] 2 3 4  All