Wallet import requires a passphrase #26

New Issue

spivee · 2025-09-30T15:31:34+09:00

spivee commented

2025-09-30 15:31:34 +09:00

At the moment the software quite rightly assumes that when you import a wallet, you will immediately want to open it, but the way this is currently achieved is to ask the user for a passphrase before the wallet even gets added to the menu of things they can open. Especially confusing, it asks for a passphrase whether one is needed or not, which leads some users to think that they have set a passphrase and forgotten it, when in fact there is no passphrase.

Ideally you could import a wallet just by choosing its name, and then worry about how to open it, but I am not sure how the passphrases are implemented, as to whether we want the passphrase first to check that the file contents are consistent... At the very least we should try to open the file once before we have asked the user for a passphrase.

At the moment the software quite rightly assumes that when you import a wallet, you will immediately want to open it, but the way this is currently achieved is to ask the user for a passphrase before the wallet even gets added to the menu of things they can open. Especially confusing, it asks for a passphrase whether one is needed or not, which leads some users to think that they have set a passphrase and forgotten it, when in fact there is no passphrase. Ideally you could import a wallet just by choosing its name, and _then_ worry about how to open it, but I am not sure how the passphrases are implemented, as to whether we want the passphrase first to check that the file contents are consistent... At the very least we should try to open the file once before we have asked the user for a passphrase.

spivee added the

pig lipstick

label 2025-09-30 15:31:34 +09:00

~~spivee referenced this issue 2025-09-30 15:32:43 +09:00~~

Special 'import' wizard #27

spivee referenced this issue

2025-09-30 15:35:14 +09:00

Special 'import' wizard #27

Sign in to join this conversation.