NEM Beta 0.6.83

Releases
#1

NEM Beta 0.6.83

This release is only relevant if you have accounts that own namespaces.

##Changes:
Fixed a NIS bug that prevented NanoWallet from correctly displaying owned namespaces / mosaics in case a namespace had expired.

Usual info:
If you’re using the installer, make sure to stop running NCC and NIS before running the installer!

NEM requires Java 8
Remember the installer requires 64-bit Java
You can download Java from official page: http://java.com/en/download/manual.jsp12

You can start NCC and NIS with an installer from the following link: http://bob.nem.ninja/installer
Standalone version: http://bob.nem.ninja/

#2

Hello,

Ive updated my node last friday left it running but im getting the following errors;

2017-02-28 16:51:45.961 INFO synchronizing with Node [alice7 ] @ [104.238.161.61] (org.nem.peer.services.NodeSynchronizer b)
2017-02-28 16:51:46.929 INFO failed to synchronize with Node [alice7 ] @ [104.238.161.61]: org.nem.core.connect.FatalPeerException: remote node is evil: REMOTE_RETURNED_INVALID_HASHES (org.nem.nis.BlockChain a)
2017-02-28 16:51:46.929 INFO synchronizing with Node [alice7 ] @ [104.238.161.61] finished (org.nem.peer.services.NodeSynchronizer b)
2017-02-28 16:51:46.929 INFO Updating experience with Node [alice7 ] @ [104.238.161.61]: FAILURE (org.nem.peer.PeerNetworkState a)
2017-02-28 16:51:49.931 INFO synchronizing with Node [Hi, I am Alice2 ] @ [85.25.36.97] (org.nem.peer.services.NodeSynchronizer b)
2017-02-28 16:51:49.982 INFO failed to synchronize with Node [Hi, I am Alice2 ] @ [85.25.36.97]: org.nem.core.connect.FatalPeerException: remote node is evil: REMOTE_RETURNED_INVALID_HASHES (org.nem.nis.BlockChain a)
2017-02-28 16:51:49.982 INFO synchronizing with Node [Hi, I am Alice2 ] @ [85.25.36.97] finished (org.nem.peer.services.NodeSynchronizer b)
2017-02-28 16:51:49.982 INFO Updating experience with Node [Hi, I am Alice2 ] @ [85.25.36.97]: FAILURE (org.nem.peer.PeerNetworkState a)
2017-02-28 16:51:52.982 INFO synchronizing with Node [[c=#41ce7b]h[/c][c=#8e8e8e]ac[/c][c=#41ce7b]hi[/c] ] @ [hachi.nem.ninja] (org.nem.peer.services.NodeSynchronizer b)
2017-02-28 16:51:53.038 INFO failed to synchronize with Node [[c=#41ce7b]h[/c][c=#8e8e8e]ac[/c][c=#41ce7b]hi[/c] ] @ [hachi.nem.ninja]: org.nem.core.connect.FatalPeerException: remote node is evil: REMOTE_RETURNED_INVALID_HASHES (org.nem.nis.BlockChain a)
2017-02-28 16:51:53.038 INFO synchronizing with Node [[c=#41ce7b]h[/c][c=#8e8e8e]ac[/c][c=#41ce7b]hi[/c] ] @ [hachi.nem.ninja] finished (org.nem.peer.services.NodeSynchronizer b)
2017-02-28 16:51:53.038 INFO Updating experience with Node [[c=#41ce7b]h[/c][c=#8e8e8e]ac[/c][c=#41ce7b]hi[/c] ] @ [hachi.nem.ninja]: FAILURE (org.nem.peer.PeerNetworkState a)
2017-02-28 16:51:56.039 INFO synchronizing with Node [Hi, I am Alice3 ] @ [85.25.36.92] (org.nem.peer.services.NodeSynchronizer b)
2017-02-28 16:51:56.092 INFO failed to synchronize with Node [Hi, I am Alice3 ] @ [85.25.36.92]: org.nem.core.connect.FatalPeerException: remote node is evil: REMOTE_RETURNED_INVALID_HASHES (org.nem.nis.BlockChain a)
2017-02-28 16:51:56.092 INFO synchronizing with Node [Hi, I am Alice3 ] @ [85.25.36.92] finished (org.nem.peer.services.NodeSynchronizer b)
2017-02-28 16:51:56.092 INFO Updating experience with Node [Hi, I am Alice3 ] @ [85.25.36.92]: FAILURE (org.nem.peer.PeerNetworkState a)

So I deleted the old nem folder with the blockchain, re syncd and still the same issues, please help

#3

You will have to wait for version 0.6.84 which will be released shortly.
The log shows that your node is on a fork.

#4

Thanks for that fast reply!

#5

BR, could you specify that “shortly”, or - do you have some ETA, when 0.6.84 will be available (on mainnet) ? Thanks!

#6

Hopefully today, at least that is the plan.