Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Data Backup does not restore Bitcoin Core hot wallet.
See original GitHub issueUsing a brand new Specter 1.0.0 (via getumbrel.com), I loaded the data backup files from my other node and it appeared to successfully restore all devices and wallet onto the node.
When attempting a simple roundtrip transaction using a 2-of-3, I discovered the following issue.
When signing with the newly restored hot wallet, the following error was surfaced:
Failed to sign PSBT: Request error: Requested wallet does not exist or is not loaded.
My best guess is that Specter restores the metadata, but does not check for hot wallets within, and therefor does not reinitialize those wallets inside Bitcoin Core. This causes the wallet to feel restored, but otherwords be orphaned.
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
As long as the extra fields to the format are optional I don’t see any issues adding them. Not sure if you should require adding the mnemonic for the hot wallet import, I think just warning that otherwise it’ll be watch only is fine.
Thanks, yes that’d definitely make sense. The whole backup and flow of the hot wallet functionality could be improved quite a bit, so would be great if you could do that.