Nxt Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Nxt Client 1.11.9 - NEW RELEASE: Ardor 2.0.3e TestNet IS LAUNCHED! - The Ignis ICO is currently ongoing!!

Pages: [1] 2 3  All

Author Topic: NRS v1.10.1  (Read 13005 times)

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Offline Offline
  • Posts: 1610
    • View Profile
  • Karma: +816/-81
NRS v1.10.1
August 10, 2016, 03:53:29 pm

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

Release 1.10.1

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

sha256:

fd4ac1811a7fa968356d0391988c9a08f796748324e8cb43124b7f6b0c683823  nxt-client-1.10.1.zip

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

sha256:

9b928a253227f4c68245f6b5c3fc0eea67224858100e4ad0c0317361f541c061  nxt-client-1.10.1.sh

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

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

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


Change log:

This release adds transaction replay protection, to be enabled at the hard fork
scheduled for block 1,000,000. Upgrading to 1.10.1 or later before that block
is mandatory for all.

The ecBlockId and ecBlockHeight transaction fields, previously populated but
not used, will begin to be used for enforcing that a transaction submitted on
one blockchain or fork will not be accepted on another blockchain or fork that
shares the same code. These fields by default will be set to a block 720 blocks
behind the last block at the time the transaction is created, and transactions
will only be accepted if their ecBlockId and ecBlockHeight values point to an
existing block when they are included in the blockchain. This default setting
provides protection against replaying the transaction on a hard fork that has
diverged more than 720 blocks from the one where the transaction was created.

Light clients that have no way of verifying the ecBlock values returned by a
remote node will use hardcoded values, to be updated manually at some releases.
Transactions from legacy light clients that leave eBlockId and height set to 0
will still be accepted, but cannot benefit from such replay protection.

All CreateTransaction APIs now accept additional ecBlockId and ecBlockHeight
parameters, allowing the default values to be overridden by the client.

Minor bugfixes and UI improvements.

Updated Jetty to version 9.3.11, delete the old lib folder before unpacking on
top.


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

iQIcBAEBCgAGBQJXq0cAAAoJENqvaxkWiP4ZfPAQANqR3760FscXaV0zIQ8yFLYK
muUjnHG4/vflG8HEVIe89Ujsi9EE7Kkbv6/R7GprterKFbpBMlroxon9oX0ex3xj
IOHhcJEQsrLslu8lTxhX5/ggJCkKCWnohK7w04ch1P/AJrDsbtgJoGMrhsnkUNb6
qael5Shm+/KNEfVsUVRo0NzWTOS+WyBsdpbFyiGX4lqrACe8wMS1Wz8rBcQa1hPe
SwWAUtt81PfaAbCNSXo2SA+/09Fj2UZ1I6YNwGFLVQYi+KmtppwUBGrn2BhewWhI
jrTlgff2jqGfU8EnhjGMrZpKgqtTXWGbaPqy/vOrv0kQqFfXTO8OaeuPl+CidTJO
JoHMc3HYw4e+sekAgHb/XzJAmriE0JC8JeY1ueLwaHwA+CGxdFfPHlupnMWqNe7H
djUpCZMpg0Fiy2N1KCZnGJAqjlW2US259TtkjtfiqD8XunxPyqAZ9FywU4n2mlI7
1GGwcN+ijYOnIt/F5tSMsxh6WE2DQk7zUOYpJbKhTQtr9k6+c3d9uq/6jZJDtHr7
imObpa1HrLCl9z8HefqINNDa7NXB07iNiSq/vdxaAwSH43toyrTLpeshpDKcK+9+
LkzaCJNfuyXTNlnhjoIlKtTl357rbzaJRsbW8fj3iw8pqfbTs9aPjgfklZaHxH+P
opqlEGyOAT5EqLZZCVa6
=tZIn
-----END PGP SIGNATURE-----
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

yassin54

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 2508
  • I am Homer, Sorry my english is Bad!!
    • View Profile
  • Karma: +240/-14
Re: NRS v1.10.1
August 10, 2016, 04:02:42 pm

jnsptrsn

  • Jr. Member
  • **
  • Offline Offline
  • Posts: 64
    • View Profile
  • Karma: +6/-9
Re: NRS v1.10.1
August 10, 2016, 04:10:13 pm

Thanks,

seems like it's time to renew your key:

Code: [Select]
pub   4096R/E1E4240C 2015-07-29 [expired: 2016-07-28]
uid       [ expired] Jean-Luc Picard (Lead Developer of The Nxt Generation) <jlp@secure.mailbox.org>
uid       [ expired] Jean-Luc Picard (Lead Developer of The Nxt Generation) <jlp@mailbox.org>
uid       [ expired] Jean-Luc Picard (Lead Developer of The Nxt Generation) <jlp666@yandex.ru>
« Last Edit: August 10, 2016, 04:13:53 pm by jnsptrsn »

Riker

  • Core Dev
  • Hero Member
  • *****
  • Offline Offline
  • Posts: 1715
    • View Profile
  • Karma: +430/-42
Re: NRS v1.10.1
August 10, 2016, 04:15:07 pm

Important - light clients and new nodes which still download the blockchain, may see the message "Server Connection Error No openAPI peers found" on the login screen.
These nodes, temporarely, won't be able to connect.
The reason is that in version 1.10.1 we introduced additional parameters to existing APIs. Therefore light clients are required to connect to a public node with open API running version 1.10.1 and cannot use the existing 1.9.2 nodes.
But since there are only few such nodes, users may not be able to connect.

Therefore, users running public nodes please do your best to upgrade quickly to this release.
This should be a temporary issue, once enough nodes upgrade the problem should resolve itself.
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

Riker

  • Core Dev
  • Hero Member
  • *****
  • Offline Offline
  • Posts: 1715
    • View Profile
  • Karma: +430/-42
Re: NRS v1.10.1
August 10, 2016, 04:25:01 pm

As a temporary workaround you can force your light client to connect to a node which has already been upgraded.

For example in nxt.properties add the following setting:
nxt.forceAPIProxyServerURL=https://162.243.242.8:7876

This setting should be removed as soon as enough open API nodes upgrade so that this poor node won't become the single source of data to your light client.
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

lurker10

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 1336
    • View Profile
  • Karma: +168/-33
Re: NRS v1.10.1
August 10, 2016, 04:44:27 pm

It appears that when nxt.apiServerHost is pointed to one of the two ip addresses on a vps, the API flag is not advertised in 'services' for getPeer and addPeer. The workaround is setting nxt.apiServerHost=0.0.0.0. Is this a bug or a feature?
This is the same for 1.9.2.
« Last Edit: August 10, 2016, 06:49:58 pm by lurker10 »
Run a node - win a prize! "Lucky node" project jar: NXT-8F28-EDVE-LPPX-HY4E7

shugo

  • Jr. Member
  • **
  • Offline Offline
  • Posts: 71
    • View Profile
  • Karma: +5/-0
Re: NRS v1.10.1
August 10, 2016, 05:26:22 pm

My node runs 1.9.2 on my raspberry. What do I have to do to update to 1.10.1??

lurker10

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 1336
    • View Profile
  • Karma: +168/-33
Re: NRS v1.10.1
August 10, 2016, 05:33:58 pm

My node runs 1.9.2 on my raspberry. What do I have to do to update to 1.10.1??

wget https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.10.1.zip ;
kill -15 `pidof java`;
rm -rf ./nxt.old;
mv nxt nxt.old;
unzip nxt-client-1.10.1.zip;
mv nxt.old/nxt_db nxt;
cp nxt.old/conf/nxt.properties nxt/conf/;
cd nxt; nohup ./run.sh &
« Last Edit: August 10, 2016, 05:37:24 pm by lurker10 »
Run a node - win a prize! "Lucky node" project jar: NXT-8F28-EDVE-LPPX-HY4E7

martismartis

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 1228
    • View Profile
  • Karma: +70/-10
Re: NRS v1.10.1
August 10, 2016, 05:34:23 pm

My node runs 1.9.2 on my raspberry. What do I have to do to update to 1.10.1??

1. Stop node with ctrl+c and wait until it shutdowns completely.
2. Delete "lib" directory from your nxt installation directory.
3. Download and unzip 1.10.1 over your nxt installation, overwriting all files
4. start run.sh from your terminal window.

shugo

  • Jr. Member
  • **
  • Offline Offline
  • Posts: 71
    • View Profile
  • Karma: +5/-0
Re: NRS v1.10.1
August 10, 2016, 05:51:59 pm

thanks for your help, seems to be working. the node shows 1.10.1. but i receive a lot of blocks from the future. I'll just wait until my node shows up @peerexplorer to see if it finally worked

edit: peer explorer shows 1.9.2 on the overview but if i click on my node it shows 1.10.1 - i guess it worked and peerexplorer has to update/refresh properly
« Last Edit: August 10, 2016, 06:04:54 pm by shugo »

martismartis

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 1228
    • View Profile
  • Karma: +70/-10
Re: NRS v1.10.1
August 10, 2016, 07:40:36 pm

If I am forging on a server and then stop it for upgrade, I guess I can be penalized if my server misses it's turn to generate a block? For this reason, I try to do the upgrade as quickly as possible. Do I have to restart the forging as well after an upgrade?

Yes, if you stop a node and start it again, you need to start forging again.

hob

  • Jr. Member
  • **
  • Offline Offline
  • Posts: 34
    • View Profile
  • Karma: +1/-0
Re: NRS v1.10.1
August 10, 2016, 10:05:30 pm

seems like it's time to renew your key:
It's time you refresh your copy of the key ;-)
expires: 2017-07-28

 gpg --refresh-keys 0x811D6940E1E4240C
Dump your NXTs on me ;-P  NXT-3EK4-QWSA-3MVK-H22AY

jnsptrsn

  • Jr. Member
  • **
  • Offline Offline
  • Posts: 64
    • View Profile
  • Karma: +6/-9
Re: NRS v1.10.1
August 10, 2016, 10:09:54 pm

It's time you refresh your copy of the key ;-)

Ahh, so it's that time of the year :)
Thanks!

TheWireMaster

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 342
    • View Profile
    • NXT Folks
  • Karma: +23/-0
Re: NRS v1.10.1
August 10, 2016, 10:22:25 pm

I'm getting all the time "Warning: Your passphrase will be sent to the server!"
Is that new? Or is it related to some wrong setting I have?
What about the admin password. Is there a risk not to have that?
I am running a public node.
Thanks!
NXT-5WW2-XQ63-CFGM-G7YAJ

ScripterRon

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 457
    • View Profile
  • Karma: +72/-2
Re: NRS v1.10.1
August 10, 2016, 10:48:07 pm

Yes, if you stop a node and start it again, you need to start forging again.
ScripterRon has a shell script for starting forging, see: https://nxtforum.org/general/command-line-arguments-documentation
Could this script be shared on the forum?
I run Ubuntu on Amazon Web Services (currently Ubuntu 16.04).  Nxt is installed in $HOME/nxt (/home/ubuntu/nxt) and runs under the 'ubuntu' user.  The -Dnxt.type parameter is not used by NRS - I use it to distinguish between the mainnet and testnet servers.  I use the nxt.log.lck file as an easy check to see if NRS is running.  The only drawback is you will need to manually delete this file if the NRS java vm crashes (the file is automatically deleted when NRS shuts down).

Script to start NRS (start-nxt)
Code: [Select]
#!/bin/sh
#############
# Start NRS #
#############

cd /home/ubuntu/nxt

if [ -f logs/nxt.log.lck ] ; then
  echo "NRS is already running"
  exit 1
fi

if [ -f logs/nxt.log ] ; then
  mv logs/nxt.log logs/nxt.log.bak
fi

nohup java -Dnxt.type=mainnet -Xmx784m -cp "classes:lib/*:conf" nxt.Nxt 1>/dev/null 2>&1 &
exit $?

Script to stop NRS (stop-nxt)
Code: [Select]
#!/bin/sh
#######################
# Stop the NRS server #
#######################

PID=`ps -f -u ubuntu | grep -v grep | grep nxt.type=mainnet | tr -s ' ' | cut -f 2 -d ' '`
if [ -z "$PID" ] ; then
  echo "NRS is not running"
  exit 1
fi
echo "Stopping NRS $PID"
kill $PID
exit 0

Script to display the NRS log (show-nxt)
Code: [Select]
#!/bin/sh
#########################################
# Show the last 50 lines of the NRS log #
#########################################

tail -n 50 /home/ubuntu/nxt/logs/nxt.log
exit $?


Script to compact the NRS database (compact-nxt)
Code: [Select]
#!/bin/sh
############################
# Compact the NRS database #
############################

cd /home/ubuntu/nxt

if [ -f logs/nxt.log.lck ] ; then
  echo "NRS is running"
  exit 1
fi

if [ -f logs/nxt.log ] ; then
  mv logs/nxt.log logs/nxt.log.bak
fi

java -Xmx768m -cp "classes:lib/*:conf" nxt.tools.CompactDatabase
exit $?

Script to start forging (start-forging).  You need to replace YOUR-SECRET-PHRASE with the secret phrase for the forging account.
Code: [Select]
#!/bin/sh
#################
# Start forging #
#################

SECRET='YOUR-SECRET-PHRASE'
curl --data "requestType=startForging" --data-urlencode "secretPhrase=$SECRET" http://localhost:7876/nxt
echo
exit $?
NXT-XM86-4ZNA-65L5-CDWUE

Riker

  • Core Dev
  • Hero Member
  • *****
  • Offline Offline
  • Posts: 1715
    • View Profile
  • Karma: +430/-42
Re: NRS v1.10.1
August 11, 2016, 12:10:09 pm

I'm getting all the time "Warning: Your passphrase will be sent to the server!"
Is that new? Or is it related to some wrong setting I have?
What about the admin password. Is there a risk not to have that?
I am running a public node.
Thanks!

This message should appear when you are connected to a remote node and trying to submit an action which requires sending your passphrase to the remote node, including:
Start Forging, Stop Forging, Start Shuffler, Start Monitor, Set Hallmark.
What exactly are you doing when getting this message ?
Which configuration ? Web Wallet/Desktop Wallet, Full client, light client, roaming client.
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

TheWireMaster

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 342
    • View Profile
    • NXT Folks
  • Karma: +23/-0
Re: NRS v1.10.1
August 11, 2016, 12:23:02 pm

I'm getting all the time "Warning: Your passphrase will be sent to the server!"
Is that new? Or is it related to some wrong setting I have?
What about the admin password. Is there a risk not to have that?
I am running a public node.
Thanks!

This message should appear when you are connected to a remote node and trying to submit an action which requires sending your passphrase to the remote node, including:
Start Forging, Stop Forging, Start Shuffler, Start Monitor, Set Hallmark.
What exactly are you doing when getting this message ?
Which configuration ? Web Wallet/Desktop Wallet, Full client, light client, roaming client.

I'm using the full client and it happens, for example, when starting forging.
But why do I get this warning? I guess I'm connected to my own server. Maybe the settings with hallmark and my public ip address are letting the client believe that I'm going on a remote node?
Thanks!
NXT-5WW2-XQ63-CFGM-G7YAJ

Riker

  • Core Dev
  • Hero Member
  • *****
  • Offline Offline
  • Posts: 1715
    • View Profile
  • Karma: +430/-42
Re: NRS v1.10.1
August 11, 2016, 01:23:01 pm

I'm using the full client and it happens, for example, when starting forging.
But why do I get this warning? I guess I'm connected to my own server. Maybe the settings with hallmark and my public ip address are letting the client believe that I'm going on a remote node?
Thanks!

If you connect to addresses localhost or 127.0.0.1 you won't get this message.
When using any other address we have to assume that your passphrase can be at risk when transported to the remote node or in case the remote node is hacked, therefore we warn you about this.
Use your best judgement. Setup an https connection and secure the access to your remote node.
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

ScripterRon

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 457
    • View Profile
  • Karma: +72/-2
Re: NRS v1.10.1
August 11, 2016, 02:02:25 pm

Thanks for the scripts, ScripterRon :-)
Regarding curl, it is not installed by default on Ubuntu 16.04, so I had to:
Code: [Select]
sudo apt-get update
sudo apt-get install curl
I assume that the NXT-account to forge is extracted from the secret phrase? If I have two NXT-accounts which I want to forge with on the same server, I can simply extend your script as follows:
Code: [Select]
#!/bin/sh
#################
# Start forging #
#################

SECRET1='YOUR-SECRET-PHRASE-ACCOUNT-1'
SECRET2='YOUR-SECRET-PHRASE-ACCOUNT-2'
curl --data "requestType=startForging" --data-urlencode "secretPhrase=$SECRET1" http://localhost:7876/nxt
curl --data "requestType=startForging" --data-urlencode "secretPhrase=$SECRET2" http://localhost:7876/nxt
echo
exit $?
The server update can now be automated:
Code: [Select]
./stop-nxt
wget https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.10.1.zip
rm -rf nxt/lib
unzip nxt-client-1.10.1.zip #(answer A for [A]ll)
./start-nxt
sleep 60
./start-forging
The blockchain and nxt.properties from the previous version remain in place after unzip.
Yes, the secret phrase specifies the account to be used as well as the private key used to sign generated blocks.

NRS does not stop immediately since it needs to wait for H2 to close the database.  So you need to wait before updating the code.  An easy check is to just wait until the nxt.log.lck file is removed.  Something like this:
Code: [Select]
until [ ! -f nxt/logs/nxt.log.lck ] ; do
  echo "Waiting for NRS to stop"
  sleep 15
done
NXT-XM86-4ZNA-65L5-CDWUE

TheWireMaster

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 342
    • View Profile
    • NXT Folks
  • Karma: +23/-0
Re: NRS v1.10.1
August 11, 2016, 02:25:16 pm

I'm using the full client and it happens, for example, when starting forging.
But why do I get this warning? I guess I'm connected to my own server. Maybe the settings with hallmark and my public ip address are letting the client believe that I'm going on a remote node?
Thanks!

If you connect to addresses localhost or 127.0.0.1 you won't get this message.
When using any other address we have to assume that your passphrase can be at risk when transported to the remote node or in case the remote node is hacked, therefore we warn you about this.
Use your best judgement. Setup an https connection and secure the access to your remote node.

Hi Riker
I actually am connected to my localhost (http://localhost:7876/index.html)
But it looks like it's related to the settings I've changed to make my node a public node. When I go back to the default settings then I don't have those warnings.
This is the diff between the original and my properties file:
"
61c61
< nxt.myAddress=
---
> nxt.myAddress=mypublicIPaddress
67c67
< nxt.myHallmark=
---
> nxt.myHallmark=3dc6529a.............ba4a9359afc5ddd9ce
234c234
< nxt.allowedBotHosts=127.0.0.1; localhost; [0:0:0:0:0:0:0:1];
---
> nxt.allowedBotHosts=*
244c244
< nxt.enableAPIUPnP=false
---
> nxt.enableAPIUPnP=true
249c249
< nxt.apiServerHost=127.0.0.1
---
> nxt.apiServerHost=0.0.0.0
365c365
< nxt.allowedUserHosts=127.0.0.1; localhost; [0:0:0:0:0:0:0:1];
---
> nxt.allowedUserHosts=127.0.0.1; localhost; mypublicipaddress; [0:0:0:0:0:0:0:1];
"

Also with the modified properties file when I pass over the "Forging" status I get a message: "Cannot determine forging status, please define administrator password".

Does this make sense to you?

thanks

NXT-5WW2-XQ63-CFGM-G7YAJ
Pages: [1] 2 3  All