NEM Beta 0.5.5


#1

Beta 0.5.5 is here!

This is minor release to fix some of the issues.
Changes:
UI improvements
fixed bug that could lead to fork (people stuck at block 3700 have to delete their db and resync)
fixed bug in transaction anti-spam (thanks to spammers)
Closed issues (doesn't mean solved ;)):
https://github.com/NewEconomyMovement/NemCommunityClient/issues/236
https://github.com/NewEconomyMovement/NemCommunityClient/issues/237
https://github.com/NewEconomyMovement/NemCommunityClient/issues/239
https://github.com/NewEconomyMovement/NemCommunityClient/issues/234
https://github.com/NewEconomyMovement/NemCommunityClient/issues/249
https://github.com/NewEconomyMovement/NemCommunityClient/issues/250
https://github.com/NewEconomyMovement/NemCommunityClient/issues/251
https://github.com/NewEconomyMovement/NemCommunityClient/issues/256
There's a good reason to try standalone instead of webstart - it starts a lot faster


Some hints for multi-sig
If you convert an account into a multi-sig account that account will from that point on only act as a "storage". You can't issue tx from that account directly anymore - only from it's cosignatories.

DO NOT set the multisig account as cosignatory of itself. Since multisig account can't issue any transactions it will also NOT be able to cosign any transactions, therefore will yield the funds UNTOUCHABLE.

Quick Example (via pestmaster):

You have a lot of NEM and you're afraid your girl is spending all your NEM on shoes again. So you want to set up a multi-sig account so that you will have to sign every tx your girlfriend makes.
For this purpose you create a new account A and convert it to a multi-sig account. As co-signatories you set an account controlled by you (B) and your girlfriends account ©.
When that process is completed B and C will be able to spend NEMs from A but only when the other party also signs the tx.

Remember this is just the first iteration of multi-sig so more flexibility will be added in the future. For example right now all keys are needed to sign a tx. In the future we might have multi-sig accounts that only require a subset of all co-signatories to sign. 

[hr]

NEM requires Java 8
You can start NCC and NIS with the following link:
http://bob.nem.ninja/webstart/
Alternatively, you could just shutdown and restart NEM monitor by double-clicking the NEM icon on the desktop.
Standalone version: http://bob.nem.ninja/
[hr]

Usual Troubleshooting Guide:


    [li]Standalone - shouldn't have issues with this release.[/li]
    [li]Webstart,

      [li]kill any running jawa/jawaws processes[/li]
      [li]Go to java control panel, and hit "View…" (can be run with javaws -viewer)

        [li]from "applications" remove both NCC and NIS[/li]
        [li]to be sure check resources and clean them all (this will cause redownload of everything, which might take a bit,
        but should help with most of the problems)[/li]
        [/li]
        [li]There is a detailed post on how to remove the NEM software prior to installing the new version in the ournem forum:
        https://forum.ournem.com/index.php?topic=2635.msg8834#msg8834[/li]
        [li]If you end up on a fork, go to c:\users<i><username>\nem\nis and delete data subdirectory[/li]
        [/li]


        As most of you know, this is probably last testnem release.

        Enjoy the new version :slight_smile:

#2

Starts a lot faster!

It shows this for importance score 0.77%o, there is an extra o after the %


#3

Starts a lot faster!

It shows this for importance score 0.77%o, there is an extra o after the %


We switched it to http://en.wikipedia.org/wiki/Per_mille

There are 160 50M accounts IIRC, so standard value for a fully vested account should be around 6,25

#4


Starts a lot faster!

It shows this for importance score 0.77%o, there is an extra o after the %


We switched it to http://en.wikipedia.org/wiki/Per_mille

There are 160 50M accounts IIRC, so standard value for a fully vested account should be around 6,25

#5

nice job devs. :smiley: very fast turn around.


#6

that's cool and something different to see in a client, good work.


it's not unified yet, so in some places percentages will probably show up.

#7

This version started up a lot faster for me than 0.5.4

Does the Nem network crawler work still?

Previously I showed up on it, but now don't - just wondered  (my router has its ports open)


#8

I seem to be stuck on block 5702 when synchronising


#9

Second thoughts:

The blocks don't get loaded now until the client starts? Have restarted NIS a couple of times now and it always starts at around block 4000 ish(looks like it loads blocks earlier then that) even though when I shutdown NIS I am fully synced so to become fully synced takes longer.


#10

Second thoughts:

The blocks don't get loaded now until the client starts? Have restarted NIS a couple of times now and it always starts at around block [s]4000[/s] ish(looks like it loads blocks earlier then that) even though when I shutdown NIS I am fully synced so to become fully synced takes longer.


We've added delayed loading, in ui it looks as follows. So nis tries to start as fast as possible. And then it loads blocks.

[img width=800 height=289]http://i.imgur.com/mjZED3g.png[/img]

#11

Beta 0.5.5 is here!

DO NOT set the multisig account as cosignatory of itself. Since multisig account can't issue any transactions it will also NOT be able to cosign any transactions, therefore will yield the funds UNTOUCHABLE.



This really should be disabled (at least) by client otherwise some people will loose their NEM and it will be bad PR
(like when nxt lacked check-sum on sending addresses which resulted in creating losts of "darkNXT")
what CAN happen WILL happen ...

#12

this is strange…the client is synching but very slowly…5702…more than an hour…5703…more than an hour…5704…anybody any idea ?


#13


Beta 0.5.5 is here!

DO NOT set the multisig account as cosignatory of itself. Since multisig account can't issue any transactions it will also NOT be able to cosign any transactions, therefore will yield the funds UNTOUCHABLE.



This really should be disabled (at least) by client otherwise some people will loose their NEM and it will be bad PR
(like when nxt lacked check-sum on sending addresses which resulted in creating losts of "darkNXT")
what CAN happen WILL happen ...

+1

#14

We've added delayed loading, in ui it looks as follows. So nis tries to start as fast as possible. And then it loads blocks.

First I thought: Hell yeah! Now I can fire up NIS and NCC on the cubie, log into the wallet and leave.
But no, its not possible to log in until the block analysis (in the GUI its called "Loading blocks from db, at block: xyz") is done:
"ERROR 602

Cannot perform any operations until db is fully loaded."

Isn't it possible to log in while the analysis is going on and maybe even start harvesting in the GUI (it will in fact start after analysis is done), but for a cubie node this would be so much better!

#15

ok…deleted data…started synchronisation again…hardly any delays until block 5670…seems to hit a brick wall here…any reason why ?


#16

Avast anti-virus seems to be having a hissy fit lately. Did it on the last version as well as this one.

I've got enough faith in you guys that it's not malicious :P. But any idea on a fix other then telling avast to make an exception? Don't want average jo to be getting all upset if their antivirus starts reporting false positives. Crypto's got a dodgey enough rep as it is :stuck_out_tongue:


#17

Avast anti-virus seems to be having a hissy fit lately. Did it on the last version as well as this one.

Which file triggers the false positive?

https://www.virustotal.com/en/file/b72b22fc2e0a700a6bfe47cb3aeb56479e19bd5a51613907df3bbdbff703acab/analysis/1423494379/
https://www.virustotal.com/en/file/26952857eefce5bdd5d1e846ae2f24c41143ebb64401aa00d7860819c1cb7ed7/analysis/1423494400/
https://www.virustotal.com/en/file/683897173d446e877e115593088ee5223ecded2283f50250435559de040d87c8/analysis/1423494425/
https://www.virustotal.com/en/file/ba7679e32811f3867e9b3b2ffbd207b9cddc44290554fce25f434cc6ae8abb42/analysis/1423494469/
https://www.virustotal.com/en/file/3973bd3b5761f6852037ef49d5576c9f1538e6d5b40611616cabb715dced0648/analysis/1423494501/

#18

my node isnt autobooting even though iv sorted out the config files…


# NIS configuration
nis.bootKey = 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef
nis.bootName = kodtycoon


in the settings above i removed the hashes… but even after doing this it wont autoboot… am i missing a setting somewhere? i couldnt see anything else…

#19

my node isnt autobooting even though iv sorted out the config files..


# NIS configuration
nis.bootKey = 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef
nis.bootName = kodtycoon


in the settings above i removed the hashes.. but even after doing this it wont autoboot.. am i missing a setting somewhere? i couldnt see anything else..
Did you try to put # in front of your key?

#20


my node isnt autobooting even though iv sorted out the config files..


# NIS configuration
nis.bootKey = 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef
nis.bootName = kodtycoon


in the settings above i removed the hashes.. but even after doing this it wont autoboot.. am i missing a setting somewhere? i couldnt see anything else..
Did you try to put # in front of your key?


ya no i didnt need to ... just needed to be a little patient.. ha :)