Beta 0.5.4 is here!
[hr]
Everyone who is actively following, probably knows this, but here it goes.
Changes:
[li]Address book[/li]
[li]Multisig[/li]
[li]experimental anti-spam[/li]
[li]LOTS of internal changes[/li]
Bump in minor version means that hosts using 0.5 won't talk with previous nodes.
Before proceeding you should drop previous database
Under windows you can drop whole [tt]c:\users<i><username>\nem\nis[/tt]
The old accounts will be empty, so you might want to drop ncc too
Under windows you can drop whole [tt]c:\users<i><username>\nem\ncc[/tt]
Or to be sure you can drop whole [tt]c:\users<i><username>\nem[/tt]
There is small bug with display of multisig transactions:
http://i.imgur.com/9oFA9w3.png
Please forgive us this tiny imperfection, webstart was giving us hell lot of problems.
Actually it got us so frustrated, we're considering getting rid of it, and providing an installer…
btw, 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 pat):
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
