NEM Beta 0.6.87


#1

NEM Beta 0.6.87

##There will be a fork at height 1110000 (which is roughly May 15th).

##Changes:
More protection for users unintentionally hurting themselves.
Details will be announced once we pass the fork height.

This upgrade is mandatory.

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

Thanks BloodyRookie.

On the supernode, is it just a matter of extracting the jar files from nis-ncc-0.6.87.tgz and replacing them.from nis, ncc, console and mon folders into respective supernode folders

i.e. to
nis-ncc/package/nis
nis-ncc/package/ncc
nis-ncc/package/console
nis-ncc/package/mon

Or does the libs folder jar files also need to be replaced?


#3

For a supernode, only nis matters and only those jars have to be updated (and nis needs to be restarted)


#4

Thanks BR. Appreciate your help as always.


#5

It is currently impossible to verify the sha of the downloaded file because the transaction ID published in the .sig file is incorrect. Can someone please fix that?


#6

why do you think the id is incorrect?


#7
$ curl http://bob.nem.ninja/nis-ncc-0.6.87.tgz.sig
txId: e6efac6b3f2dc109aa0a9e8fd4925a2308291b0e9a7976358c3913dc9e9c5
block: 1072404

$ curl http://bigalice3.nem.ninja:7890/transaction/get?hash=e6efac6b3f2dc109aa0a9e8fd4925a2308291b0e9a7976358c3913dc9e9c5
{"timeStamp":65122815,"error":"Bad Request","message":"Hash was not found in cache","status":400}

As you noted yesterday when I first reported it, the whole hash should be passed:

$ curl http://bigalice3.nem.ninja:7890/transaction/get?hash=f5ae6efac6b3f2dc109aa0a9e8fd4925a2308291b0e9a7976358c3913dc9e9c5
{"meta":{"innerHash":{},"id":695744,"hash":{"data":"f5ae6efac6b3f2dc109aa0a9e8fd4925a2308291b0e9a7976358c3913dc9e9c5"},"height":1072404},"transaction":{"timeStamp":64947828,"amount":0,"signature":"271dcaa5e55c8f6463c73e44a5ecd9b6b4751205ede36f95c8fe3c911a56acf6b52bb114a11fe82f052eaae1c4073084284f8396dc7f45803501168bc5ed6108","fee":3000000,"recipient":"NCZSJHLTIMESERVBVKOW6US64YDZG2PFGQCSV23J","type":257,"deadline":64951428,"message":{"payload":"fe4e5459031168167aacc0a4e7c7ebd5ae4162e8a841ba4e64a5bba197f5147ef6119d5e76","type":1},"version":1744830465,"signer":"826cedee421ff66e708858c17815fcd831a4bb68e3d8956299334e9e24380ba8"}}

#8

txId: 5bfe2979482cd9b5fa80de45c6d3a7bf18531aa63cde9a62d2696fcf863802a4
block: 1072404
in the sig file i have

Edit: oh you mean the tgz sig file


#9

i told @gimre

Edit: file was updated


#10

Thanks. nem-docker builds again.

I also published an experimental (use at your own risk!) ubuntu repo. See details at https://github.com/rb2nem/nem-nis-apt/blob/master/README.md


#11

@rb2
Good job!
Would you consider to include the servant into the Ubuntu repo? Then, it can become a supernode by itself :slight_smile:


#12

If there is enough interest I might have a look :slight_smile:


#13

OK. me +1 … :sunglasses:


#14

So im good if im just using the nano wallet? this java update only goes for people using the actual installation version and not the nano wallet version with the start file that i didnt have to install?


#15

Yes, if you only use nano wallet then you don’t need to update anything.


#16

awesome thanks and that was a fast reply.lol


#17

So we pass fork height.

Any details?


#18

Fork details:

1) Fix for mosaics:
A mosaic creator could accidentally kill his mosaics by issuing a new definition where only the description is changed.
The handling of such a transaction was fixed and the mosaics are there again after the fork kicks in.

2) Fix for remote account.
A user could accidentally block his main account by supplying the main accounts public key when deactivating local harvesting.
The main account will be unblocked after the fork kicks in.


#19

Hello, I’ve been using Nem via the NIS / NCC .tgz client, but I haven’t ran the runmod file (I think this is the right name) since the hard fork. Do I need to do anything now or can I boot NIS / NCC and use my .wlt wallet file as per usual? Or do I need to download a new .tgz NIS / NCC client now?

I’ve never had the .json file or used nano wallet, just have my .wlt and .abd files backed up along with password etc. in multiple locations. Is this safe?

Do I need to do anything else to upgrade?

Thank you.


#20

If you want to continue using NIC / NCC then you must update both. There is no way around that.
The new client can be found here Standalone client.