How can I restore wallet from secret.key file from daedalus 0.15.1

[skazichris]

I got your contact from Nikola Glumac.

I understand that you're the right team to contact in terms of older cardano wallets.
Would you happen to be so kind and review the following subject?
input-output-hk/daedalus#1234 (comment)

Long story short:
There are plenty of users stuck on the 0.15.1 daedalus wallet
which suddenly stopped working and our ADA funds are stuck in it.

Your insight and help is much appreciated.

//BR, Chris

[mkr-j]

I am in a similar situation as skazichris. Looking forward to support from the dev team in restoring access to the stuck ADA coins. Re-enabling the import wallet feature to allow access through the secret.key file would be great.

Appreciate the help!

[KtorZ]

Questions for both of you @skazichris and @mkr-j:

• What operating system are you on / familiar with?
• What is your level of expertise in IT?

[mprymek]

I'm in the same situation.

• What operating system are you on / familiar with?

Linux, MacOS. Can use Windows if it's absolutely necessary :)

• What is your level of expertise in IT?

Masters degree in computer science. Basic knowledge of Haskell. Good knowledge of Python, Go, C. For me personally, a good specification of secrets.key file format and a process how to obtain private keys or a wallet phrase from it could be enough.

[KtorZ]

@mprymek have a look at: input-output-hk/cardano-sl#4278 (comment), there's a pre-compiled binary which should work on any GNU linux. This however requires that you still have access to the old wallet database AND the secret key file. The tool will extract all known encrypted keys from the keystore and spit them in a nicer JSON format.

There has been a few additions to the tools later that aren't in the pre-compiled version linked above but they are non-essential.

From there, the cardano-wallet gives you a way to import such credentials directly in the "byron-wallets" API (see the "random (xprv) tab in https://input-output-hk.github.io/cardano-wallet/api/edge/#operation/postByronWallet). Fields are named identically in the API and in the tool output. From there, your wallet should restore itself and you should be able to operate it as normal provided that you still remember the encryption passphrase. If you do not, it's hopeless.

If you do not have access to the acid-state database that the old wallet was using at the time and only have the keystore file, then let me know. I'll spend some time documenting the CDDL specification corresponding to the keystore serialization format and/or update the extraction tool to make the acid-state database optional (it's really only used to link the encrypted key to a wallet name and wallet id).

[mprymek]

Thanks a lot, @KtorZ. I think I have a backup of the acid-state db too but must find it and restore somewhere. And also recall the master password. Will take a while I'm afraid :)

[mkr-j]

Questions for both of you @skazichris and @mkr-j:

• What operating system are you on / familiar with?
• What is your level of expertise in IT?

I am on Windows. I've done some basic coding in the long past but generally am not too familiar with non-GUI operations. With some guidance, however, I'd be willing to attempt something a little more complex.

I do remember the encryption phase, but I do not see an acid-state database. My Daedalus version is 1.0.3769, wallet 0.8.2. Is the tool you referenced expected to work with this version of the wallet?

[mprymek]

@KtorZ I have some findings, probably not very good for me...

@mprymek have a look at: input-output-hk/cardano-sl#4278 (comment), there's a pre-compiled binary which should work on any GNU linux.

Sidenote: It doesn't work on "any" Linux distribution. It's dynamically linked and at least librocksdb.so.5.8 is a little bit problematic. It's not available in Ubuntu 20.04. I found it's available in Ubuntu 18.04.

I can confirm it's working on Ubuntu 18.04:

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.1 LTS
Release:	18.04
Codename:	bionic

$ ./export-wallets --mainnet   --wallet-db-path ./state-wallet-mainnet/wallet-db   --keyfile ./state-wallet-mainnet/secret.key
No wallet for id: Ae2tdPwUPEZKHDtF6psSMU99Z7HnMAgSs4T7wpbWAGdHrh1RGM8GhLd3BRq
No wallet for id: Ae2tdPwUPEZ42xY2TByWhGPQ7UST7VsopbX4KAhQRdd6o5KyS9ZJxiEMzLX
[
    {
        "encrypted_root_private_key": "f6e79f49b8999a39d7e970e42d0a91224ecacefc3aa1edb342f34eb8bc6c2fc63e743b862b312a6f92ba0161d4d53c3ee5a2bd8085476d9575765c49dceecbe54b34ec47daf9b7ebc6bdb706622616451c000e85ba81c7449ae436a8cbbf3aab98e5cc704977bd11bb0ba8d5b5571a705704cb9334d27a048532eab49a698c2d",
        "name": "亜哀うめるтУуФф",
        "passphrase_hash": "31347c387c317c5743413633702f6a487a5777575278756756344e316854793470646c6d4f76665177653863775a575472784f79773d3d7c796341722f61326f4f777a736e4e746f4e655049416e4f6b7978426549494a6b59623039574b564a7159493d"
    },
    {
        "encrypted_root_private_key": "38e8de9c583441213fe34eecc4e28265267466877ba4048e3ab1fa9956366947aefaf5ba9779db67eead7fc9cd1354b994a5d8d9cd40ab874bfeb1b33649280cd33651377731e0e59e0233425a55257782c5adaa768da0567f43c1c6c0c18766ed0a547bb34eb472c120b170a8640279832ddf18002887f03c15dea59705422d",
        "name": "WALLET 💜 💛 💚 💙",
        "passphrase_hash": null
    }
]

But i found the original Daedalus version I have a backup of, was probably older than 0.15.

Don't know if it's of any value, but anyways:

$ ls
 GPUCache         Logs          Secrets-1.0   config.json   tls
'Local Storage'   Preferences   Wallet-1.0    storage

$ cat Wallet-1.0/events.version
0.14.2

Export does not work (pre-0.15 had a different DB format?):

$ ../export-wallets-qa/export-wallets --mainnet --wallet-db-path Wallet-1.0/ --keyfile Secrets-1.0/secret.key
export-wallets: user error (There's no acid-state database matching the given path.)

$ ls Wallet-1.0/
Archive                     checkpoints-0000000071.log  events-0000057291.log  open
checkpoints-0000000070.log  checkpoints.version         events.version         open.lock

[rdlrt]

Just to add, it's probably something zendesk support should have heaps of tickets above, but we have tons of users reporting on telegramnover past few months who - do not seem to have read the warnings and have their funds locked due to missing 12 word seed.

Atleast for those that have the spending password available, it would be really helpful if there's a published way from IOG to use as a workaround (rather than someone from community passing a python/js code and asking them to run - as that involves trust, and potentially mote susceptible to scams on crypto social platforms). If only the part regarding secret.key to master key (unencrypted with spending password) is available as a method from IOG, we could easily ask users to import their wallets into Yoroi 🙂

[devilus]

Hello @KtorZ and @mprymek
I can confirm that unfortunately export-wallets-qa util doesn't works.

$ ls Secrets-1.0/
secret.key  secret.key.lock

$ ls Wallet-1.0/
Archive                     checkpoints-0000000009.log  events-0000002481.log  open
checkpoints-0000000008.log  checkpoints.version         events.version         open.lock

$ ./export-wallets --mainnet --wallet-db-path Wallet-1.0/ --keyfile Secrets-1.0/secret.key
export-wallets: user error (There's no acid-state database matching the given path.)

[clovehitch]

I'm trying to restore a wallet that was created with Daedalus 0.13.1

When using the utility I'm getting the error "user error (There's no acid-state database matching the given path.)"

I'm not %100 on what path or file I should be pointing this too. I have tried:
DB-1.0/
Wallet-1.0-acid/
Wallet-1.0-sqlite.sqlite3

@mprymek mentioned that this utility might not work with this db version. Does anyone have any more information on this?

Any help would be appreciated, thank you.

[khughes5]

I am in the same predicament.. i had my wallet in Daedalus 0.13.1 and although i can get the script to work under ubuntu 18.04 with the test data in the gzip, it seems not work with my 0.13.1 data (same as @clovehitch)

I still have 0.13.1 installed on my windows PC (it runs, just can't connect).. is upgrading to 0.15.1 (after taking a VM snapshot) to upgrade the data structure an option? i had a search around everywhere for the old installer.. but had no luck..

to be honest, this thread is the best lead i have found on this problem, and i have been looking for months! Really appreciate the assistance being given! It's hard to wait for the official import to be re-enabled (had hoped it would have been in FC3 - but no)

[testbookbear]

same error here. There's no acid-state database matching the given path
events.version file shows 0.15.0.
need to import wallet using secret.key.
Please help

[piotr-iohk]

I have just checked some old Daedalus versions: 0.13.0, 0.13.1 and 0.15.1. From what I see, in all those versions the state directory looks as follows:

~/.local/share/Daedalus/mainnet$ ls -l
total 1036
drwxrwxr-x 7 piotr piotr   4096 sty 11 09:10 DB
-rw-r--r-- 1 piotr piotr 975704 sty 11 09:10 icon_large.png
-rw-r--r-- 1 piotr piotr   4800 sty 11 09:10 icon.png
drwxrwxr-x 3 piotr piotr   4096 sty 11 09:10 Logs
-rwxr-xr-x 1 piotr piotr    880 sty 11 09:10 namespaceHelper
drwxrwxr-x 2 piotr piotr   4096 sty 11 09:10 Secrets
drwxrwxr-x 4 piotr piotr   4096 sty 11 09:10 tls
drwxrwxr-x 3 piotr piotr   4096 sty 11 09:10 Wallet-acid
-rw-r--r-- 1 piotr piotr  45056 sty 11 09:10 Wallet-sqlite.sqlite3

Where:

~/.local/share/Daedalus/mainnet/Wallet-acid$ ls -l
total 16
drwxrwxr-x 2 piotr piotr 4096 sty 11 09:34 Archive
-rw-rw-r-- 1 piotr piotr  127 sty 11 09:34 checkpoints-0000000002.log
-rw-rw-r-- 1 piotr piotr    0 sty 11 09:34 checkpoints-0000000003.log
-rw-rw-r-- 1 piotr piotr    6 sty 11 09:33 checkpoints.version
-rw-rw-r-- 1 piotr piotr    0 sty 11 09:33 events-0000000000.log
-rw-rw-r-- 1 piotr piotr    6 sty 11 09:33 events.version
-rw-rw-r-- 1 piotr piotr    0 sty 11 09:33 open.lock

I am able to run the export-wallets tool on all three Daedalus versions like this:

$ ./export-wallets --wallet-db-path ~/.local/share/Daedalus/mainnet/Wallet \
                   --keyfile ~/.local/share/Daedalus/mainnet/Secrets/secret.key \
                   --mainnet
[]

It is a bit counter-intuitive but, I think, the "rule" would be: if you have those two items in your state directory: Wallet-acid and Wallet-sqlite.sqlite3 you should point --wallet-db-path to something like /path/to/state-dir/Wallet.

Please also note that Daedalus should not be running when you use export-wallets otherwise you'll get error:

export-wallets: StateIsLocked "/home/piotr/.local/share/Daedalus/mainnet/Wallet-acid/open.lock"

[khughes5]

My Daedalus installation was on windows, would that make a difference?

My 0.13.1 directory structure looks like the following (its a copy, so date stamps are not original) :
10/01/2021 01:39 PM

.
10/01/2021 01:39 PM ..
10/01/2021 01:36 PM blob_storage
01/09/2020 12:05 PM 167 config.json
10/01/2021 01:39 PM DB-1.0
10/01/2021 01:39 PM GPUCache
10/01/2021 01:39 PM Local Storage
10/01/2021 01:39 PM Logs
01/09/2020 11:59 AM 533 Preferences
30/12/2018 01:31 PM 0 public.key
30/12/2018 01:31 PM 0 public.key.lock
10/01/2021 01:39 PM Secrets-1.0
10/01/2021 01:39 PM tls
10/01/2021 01:39 PM Wallet-1.0-acid
10/01/2021 01:39 PM Wallet-1.0-backup-2018-12-30T02_31_27
24/03/2019 09:28 PM 45,056 Wallet-1.0-sqlite.sqlite3
24/03/2019 09:04 PM webrtc_event_logs

The Wallet-1.0-acid directory contains :
10/01/2021 01:39 PM

.
10/01/2021 01:39 PM ..
10/01/2021 01:39 PM Archive
01/09/2020 12:04 PM 883,800 checkpoints-0000000737.log
01/09/2020 12:04 PM 0 checkpoints-0000000738.log
30/12/2018 01:31 PM 6 checkpoints.version
01/09/2020 12:04 PM 0 events-0001994441.log
30/12/2018 01:31 PM 6 events.version
30/12/2018 01:31 PM 0 open.lock

I have copied the files across onto a linux box now and trying to recover through there (as this is the only tool i have found so far).

I tried using "Wallet-1.0" in --wallet-db-path, with no luck.. i even tried renaming the wallet-1.0-acid and the sqlite3 file to exclude the 1.0 part trying to bring it inline with the example files but no luck there either..

Windows add/remove still shows 0.13.1 as the installed version (as does Daedalus.exe), the contents of my events.version file in Wallet-1.0-acid does show 0.15.0 though

[piotr-iohk]

Hi @khughes5, I just did the same, i.e. copied Daedalus (0.13.0) state dir from Windows to Linux:

My state directory looks as follows:

$ ls -l ~/Documents/daedalus-win/Daedalus/
total 84
drwxrwxr-x 3 piotr piotr  4096 sty 11 12:30  blob_storage
-rw-rw-r-- 1 piotr piotr    35 sty 11 12:19  config.json
drwxrwxr-x 7 piotr piotr  4096 sty 11 12:30  DB-1.0
drwxrwxr-x 2 piotr piotr  4096 sty 11 12:30  GPUCache
drwxrwxr-x 3 piotr piotr  4096 sty 11 12:30 'Local Storage'
-rw-rw-r-- 1 piotr piotr     0 sty 11 12:19  lockfile
drwxrwxr-x 3 piotr piotr  4096 sty 11 12:30  Logs
drwxrwxr-x 2 piotr piotr  4096 sty 11 12:30  Secrets-1.0
drwxrwxr-x 4 piotr piotr  4096 sty 11 12:30  tls
drwxrwxr-x 3 piotr piotr  4096 sty 11 12:33  Wallet-1.0-acid
-rw-rw-r-- 1 piotr piotr 45056 sty 11 12:19  Wallet-1.0-sqlite.sqlite3
drwxrwxr-x 2 piotr piotr  4096 sty 11 12:19  webrtc_event_logs

where:

$ ls -l ~/Documents/daedalus-win/Daedalus/Wallet-1.0-acid/
total 16
drwxrwxr-x 2 piotr piotr 4096 sty 11 12:40 Archive
-rw-rw-r-- 1 piotr piotr  127 sty 11 12:40 checkpoints-0000000004.log
-rw-rw-r-- 1 piotr piotr    0 sty 11 12:40 checkpoints-0000000005.log
-rw-rw-r-- 1 piotr piotr    6 sty 11 12:19 checkpoints.version
-rw-rw-r-- 1 piotr piotr    0 sty 11 12:29 events-0000000000.log
-rw-rw-r-- 1 piotr piotr    6 sty 11 12:19 events.version
-rw-rw-r-- 1 piotr piotr    0 sty 11 12:19 open.lock

With that I am able to run the tool like this:

$ ./export-wallets --mainnet \
--wallet-db-path ~/Documents/daedalus-win/Daedalus/Wallet-1.0 \
--keyfile ~/Documents/daedalus-win/Daedalus/Secrets-1.0/secret.key

[]

Is there any error you are seing?