NEM Beta 0.5.18

Releases
#1

Beta 0.5.18 is here!

[hr]
This release changes DB format. Initial migration might take QUITE A WHILE (14 mins on VPS), and resulting db will be twice larger
(that's due to way migrations work). So if you're running on low-power node it might be good idea, to synch from scratch, instead of making a migration

Changes:


    [li]changed handling of db blocks, and removed redundand field[/li]
    [li]fixed bug that could block harvesting (related to multisig transactions validation), KUDOS/thx to spammers[/li]
    [li]limiting node names to 128 bytes, check http://localhost:7890/node/extended-info[/li]
    [li]improved time-synching[/li]
    [li]overall in last few releases, we've addressed A LOT in code TODOs, now nis is below 20[/li]
    [li]UI changes and closed issues (doesn't mean solved ;)):

      [li]https://github.com/NewEconomyMovement/NemCommunityClient/issues/241[/li]
      [li]https://github.com/NewEconomyMovement/NemCommunityClient/issues/270[/li]
      [li]https://github.com/NewEconomyMovement/NemCommunityClient/issues/292[/li]
      [li]https://github.com/NewEconomyMovement/NemCommunityClient/issues/298[/li]
      [li]changed confirmations count display (current block == 1 confirmation)[/li]
      [li]fixed labels displaying in some places[/li]
      [li]added warning when trying to boot remote node[/li]




      [hr]

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

      [hr]

      Enjoy the new version :slight_smile:
#2

Hahaha. You put in the smiley face!!!  ;D ;D ;D ;D

#3

nice work :slight_smile: updating now…

#4

If you are using a Mac and are using the installer, please uninstall the previous version first.  If you don't when you click on the NEM icon, then 0.5.16 will still start.  Otherwise the install is going very well. 

#5

I somehow ended up with NCC on 5.16 and NIS on 5.18 with my Mac.  I got to go to work now so I'll look at it after I'm home. 

#6

I somehow ended up with NCC on 5.16 and NIS on 5.18 with my Mac.  I got to go to work now so I'll look at it after I'm home.


Once it happened to me as well but it was due that I have just overwritten the NEM folder and
that meant that 2 versions (older an newer) of the jar file were present in the same folder.
When i started the ncc (standalone) from commandline it always loaded the smaller (older) ncc version.

Check to see what is in your folder.
#7


I somehow ended up with NCC on 5.16 and NIS on 5.18 with my Mac.  I got to go to work now so I'll look at it after I'm home.


Once it happened to me as well but it was due that I have just overwritten the NEM folder and
that meant that 2 versions (older an newer) of the jar file were present in the same folder.
When i started the ncc (standalone) from commandline it always loaded the smaller (older) ncc version.

Check to see what is in your folder.



Good tips.  Not sure how to check the folders so I just did it my way. hahaha

I uninstalled NEM and then deleted the NEM folder in Mac.  I then reinstalled NEM and started it up.  I am now on 0.5.18 for both NIS and NCC and syncing a new chain.  :)
#8

I am not sure if this a bug or if I am doing something wrong

I am trying to limit harvesting to my remote harvesting account

The file /package/nis/config.properties contains this line
[code]nis.allowedHarvesterAddresses = TAWKPUE72SWHPKD3YLKY73LXXRJYB5SD2KW5RFUY[/code]

But when I try to start remote harvesting nis reports this error
[code]WARNING blocking private key request with non-configured address TAWKPUE72SWHPKD3YLKY73LXXRJYB5SD2KW5RFUY (org.nem.nis.controller.g.so validate)[/code]


Seems to be a bug, i will have to test it to confirm.
#9

We've put quite fresh db on [url=http://bob.nem.ninja]http://bob.nem.ninja

file nis5.h2_2015_03_12.zip

#10

can wait to get home to try it

#11

@jadedjack: as Jaguar pointed out in the internal irc chat, when using remote harvesting it is expecting the remote harvesting address. Since we don't expose the remote harvesting address right now in the gui you cannot use the feature when remote harvesting.

#12

Just in case I ruled out the limiting factor of RAM for Java, has returning recommended -Xms512M -Xmx1G.
Migration of db to the new format took 35 minutes on my laptop.
But later in the verify stage of the db program NIS constantly crashes.
Then I started the synchronization from scratch, removing db.
54800 blocks downloaded in 5.5 hours.
If the restart of a node, then these blocks are verified for 30 minutes.
When it restarts NIS was hung on Booting NIS… This has been once before. It curing by clearing cache of Java.
After the change of format db has lost 20%.

#13

Great work guys!

#14


@jadedjack: as Jaguar pointed out in the internal irc chat, when using remote harvesting it is expecting the remote harvesting address. Since we don't expose the remote harvesting address right now in the gui you cannot use the feature when remote harvesting.

Thanks BloodyRookie, I will limit it by the number of accounts allowed to harvest on that node
I got that address from entering a different account in the config, then clicked on start remote harvesting. I assumed the account that was denied was the address of the remote harvester


You may want to do a roundabout way to get your "shadow address" or remote harvesting address. Look at the reward and the block time, go to the explorer, and you will see a different address. That address is the "shadow address" of your account. Use that address. I remember that was the case few months ago. I am not sure if it is still the case now.
#15

You may want to do a roundabout way to get your "shadow address" or remote harvesting address. Look at the reward and the block time, go to the explorer, and you will see a different address. That address is the "shadow address" of your account. Use that address. I remember that was the case few months ago. I am not sure if it is still the case now.


There will be way to get that key inside UI before launch.
#16

for all you nembex colors' lovers, tag in name has shorcut as [c] tag

#17

three different nods after upgrade to 0.5.18 didn't harvest any blocks or catch rewards, the last block have been get 12 hours ago. "NIS is sinhronized", i try reload NIS and NCC but haven't result  :frowning:

#18

can you send me (and CC Bloodyrookie) IPs of those nodes?

#19

My Score is 0.54

#20

Can someone please send me some test nem to TBNJDU-CDRL7N-IFHDSW-PTBVM5-JWCTAX-BAD5ZG-E4J3 ?

Thanks.