@suky321 based on tutorial Nano Wallet Beta 2.0.14 - Mandatory update - Bug bounty paid in XEM
"III - Imported accounts that are already harvesting using NCC
NCC is using a different way to generate the remote associated with an account. Nano Wallet uses BIP32 to generate it deterministically and make everything easier. In order to manage and monitor harvesting, you’ll need to deactivate the old remote account from NCC and activate your new remote account from Nano."
Nanowallet use new (different) delegated account and you must deactivate old. You can do this from NCC (as is described above) or you can click “Use a custom public key”, put your old account from NCC in field “remote public key” and next deactivate harvesting (select a mode deactivate). If you already deactivated old remote account from NCC it’s not necessary.
Node (Ip address) from which you want to harvest (your current supernode) need to be put in section “Start / Stop delegated harvesting”.
Summarizing what you need to do is:
- deactivate old delegated account (from NCC or using the option “use a custom public key”). Option from NCC is described in tutorial that’s why I think you should try it first (if you have NCC configured)
- activate the new delegated account from Nanowallet. It requires 6h to activate.
- put your supernode in section “Start/Stop delegated harvesting” and start harvesting.
I’m not sure if what I describe above answers your questions.
@Saul please confirm my explanations.