-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Can't import wallet file / Electrum and Sparrow #5970
Comments
Not sure if it'd make a difference but did you follow the export instruction or just used a wallet file? BTW last I tested that, it would only import the XPUB from the wallet, read only. |
Yes of course, I followed the export instructions |
Hey @Nisaba tried to reproduce but it works as expected for me. Did you ensure you exported as electrum compatible json format? Is it a multisig or singlesig? Maybe you can send a test-wallet export? |
The files are not JSON, but encoded files. |
We have the instructions right on the import wallet page, it says you need to go to It would also work with an additional passphrase afaik. An encrypted wallet backup is something else and would be used to create a hot wallet, the above mentioned import only adds a watch-only wallet. If you want to have a hot wallet you can only do that by entering the seed words. Can you point out the docs where this is unclear so we can fix it? |
Since the backups generated by Electrum and Sparrow are not json but encoded files, so the issue comes from the password of the wallet.
-> Maybe this could be added to avoid misunderstanding... |
What is your BTCPay version?
BTCPay 1.13.1
How did you deploy BTCPay Server?
Docker
What happened?
I Get this error when I try to import wallet file generated by Electrum or Sparrow :
"Import failed, make sure you import a compatible wallet format"
How did you encounter this bug?
Select wallet file (generated by Electrum or Sparrow) then click on Continue
Relevant log output
No response
What browser do you use?
No response
Additional information
No response
Are you sure this is a bug report?
The text was updated successfully, but these errors were encountered: