Unable to create legacy wallet, or connect to an existing legacy wallet from a ledger device

[Voll3r]

In principle, the current version of Neon seems to be able to handle legacy wallets just fine. For example, it is possible to import a legacy wallet from an encrypted key, or to set up a watch account for a legacy wallet from a public key.

What does not seem to be possible, however, is to:

1. Create a new wallet that functions as a legacy wallet
2. Connect a legacy wallet from a ledger

Hoping this functionality can be added

Thanks!
Matt

[thiagocbalducci]

Hi @Voll3r, thank you for reaching us with your question, I will do my best to help :)

1 - You are able to create a legacy account, once you go through our onboarding process and has already set a password for your NEON Account, navigate to "Wallets" menu option, you should see an "Add Account" button, when you click it, it is just a matter of giving it a name and thenselecting Neo Legacy to create your Legacy account in your currently selected wallet.

2 - That is correct, right now we don't have support for Neo Legacy Ledger App, but we are looking into the possibility of adding it.

I'm also attaching a couple screenshots that might help with item 1

[Voll3r]

Hi @thiagocbalducci,

thanks for clarifying. I have been able to add a legacy wallet as per point 1 as you have described. Since I had already deleted "My first wallet" after the onboarding, the step of adding an account as opposed to a wallet hadn't occurred to me.

I guess what is a little confusing is that adding anything other than an N3 type of account would first require a wallet to be created. Any wallet that is created via onboarding or the "add wallet" option will by default add an N3 account to it - whether it is required by the user or not. Without creating such a wallet first, the option to "add account" and the subsequent choice of what type of account to add does not become available to the user.

In principle, the N3 account can be deleted from the wallet afterwards, so the Neon interface is perfectly capable of having a wallet with only a non-N3 account in it.

I will leave this as a suggestion: creating a new wallet - whether through the onboarding or through the main UI - should already prompt the user to specify the type of account they wish to add. It should not create an N3 account by default. The UI for this already exists in principle:

That way the user has complete freedom as to when to create the wallet and the desired account type. I would also say that such an approach would be more intuitive, because it doesn't require the user to first create an N3 account that they may have no use for and that is otherwise not required either.