You can deactivate delegated harvesting in Nano Wallet, the supplied public key is ignored because NIS knows which account is the delegated account.
If you auto harvest on your supernode, Nano wallet can only see the correct harvesting status if you are connected to your supernode, i.e. you have chosen your supernode with the node selection popup. At least that is my understanding of nano wallet.
I asked this because i see in Nano Wallet that the
the Harvesting status is set to INACTIVE for the remote delegate account even if i’m connected to my supernode where the harvesting is active and i see
in NCC is set to active and i can deactivate it there
but in Nano i can only activate because it seems is not aware that is active.
Regarding the 2nd question i figured out that if i import the wallet that i have backed up from the NanoWallet and not the one that is saved the 1st time before login that it doesn’t akst for the upgrade.
Also i suppose the address book is not yet implemented in the NanoWallet
i can’t see there any adressess that I had in NCC.
I’m trying to migrate my wallet from NCC into NanoWallet. Everything with exporting of json file and importing into Nano login screen is clear, but when I put password and click into “Upgrade wallet”, it looks nothing happened (I’m just waiting more than 30 minutes, it couldn’t be so long, isn’t ? ).
I’m trying this process in Chromium (could it be the same as Chrome in this way?) 59, OS Fedora Linux. Any hints ? Thanks.
Just one account (with delegated harvesting into my NIS node…anyway, I’ll have to change delegate harvesting due to new public key, is it correct?). Now I’ trying the same upgrade process in FF 55 … same issue, means nothing happened after “Upgrade wallet” button click, for a long time. It’s really weird…
PS: I’m running Nano thru my local Apache, with normal http (80/tcp) port (it could be secure as it is a strictly local connection) … is this the correct way ? I saw there is also Linux desktop Nano app, but even of that, I prefer browser/web access…
PS2: all the previous versions of NCC worked in my browsers (FF, Chromium, Chrome, everything under Linux) without any troubles.
I’ve been tested this issue on another computer (also Linux based), under FF, Chromium and Chrome as well. Same issue in every cases (successful import of *.json file from NCC, then nothing happened after “Upgrade wallet” click). Really strange…
Yes if you were harvesting in NCC you need to deactivate the old remote:
Services -> Manage delegated account -> Use custom key -> Paste your old delegated public key -> Select deactivate -> Send
6 hours later you can go back to Manage delegated account page and just send an activation transaction to activate your new remote (the one shown in the grey input)
Then if harvesting was linked to a supernode you need to update the key in the NIS, enroll again with the new delegated public key and ask @BloodyRookie to deactivate the old entry here: NEM Supernode Rewards Program
Should be secure but you don’t need any local server to run Nano
Okay, strange indeed, it works here… Will look into it for v2.0
Ok, but if I don’t want (or don’t need) to run linux NanoClient and just use the html pages and *.js, probably I’ll need local webserver (e.g. Apache), is that correct? I’m thinking, if there couldn’t be a trouble, if sign-up/login doesn’t expect app hearing on some appropriate port (?)
What is more strange - I’ve been tried another way - in Nano “Sign Up”, then “Private key wallet”, then put my private key, name of wallet, pass, etc., finally clicked on “Create private key wallet”, and voilla - nothing happened. Looks like the same issue as with importing wallet (*.json) from NCC, so I’m observing (see above), if there couldn’t be some “global problem” with expecting of some another port (than default 80/tcp Apache’s one), or something like this ?
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 ?