Background
Some years in the past (2017) I should have discovered a option to ‘serialise’ my pockets, as a result of I saved the next in my password supervisor:
- Title: “Bitcoin pockets”
- Password: (typical generated password)
- Technology seed: (typical passphrase, e.g. checklist of random phrases)
- Receiving deal with: (typical bitcoin deal with)
- Notes: (seems to be like base64 knowledge, about 3000 characters in size)
I vaguely bear in mind having the Bitcoin-Qt consumer put in.
Query
What technique did I exploit to serialise (or export, or back-up) my pockets in 2017?
Additional info
What I attempted up to now:
- Copied the info to textual content file
- Ran bitcoin-cli importwallet “/path/to/file.txt” (by way of Bitcoin-Qt’s console). Obtained the error “Solely legacy wallets are supported by this command (code -4)”.
- Decoded the textual content file utilizing
cat /path/to/file.txt > base64 -d > /path/to/file.datand ran bitcoin-cli importwallet “/path/to/file.dat”. Obtained the error “Solely legacy wallets are supported by this command (code -4)”. - In Bitcoin-Qt chosen File, Restore Pockets…, and chosen the .dat file. Obtained “Pockets file verification failed. Did not load database path ‘~/Library/Utility Assist/Bitcoin/wallets/Take a look at’. Information shouldn’t be in acknowledged format.”
- Ran
file /path/to/file.datand boughtfile.dat: knowledge(I hoped it might be recognized as Berkeley DB, since I learn right here that pockets.dat information are BerkeleyDB database information). - Checked the hyperlinks within the reply to this query in regards to the ‘pockets export’ format, but it surely seems to be like that’s only a option to encode a personal key, which might not end result within the sort of knowledge I’ve saved in my password supervisor.
What I didn’t do but:
- Set up the model of Bitcoin-Qt present in 2017, and try to revive the .dat file.
