NEM Wallet Beta 2.4.4 - Bug bounty paid in XEM

Releases
#242

@jelin1984 You can try to follow this https://blog.nem.io/ncc-to-nanowallet-export/. Upgrade works for me, should work for you too.

@KloNEM No need for a local webserver, you can click on start.html and it will open in your browser. Everything is client side, it does not expect any port or else for creating wallets.

Are you using latest version ? Can you open the browser console, try to create a private key wallet and look if you see any red error message.

Don’t paste console content here, send it to me via PM.

#243

kindly remind :slight_smile:

#244

Hi Team. @Saul
The download page is still ver1.4.3.
Please update to the current latest.

https://nem.io/install.html

#245

Eh, my fault! I really don’t know, why I was expected, that Nano has to be running over TCP/IP / webserver, and not just “as local files”. So, I did it by this way, click on “Upgrade wallet” and everything is running smoothly and fine now. Thanks and sorry again!

Just a question - also in this case (“Upgrade JSON/existing NCC wallet”) I have to deactivate delegated harvesting in old NCC and (after 6 hours) just do activation in “Manage delegated account” in Nano ?

#246

There is now a 5,000 XEM bounty for issues reported to QM’s Github.

Any bounties for bugs in the Android wallet?

#247

Version 1.4.13

  • Allow sub-namespaces and mosaic names to start with a number
  • Fix secondary accounts: In occasional cases, secondary accounts private keys can start with ‘00’ but BIP32 was omitting it, giving a 62 characters private key. Those secondary accounts will fail to send anything out even if password is valid (but recoverable).
  • Update languages
#248

Yeah, you can also deactivate the old remote account from Nano directly by providing it’s public key

#249

New bug bounty system is posted on the website https://nem.io/developers/developer-bounties/.

#250

I´m supprised. In the new Version 1.4.13 (simple Wallet) we can read " It is still recommended to use a private key generated from a NEM client (NCC). " . The NCC support has expired.
Should we change it in the next version?

#251

Where was the document recommending the secret key of NCC?
Basically, there is a problem with using BrainWallet with NanoWallet.
In the latest NanoWallet, when using BrainWallet, you can not register unless the password has a certain degree of complexity or more.
Also, if you are using a weak password in BrainWallet, you will now get a warning.

thanks

#252

When I start the universal client —> Sign up —> Simple Wallet .

#253

Oh, lol
There is no problem as long as you use Simple Wallet.
I will fix this document.

#254

Yep, but for some new user maybe it´s a bit strange with the good old NCC.

1 Like
#255

Is bounty program actual?

#256

Is this update mandatory like the last one?

Thanks.

#257

Not mandatory, no. The last one was not mandatory either.
You just won’t be able to get the benfits of the improvements, and you will be paying higher fees.

#258

Thank you Saul.

#259

Just a question, is it possible to open .wlt without password? if someone hacks the .wlt file they still need the password?

#260

Yes, that is correct.

#261

So far have not had any issues, but now I know where to post if I start getting any bugs! Great job guys!

1 Like