Как открыть файл secret key кошелька daedalus

Saved searches

Use saved searches to filter your results more quickly

Cancel Create saved search

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

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

How can I restore wallet from secret.key file? #1234

yuelipeng opened this issue Dec 20, 2018 · 385 comments

How can I restore wallet from secret.key file? #1234

yuelipeng opened this issue Dec 20, 2018 · 385 comments
feature-request release-3.3.0-FC1 Daedalus Flight release-3.3.0 Daedalus Mainnet

Comments

yuelipeng commented Dec 20, 2018

when i heard 0.12 version has low disk usage, i just copy my secret.key out, i thought it is the keystore like ethereum. then i delete the old 0.11.2 version’s daedalus folder。 when i finished sync of 0.12, i copy secret.key into Secrets-1.0 folder, it can’t identify.

i lost my 12 words phase unfortunately。so how can i restore wallet from secret.key file, please.

The text was updated successfully, but these errors were encountered:

Contributor
nikolaglumac commented Dec 20, 2018

@yuelipeng I have originally posted wrong links to the previous Daedalus installers — please use the ones from my comment which I have now updated. Thanks!

yuelipeng commented Dec 21, 2018

i’m in mac too. this secret.key is created at early 2018 not 0.11.2.
and i have tried 0.11.1, 0.11.2 and 0.9.0 all shows error , but i think my file path is right, because it add a secret.key.lock file automatically.

Contributor
nikolaglumac commented Dec 21, 2018

@yuelipeng did you have a spending-password set for this wallet of yours?

yuelipeng commented Dec 21, 2018

@nikolaglumac yes, password protected.

Contributor
nikolaglumac commented Dec 21, 2018

@yuelipeng so the problem is your wallet’s secret.key file is encrypted and therefore it can not be imported using the steps I have described in my first comment.
I’ll investigate if there is something else we could try.

Contributor
nikolaglumac commented Dec 21, 2018

@yuelipeng did you save any other files from the state directory besides the secret.key one?

yuelipeng commented Dec 21, 2018
Contributor
nikolaglumac commented Dec 21, 2018

@yuelipeng unfortunately, there is no easy way to extract a wallet.key file out of the secrets.key you have. Still, there is no reason for despair as @cleverca22 is working on a util app which will make this extraction possible. Once this util is ready @cleverca22 will update this thread and you will then be able to use the extracted wallet.key for importing in the latest Daedalus version.

yuelipeng commented Dec 22, 2018

@cleverca22 when will this extraction util app be done, you can just build a command line tool to decode.

nikolaglumac changed the title how can i restore wallet from secret.key file Jan 30, 2019
nikolaglumac added the feature-request label Jan 30, 2019
webmacho commented Mar 20, 2019

This is what I need because when I instaled the new daedlus instance year after this instance used wallet that I don’t have password for it so it never asked me for 12 words phrase to write down, I have sen’t funds and downloaded paper wallet instuctions I tought that was it but money is now stuck in old wallet from what I don’t have a password or phrase

webmacho commented Mar 20, 2019

@cleverca22 when will this extraction util app be done, you can just build a command line tool to decode.

that is it, with decryption we could see our wallet password and send it to another wallet

webmacho commented Mar 20, 2019

OMG I found my old 12 word phrase now, lucky as hell

Contributor
nikolaglumac commented Mar 20, 2019 •

@webmacho writing down your 12 words recovery phrase during wallet creation is the most important step. Having those 12 words protects you from all potential issues — it can save you even if you forget your spending-password. It is very unfortunate that you forgot this phrase.

I have sen’t funds and downloaded paper wallet instuctions I tought that was it but money is now stuck in old wallet from what I don’t have a password or phrase

I believe you did not understand the paper-wallet feature. The idea behind it is that Daedalus generates a new wallet (which is in no way connected to any of the existing wallets you have in Daedalus) and then you can send ada from your other wallets to the wallet address listed on the paper wallet PDF.

. and then follow these steps:

Using Daedalus «Wallet importer» tool

1. Salvage/save secret.key file from the previously used Daedalus installation by copying it to a safe location. This file can be found in the state directory:

Windows: C:\Users[your user name]\AppData\Daedalus\Secrets-1.0\secret.key
macOS: ~/Library/Application Support/Daedalus/Secrets-1.0/secret.key
Linux: ~/.local/share/Daedalus/mainnet/Secrets/secret.key

1. Uninstall any existing Daedalus installation and delete the state directory:

Windows: C:\Users[your user name]\AppData\Daedalus\
macOS: ~/Library/Application Support/Daedalus/
Linux: ~/.local/share/Daedalus/mainnet/

1. Install a special Daedalus edition (links provided above).
2. Wait until Daedalus is fully synced and the main UI shown.
3. Once the main UI is shown navigate to the «Wallet Importer» screen using application menu «Daedalus > Wallet Importer».
4. Use the file-input field shown on the screen to open secret.key file salvaged from the previous Daedalus installation (described in step No. 1).
5. Daedalus will extract wallets from the submitted secret.key file and show the list of discovered wallets.
6. For each of the discovered wallets you will be able to see it’s balance and whether or not it is protected by a spending password.
7. All the wallets that haven’t been protected by a spending password can be imported right away (note: wallet import process takes between 30 and 120 minutes depending on the machine speed and there can be only one active import process at the time).
8. Use the «Passwords list» field to enter a list of up to 20 potential spending passwords and then click the «Match passwords» button in order to match them to your wallets.
9. You can repeat step No. 10 until all the wallet passwords are matched.
10. All the wallets you import using this tool will no longer be protected by a spending password which will enable you to transfer your ada to another wallet.

This will resolve your issues too @yuelipeng.

yuelipeng commented Mar 21, 2019

@nikolaglumac thanks for the improvement. But after i selected the secret.key, it shows «Wallet could not be imported, please make sure you are providing a correct file». i didn’t modified the file.

Contributor
nikolaglumac commented Mar 21, 2019

@yuelipeng I believe you used the «Import dialog» from the «Add wallet» screen and this is not something you can do with the «secret.key» file.
You have to use the new screen — the one you can navigate from the application menu -> «Daedalus > Wallet importer».

yuelipeng commented Mar 21, 2019

@nikolaglumac ok, my fault, restoration is in progress, thanks.

yuelipeng commented Mar 21, 2019

@nikolaglumac thanks, it’s already recovered.

Contributor
nikolaglumac commented Mar 21, 2019
Aleksaleks1970 commented Jun 5, 2019

Thank you guys for your work. You helped me get my money back!

GeekFinity commented Nov 15, 2019

Now a day, Yoroi should be able to restore a wallet from a Daedalus un-encrypted master key.
Does anyone know a console command in Daedalus to decrypt the encrypted master key (secret.key)?

icyak commented Dec 17, 2019

any possibility how to recover wallet from secret.key ?

sohosynergy commented Jan 11, 2020

I tried to download the app you referenced below but the link is dead and I am trying your solution to recover my wallet.

@webmacho writing down your 12 words recovery phrase during wallet creation is the most important step. Having those 12 words protects you from all potential issues — it can save you even if you forget your spending-password. It is very unfortunate that you forgot this phrase.

I have sen’t funds and downloaded paper wallet instuctions I tought that was it but money is now stuck in old wallet from what I don’t have a password or phrase

I believe you did not understand the paper-wallet feature. The idea behind it is that Daedalus generates a new wallet (which is in no way connected to any of the existing wallets you have in Daedalus) and then you can send ada from your other wallets to the wallet address listed on the paper wallet PDF.

. and then follow these steps:

Using Daedalus «Wallet importer» tool

1. Salvage/save secret.key file from the previously used Daedalus installation by copying it to a safe location. This file can be found in the state directory:

Windows: C:\Users[your user name]\AppData\Daedalus\Secrets-1.0\secret.key
macOS: ~/Library/Application Support/Daedalus/Secrets-1.0/secret.key
Linux: ~/.local/share/Daedalus/mainnet/Secrets/secret.key

1. Uninstall any existing Daedalus installation and delete the state directory:

Windows: C:\Users[your user name]\AppData\Daedalus
macOS: ~/Library/Application Support/Daedalus/
Linux: ~/.local/share/Daedalus/mainnet/

1. Install a special Daedalus edition (links provided above).
2. Wait until Daedalus is fully synced and the main UI shown.
3. Once the main UI is shown navigate to the «Wallet Importer» screen using application menu «Daedalus > Wallet Importer».
4. Use the file-input field shown on the screen to open secret.key file salvaged from the previous Daedalus installation (described in step No. 1).
5. Daedalus will extract wallets from the submitted secret.key file and show the list of discovered wallets.
6. For each of the discovered wallets you will be able to see it’s balance and whether or not it is protected by a spending password.
7. All the wallets that haven’t been protected by a spending password can be imported right away (note: wallet import process takes between 30 and 120 minutes depending on the machine speed and there can be only one active import process at the time).
8. Use the «Passwords list» field to enter a list of up to 20 potential spending passwords and then click the «Match passwords» button in order to match them to your wallets.
9. You can repeat step No. 10 until all the wallet passwords are matched.
10. All the wallets you import using this tool will no longer be protected by a spending password which will enable you to transfer your ada to another wallet.

This will resolve your issues too @yuelipeng.

Contributor
nikolaglumac commented Jan 14, 2020

@sohosynergy the links have probably expired.
@disassembler @cleverca22 is there any way for us to restore these installers?

mondonet commented Feb 8, 2020

Links are not working. can you provide us with other working links?

mondonet commented Feb 8, 2020

My story. i upgraded to a bigger hard drive and install new windows operating system on the new hard drive. then i connect the old one to transfer all my files and when i look at the files on my old hard drive i can see all the scrennshot .png files in there but i can’t open it.
One of those .png files was my 12 seed words to my mainnet Daedalus wallet.
However i’m able to restore the incentivized testnet yoroi wallet with the 15 seed words.
My only option is to figure out how to restore it with the secret.key file which by the way appears to be encrypted.
If anyone knows a solution to this problem please help us and post it here.
Thanks in advance.

mondonet commented Feb 8, 2020

The links above not working. there’s any way we can restore Daedalus with the secret key file.
Any help is highly appreciated.

Ugosha commented Mar 2, 2020 •

The problem is still actual. Need to recover my secret.key to. Please update links above (Windows version). Thanks a lot!

hirohiro8382 commented May 16, 2022 via email
Thank you. # 1234 I saw everything, but there was no solution.

2022/05/16 18:45、Dragovioon ***@***.***>のメール: The restoration was successful using secret.key. However, I cannot send money. Is there a solution ? I need to remember my spending password but I have no idea need help pay well

michalrus commented May 16, 2022 •

internal: correct linking of ↑: #2985

hirohiro8382 mentioned this issue May 16, 2022
serjikc commented Jun 24, 2022

I am reaching out with almost similar problem. I have lost the spending password and the key phrase -daedalus wallet- byron. Can anything be done to retirieve the funds out of that wallet that it has been set up around 17-2018? I can see the funds on my laptop, I have the secret.key but I have no other information that would allow me to transfer the funds from this wallet to another. The password I’ve created is very long and has had a variety of characters that would be impossible to remember even if I tried 3 months straight to dig and remember.

Is iohk foundation able to help or is anything in the making to help retrieve these locked funds for all users?

An answer would be greatly appreciated thanks !

Contributor
danielmain commented Jun 24, 2022

Hi,

I am reaching out with almost similar problem. I have lost the spending password and the key phrase -daedalus wallet- byron. Can anything be done to retirieve the funds out of that wallet that it has been set up around 17-2018? I can see the funds on my laptop, I have the secret.key but I have no other information that would allow me to transfer the funds from this wallet to another. The password I’ve created is very long and has had a variety of characters that would be impossible to remember even if I tried 3 months straight to dig and remember.

Is iohk foundation able to help or is anything in the making to help retrieve these locked funds for all users?

An answer would be greatly appreciated thanks !

Dragovioon commented Jun 24, 2022

Hi,
I am reaching out with almost similar problem. I have lost the spending password and the key phrase -daedalus wallet- byron. Can anything be done to retirieve the funds out of that wallet that it has been set up around 17-2018? I can see the funds on my laptop, I have the secret.key but I have no other information that would allow me to transfer the funds from this wallet to another. The password I’ve created is very long and has had a variety of characters that would be impossible to remember even if I tried 3 months straight to dig and remember.
Is iohk foundation able to help or is anything in the making to help retrieve these locked funds for all users?
An answer would be greatly appreciated thanks !

There is no tópic about losing all passwords. Been in this situation for years now. No help whatsoever

Dragovioon commented Jun 24, 2022

Hi,

I am reaching out with almost similar problem. I have lost the spending password and the key phrase -daedalus wallet- byron. Can anything be done to retirieve the funds out of that wallet that it has been set up around 17-2018? I can see the funds on my laptop, I have the secret.key but I have no other information that would allow me to transfer the funds from this wallet to another. The password I’ve created is very long and has had a variety of characters that would be impossible to remember even if I tried 3 months straight to dig and remember.

Is iohk foundation able to help or is anything in the making to help retrieve these locked funds for all users?

An answer would be greatly appreciated thanks !

I have hundreds of thounsends of dollars trapped in my Open wallet and no help Will Come friend. This is a very sad situation

valbucci commented Jun 24, 2022 •

I’ll have to sync with @nikolaglumac about the best way to proceed but I think it’d be great to have that feature back in the recovery feature because others may be in that situation; so it’ll likely end up in some future version of Daedalus Flight.

I can draft a PR to extend the current recovery feature to also process that file and extract the secret key out of it.

Any news about this? I’m a developer and I would like to contribute. Please let me know if there is a way I can help

Dragovioon commented Jun 24, 2022

I’ll have to sync with @nikolaglumac about the best way to proceed but I think it’d be great to have that feature back in the recovery feature because others may be in that situation; so it’ll likely end up in some future version of Daedalus Flight.
I can draft a PR to extend the current recovery feature to also process that file and extract the secret key out of it.

Any news about this? I’m a developer and I would like to contribute. Please let me know if there is a way I can help

Also looking for a solution for só long now.

serjikc commented Jun 24, 2022

I am sure there’s a solution for every problem. Iohk foundation must do something for the sake of it’s community. For the past 3 years I’ve read a lot about people like me that lost their funds due to different incidents and due to the rush in the market I can understand that such minor problem in the eyes of iohk foundation is not as important. But as time passes, the foundation must and shall dedicate to themselves to come up with something solve this issue. Cardano is not Terra Luna, and Charles Hoskinson is not Do Kwon. This can’t go just like that, as a matter fact you definitely take and lead by example as other projects lead the market if that is the overall goal.

Contributor
danielmain commented Jun 25, 2022

@serjikc with all respect, the problem here is not about an incident. It’s about someone forgetting their passphrase. We have a dedicated team that filter this kind of requests so please contact our service desk here: https://iohk.zendesk.com/hc/en-us/categories/360000877653-Daedalus-Mainnet

valbucci commented Jun 25, 2022

@serjikc with all respect, the problem here is not about an incident. It’s about someone forgetting their passphrase.

That is not completely true. At least in my case, it is about a wallet exported to a file in 2017, which is not being recognised by the current Daedalus wallet recovery feature. I forgot my recovery seed, but I perfectly remember my passphrase.

I am simply asking if there are any news on this and, if not, if there is a way for me to contribute in solving this backward-compatibility issue.

valbucci commented Jun 25, 2022 •

No, that’s actually good ending. We will certainly be able to do something for you 🙂

I’ll have to sync with @nikolaglumac about the best way to proceed but I think it’d be great to have that feature back in the recovery feature because others may be in that situation; so it’ll likely end up in some future version of Daedalus Flight.
I can draft a PR to extend the current recovery feature to also process that file and extract the secret key out of it.

I was just hoping to see some sort of update since these messages. Not necessarily a solution, but at least knowing that the issue is being worked out

Contributor
danielmain commented Jun 25, 2022 •

@endlessbux, unfortunately, the colleagues who were trying to help you with the corrupted secret.key could not find any solution. Besides they don’t work at IO anymore. Our colleges in the service desk are already in touch with some people that actually are reporting the same problem and with the exact same secret.key. I can’t really do anything from the Daedalus Team side. please contact the service desk.

Dragovioon commented Jun 25, 2022

@endlessbux, unfortunately, the colleagues who were trying to help you with the corrupted secret.key could not find any solution. Besides they don’t work at IO anymore. Our colleges in the service desk are already in touch with some people that actually are reporting the same problem and with the exact same secret.key. I can’t really do anything from the Daedalus Team side. please contact the service desk.

No One can do anything! And no One Cares

Contributor
danielmain commented Jun 25, 2022 •

@endlessbux, unfortunately, the colleagues who were trying to help you with the corrupted secret.key could not find any solution. Besides they don’t work at IO anymore. Our colleges in the service desk are already in touch with some people that actually are reporting the same problem and with the exact same secret.key. I can’t really do anything from the Daedalus Team side. please contact the service desk.

No One can do anything! And no One Cares

That is not true, a lot of time was spent here. And I am writing you in my weekend even!

Sorry for being direct with you, but you should ALWAYS save securely your recovery phrase

wadie914 commented Jun 25, 2022 via email
I gave up on 50 Grand

On Sat, Jun 25, 2022, 5:00 PM Daniel Main ***@***.***> wrote: @endlessbux , unfortunately, the colleagues who were trying to help you with the corrupted secret.key could not find any solution. Besides they don’t work at IO anymore. Our colleges in the service desk are already in touch with some people that actually are reporting the same problem and with the exact same secret.key. I can’t really do anything from the Daedalus Team side. *please contact the service desk.* No One can do anything! And no One Cares That is not true, a lot of time was spent here to help here. And I am writing you in my weekend even! *Sorry for being direct with you, but you should ALWAYS save securely your recovery phrase* — Reply to this email directly, view it on GitHub , or unsubscribe . You are receiving this because you were mentioned.Message ID: ***@***.***>

serjikc commented Jun 25, 2022

@serjikc with all respect, the problem here is not about an incident. It’s about someone forgetting their passphrase. We have a dedicated team that filter this kind of requests so please contact our service desk here: https://iohk.zendesk.com/hc/en-us/categories/360000877653-Daedalus-Mainnet

My case is similar @danielmain I had my information saved on a flashdrive the spending password and the seed) — someone has erased the flash drive. — Now I have access to the desktop wallet with the funds but I am not able to transfer from the account to a new wallet due to missing password and seed. I have the secret key file but that doesn’t do anything other than just recover the wallet with the funds in it but can’t retrieve the funds due to the missing password and or seed.

wadie914 commented Jun 25, 2022 via email

Program version did you open secret file keywords every time I try to open the secret key files it tells me it’s invalid I have my password

On Sat, Jun 25, 2022, 5:58 PM serjikc ***@***.***> wrote: @serjikc with all respect, the problem here is not about an incident. *It’s about someone forgetting their passphrase*. We have a dedicated team that filter this kind of requests so please contact our service desk here: https://iohk.zendesk.com/hc/en-us/categories/360000877653-Daedalus-Mainnet My case is similar @danielmain I had my information saved on a flashdrive the spending password and the seed) — someone has erased the flash drive. — Now I have access to the desktop wallet with the funds but I am not able to transfer from the account to a new wallet due to missing password and seed. I have the secret key file but that doesn’t do anything other than just recover the wallet with the funds in it but can’t retrieve the funds due to the missing password and or seed. — Reply to this email directly, view it on GitHub , or unsubscribe . You are receiving this because you were mentioned.Message ID: ***@***.***>

valbucci commented Jun 25, 2022 •

@endlessbux, unfortunately, the colleagues who were trying to help you with the corrupted secret.key could not find any solution. Besides they don’t work at IO anymore. Our colleges in the service desk are already in touch with some people that actually are reporting the same problem and with the exact same secret.key. I can’t really do anything from the Daedalus Team side. please contact the service desk.

I’ll try to reach the service desk once again, but the last time I contacted them one year ago they couldn’t solve this problem.

Could you please direct me to the portion of code which used to generate the backup file?

I just find it very much disappointing that the Daedalus Team included this feature which actually turns out to not work at all. At least I would like to see if I can manage to deal with this by myself, considering the file is not corrupted and I remember my spending password.

Apologies for being direct but this lack of backward-compatibility caused me to lose my funds.

Dragovioon commented Jun 26, 2022

I gave up on 50 Grand
…
On Sat, Jun 25, 2022, 5:00 PM Daniel Main @.> wrote: @endlessbux https://github.com/endlessbux, unfortunately, the colleagues who were trying to help you with the corrupted secret.key could not find any solution. Besides they don’t work at IO anymore. Our colleges in the service desk are already in touch with some people that actually are reporting the same problem and with the exact same secret.key. I can’t really do anything from the Daedalus Team side. please contact the service desk. No One can do anything! And no One Cares That is not true, a lot of time was spent here to help here. And I am writing you in my weekend even! Sorry for being direct with you, but you should ALWAYS save securely your recovery phrase — Reply to this email directly, view it on GitHub , or unsubscribe https://github.com/notifications/unsubscribe-auth/AS7OIOABF2S7MHJ2S4Y4SZTVQ5XQTANCNFSM4GLRZXHQ . You are receiving this because you were mentioned.Message ID: @.>

Lost dar more than 50 grande friend and watched all my investment Lost during years of mental illness. Asking every chat you fórum or the support for Help and all people Will have say is «you should not lose the seed phrase»

Contributor
KtorZ commented Jul 8, 2022

I am starting a collaborative effort as part of CardanoSolutions/ByronWalletRecovery, trying to centralize all the existing knowledge, tools and content about this issue. If some have time and are interested in solving this, I encourage you to join and participate.

Contributor
KtorZ commented Jul 8, 2022 •

@danielmain if you can forward this to the current support team to let them know �� and possibly, let them redirect people to this repository once they’ve identified that they might be affected by this mysterious issue.

Saved searches

Use saved searches to filter your results more quickly

Cancel Create saved search

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

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

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

skazichris opened this issue Dec 14, 2020 · 77 comments

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

skazichris opened this issue Dec 14, 2020 · 77 comments

Comments

skazichris commented Dec 14, 2020

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.

The text was updated successfully, but these errors were encountered:

KtorZ commented Jan 4, 2021

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 commented Jan 4, 2021

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 commented Jan 4, 2021

@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 commented Jan 4, 2021

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 commented Jan 5, 2021

• 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 commented Jan 8, 2021

@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 commented Jan 9, 2021

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 commented Jan 9, 2021 •

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 commented Jan 10, 2021

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 commented Jan 10, 2021 •

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 commented Jan 11, 2021 •

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

Contributor
piotr-iohk commented Jan 11, 2021 •

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 

~/.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 commented Jan 11, 2021 •

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

Contributor
piotr-iohk commented Jan 11, 2021

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 

$ 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?

khughes5 commented Jan 11, 2021 •

@piotr-iohk — Thanks SO much. i just got it to work! and thanks to @KtorZ for originally providing reference to the tools and @mprymek for the heads up on linux version

Before i was just copying a subset of files and Directories (Wallet-1.0-acid, Wallet-1.0-sqlite.sqlite3 and Secrets-1.0)..

This time i copied the whole Directory (c:\users\Name\AppData\Roaming\Daedalus) across into linux, dumped them in the user documents directory like you did and ran the tool as you specified.. it worked! I don’t have a very good grasp on linux, so maybe i was screwing something else up before..

Now i am off to start looking at the whole API side, to try and see how to import the encrypted strings!!

PS for those following along (and like me have no linux exp), after a default install of Ubuntu 18.04 i had to run «sudo apt-get update» then «sudo apt-get install librocksdb5.8» to get the required library to be able to get the tool to run (you need an internet connection for that to work)

clovehitch commented Jan 12, 2021

@khughes5 Did you figure out how to import the encrypted strings?

khughes5 commented Jan 12, 2021 •

Unfortunately not yet (i am not a programmer).. and i don’t even know if i am on the right track here.. but i was hoping to use my Daedalus flight 3.1.0 install on windows (which seems to run the cardano-node.exe on a random listening port), along with the method described in https://iohk.zendesk.com/hc/en-us/articles/900000672303-How-to-migrate-a-Byron-Legacy-wallet-to-cardano-wallet- with the payload replaced with that described in the random(from xprv) tab by KtorZ above..

the listening port number for cardano-wallet appears to be shown in FC3.1.0 under help/Deadalus Diagnostics.. but right now i am getting certificate errors when using curl against the port for a simple query (like https://localhost:64139/wallets) .. Even when i use the —cacert pointing to the \tls\client\client.pem file, it displays the error «the certificate chain was issued by an authority that is not trusted».. not sure if we are able to run the api calls via the FC developer tools/console interface..

again not sure if i am totally missing the mark here.. very open to help from anyone in the thread about what to do with the extracted information from the tool 🙂

nikolaglumac mentioned this issue Jan 12, 2021
Contributor
piotr-iohk commented Jan 12, 2021

@khughes5 I have a tool that can be handy for your use case, but you’ll need to have ruby installed on your system. For Windows Ruby+Devkit 2.7.2-1 (x64) from https://rubyinstaller.org/downloads/ should be OK.

The tool (https://github.com/piotr-iohk/ikar) is a lightweit web app over cardano-wallet and can be easily connected with underalying cardano-wallet of your Daedalus instance.

1. To start the tool (once you have ruby on your system):

git clone https://github.com/piotr-iohk/ikar.git cd ikar bundle config set without 'development test' bundle install ruby app.rb 

1. Then point your browser to http://localhost:4444/ and click at «Discover» button. If you have Daedalus running you should get it on the list of discovered cardano-wallet servers, like this:

1. Click «Connect»
2. Then go to «Byron Wallets» -> «Create random (from xprv)»
3. Paste the output of export-wallets command into the form like below and hit «Create»

1. That’s it. You should have your wallet now visible in Daedalus and once it is restored you should be able to migrate your funds to Shelley wallet from there.

Hope that helps!

khughes5 commented Jan 12, 2021

@piotr-iohk I can’t thank you enough. thanks so much, using your instructions (and install git for windows) i was able to easily import it into my Daedalus app, and transfer the ADA across to a new shelley wallet!!

That’s a massive weight off my shoulders! and i can’t thank you enough. I am sure i am not the first to be saved from everyones guidance and advice through this thread!!

devilus commented Jan 13, 2021 •

I trying to rename «Wallet-1.0» to «Wallet-1.0-acid» but use «Wallet-1.0» in command line instead, so now the error «There’s no acid-state database matching the given path.» resolved:

./export-wallets —wallet-db-path /Wallet-1.0 —keyfile /Secrets-1.0/secret.key —mainnet

But now I get the error

export-wallets: Could not parse saved checkpoint due to the following error: Failed reading: safecopy: Cardano.Wallet.Kernel.DB.AcidState.DB: Cannot find getter associated with this version number: Version Empty call stack CallStack (from HasCallStack): error, called at src/Data/Acid/Local.hs:329:7 in acid-state-0.15.0-KPx3nxg5ffCDH1G6VxHbSk:Data.Acid.Local 

I used daedalus in 2018 last time and now I have only Secrets-1.0 and Wallet-1.0 folders backup. Also I remember decrypt pasword.
Anyone can help? Thanks guys.

KtorZ commented Jan 13, 2021

I triggered a compilation during lunch of the latest version of the export tool linked earlier. That version makes the acid-state database optional (as it is only really used to extract wallet names and map them to keys in the keystore). So you could use that to extract keys from your keystore. If you’ve a single one there’s no ambiguity, and if you have multiple ones, you’d have to figure out which one is which by restoring them all and looking at the transaction history.

devilus commented Jan 13, 2021

Which linux version do you use? I can’t find librocksdb.so.6 package for ubuntu 18.

./export-wallets --keyfile /Secrets-1.0/secret.key --mainnet ./export-wallets: error while loading shared libraries: librocksdb.so.6: cannot open shared object file: No such file or directory 

KtorZ commented Jan 13, 2021 •

The binary isn’t statically linked sorry. That’d take a bit more work to do for Haskell system dependencies are typically dynamically linked. You need rocksdb to run that one unfortunately. On aptitude, you get the necessary dependencies by installing librocksdb-dev

apt get install librocksdb-dev 

devilus commented Jan 13, 2021

Ok now I have a restored key from secret key:

Don’t understand fully what I need to do now?

Contributor
piotr-iohk commented Jan 13, 2021

@devilus one option is to try with this -> #2395 (comment).

(Probably you might want to change «name»: null into something like «name»: «My wallet» )

devilus commented Jan 13, 2021 •

@piotr-iohk
I trying your solution right now 🙂

I have a lastest 3.1.0 version Daedalus Mainnet installed and synced with fresh wallet. But after https connection to node only «Tools->Generate mnemonics» menu active. What I’m doing wrong?

Contributor
piotr-iohk commented Jan 13, 2021

Did you click at Discover button and Connected to your Daedalus?

devilus commented Jan 13, 2021

After click «Discover»

After click «Connect»

chmieleslav commented Feb 7, 2021 •

I just realized that I was missing export (sorry. )

root@chmiel:~# sudo ldconfig -v /usr/local/lib: librocksdb.so.6.17 -> librocksdb.so.6.17.0 /usr/lib: librocksdb.so.5.8 -> librocksdb.so.5.8.8 

With the following command:
root@chmiel:~# export LD_LIBRARY_PATH=/lib:/usr/lib:/usr/local/lib I moved forward, but I have a new error.

root@chmiel:/mnt/c/Users/Piotr/AppData/Roaming/Daedalus# ./export-wallets --mainnet --wallet-db-path Wallet-1.0 --keyfile Secrets-1.0/secret.key ./export-wallets: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by ./export-wallets) ./export-wallets: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by ./export-wallets) 

After the upgrade to Ubuntu 20.04:

root@chmiel:/mnt/c/Users/Piotr/AppData/Roaming/Daedalus# ./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.) 

I’m not sure I understand «acid» term correctly, but wasn’t it supposed to be optional? Thank you in advance

KtorZ pinned this issue Feb 8, 2021
KtorZ commented Feb 8, 2021

@chmieleslav note that it now exists a pure TypeScript version of that keystore exporter. See the following pull request:

Thus, provided that you have node and npm installed, you could do as follows:

$ wget -O- https://github.com/input-output-hk/daedalus/archive/a82994e4fcf6cdc9551a46216fea8ba7eb571e33.zip | bsdtar xf - --include='*restore-keystore*' $ cd daedalus-a82994e4fcf6cdc9551a46216fea8ba7eb571e33/restore-keystore $ npm install && chmod +x restore-keystore.ts

chmieleslav commented Feb 8, 2021 •

This worked like a charm, it gave me:

Then I used Ikar, did the steps described in #2395 and voilà, I can see my old wallet syncing in the new Daedalus:

Thank you so much @piotr-iohk and @KtorZ — you saved my ADA savings and I learnt a lot from you! 🙂

aaronk6 commented Feb 8, 2021 •

Worked for me, too! Thanks so much, folks! (Yes, I’m one of those who were “smart” enough to backup secret.key instead of writing down the mnemonic back in 2018).

However, I ran into two issues with the steps above which might be related to me being on macOS (not sure though).

Here is what I did to make the restore-keystore.ts utility work:

• Replace the first line in restore-keystore.ts by #!/usr/bin/env ts-node-script
• Install typescript and ts-node globally: npm install -g typescript ts-node (sudo was not required)

Also, the ikar approach didn’t work for me. All tabs except “Tools” were disabled, even though it was set to the correct port.

I’ve therefore directly connected to the API using curl as outlined above by @piotr-iohk:

curl --cacert "$HOME/Library/Application Support/Daedalus Mainnet/tls/client/ca.crt" \ --cert "$HOME/Library/Application Support/Daedalus Mainnet/tls/client/client.pem" \ https://localhost:$port/v2/byron-wallets -H "Content-Type: application/json" \ -d '' 

Make sure to replace $port , $encrypted_root_private_key , and $passphrase_hash by your actual values. You can look up the port by pressing ⌘ D in Daedalus.

That worked like a charm! Again, thanks a lot! ❤️

strangedesign11 commented Feb 10, 2021

I was able to restore my wallet from my old state directory, so big thanks to everyone on this thread. However, that was only half the battle for me in regaining control of my ADA as I do not have my seed phrase (which is, admittedly irresponsible and entirely my fault given the warnings in Daedalus) and I am unable to recall my spending password.

Is there any method to decrypt/extract/recover the existing spending password or otherwise bypass the spending password to allow me to move funds out of the old wallet? Thanks!

KtorZ commented Feb 10, 2021

Is there any method to decrypt/extract/recover the existing spending password or otherwise bypass the spending password to allow me to move funds out of the old wallet?

No. The seed is encrypted with strong encryption. It’d take you more than a lifetime to brute force it. So, best you can do is to try passphrases you can think of. Again and again :/.

wawabiker commented Feb 11, 2021

The method worked perfectly well for me: #2395 (comment)

I am a windows user. I have used the virtualbox with Ubuntu 20.04 and installed npm and node:
https://www.geeksforgeeks.org/installation-of-node-js-on-linux/
Copied the secrets dir and run the restore-keystore tool.

Ikar worked perfectly well to import wallet back to daedalus as described. Fortunately I got the spending pass.

Thank you for this thread!

strangedesign11 commented Feb 11, 2021

Is there any method to decrypt/extract/recover the existing spending password or otherwise bypass the spending password to allow me to move funds out of the old wallet?

No. The seed is encrypted with strong encryption. It’d take you more than a lifetime to brute force it. So, best you can do is to try passphrases you can think of. Again and again :/.

Thanks for the reply. Unfortunately for me, I used my password manager to generate a secure spending password and then somehow failed to save it.

To come at it from a different angle, is there a way to repeatedly retry/check the spending password without manual intervention such that I could use a password cracking program to try to crack the spending password? I’m fairly certain I know the number of characters in the spending password, but that’s about all I have to go on.

Thanks again for your help. I know this isn’t really a Cardano/Daedalus issue and was caused entirely by user error, so I really appreciate any insight you (or anyone else here) might be able provide.

KtorZ commented Feb 11, 2021

@strangedesign11 such that I could use a password cracking program to try to crack the spending password

I am really sorry but, If this was possible we would have a major vulnerability problem. Things is, with the current encryption algorithm and parameters, each verification takes around 50ms on a high-end CPU. If you’ve generated your passphrase using a passphrase manager, then it’s likely a quite secure passphrase, with quite many characters. The encryption is resistant to rainbow tables and dictionary attacks, so even with a passphrase of only 6 characters, it’d take you a few hundred years to brute-force it. Even with a modern GPU, for a long-enough passphrase it would just be unfeasible :/

michael8359 commented Feb 16, 2021

Hi KtorZ, I tried to restrore my wallet using Daedalus Flight 3.3.0 using my secret.key but i got below error message. Is my secret.key corrupt or won’t work with Daedalus Flight 3.3.0?

KtorZ commented Feb 16, 2021

@michael8359 Sounds like your secret.key is empty or corrupted indeed.

michael8359 commented Feb 16, 2021

@KtorZ No way for me to recover my wallet?

KtorZ commented Feb 18, 2021

@michael8359 I am afraid not. For any help with Daedalus however, please contact the technical support desk or, reach out on input-output-hk/daedalus#1234.

Incidentally, one of the last comment on that thread recommend to make sure to close the old Daedalus before attempting to restore from the secret.key file. Make sure it’s the case ��

Closing this issue now since Daedalus 3.3.0 now bring back the wallet recovery feature. Thanks all for your patience ��

KtorZ closed this as completed Feb 18, 2021
Anviking unpinned this issue Mar 31, 2021
NeedHelp305 commented May 2, 2021 •

@KtorZ or anyone I have used the virtualbox with Ubuntu 20.04 and installed npm and node. Copied the secrets dir and run the restore-keystore tool as described above in Ubuntu Terminal. I get the below error. What am I doing wrong? Am I missing a package or library? Thanks.

(node:4030) UnhandledPromiseRejectionWarning: Error: Additional info not implemented: 30
at Decoder._parse (/home/cmendez305/daedalus-a82994e4fcf6cdc9551a46216fea8ba7eb571e33/restore-keystore/node_modules/cbor/lib/decoder.js:455:17)
at _parse.next ()
at Decoder._transform (/home/cmendez305/daedalus-a82994e4fcf6cdc9551a46216fea8ba7eb571e33/restore-keystore/node_modules/cbor/vendor/binary-parse-stream/index.js:45:29)
at Decoder.Transform._read (internal/streams/transform.js:205:10)
at Decoder.Transform._write (internal/streams/transform.js:193:12)
at writeOrBuffer (internal/streams/writable.js:358:12)
at Decoder.Writable.write (internal/streams/writable.js:303:10)
at NoFilter.ondata (internal/streams/readable.js:719:22)
at NoFilter.emit (events.js:315:20)
at NoFilter.EventEmitter.emit (domain.js:467:12)
(Use node —trace-warnings . to show where the warning was created)
(node:4030) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag —unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:4030) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Contributor
piotr-iohk commented May 4, 2021

@NeedHelp305 the feature of importing old wallet from state directory or secret.key is now available directly in Daedalus. Have you tried that? (Add wallet -> Import)

NeedHelp305 commented May 8, 2021

@NeedHelp305 the feature of importing old wallet from state directory or secret.key is now available directly in Daedalus. Have you tried that? (Add wallet -> Import)

Indeed I did was the first thing I tried actually. I get the dreaded ‘Wallets not found. ‘ error as attached even though I point to directory and there is data in both State directory and secret.key file.

and this:

So then I built a VM with Ubuntu 18.04. Installed node. Installed npm. Python etc. tried the ./export-wallets tool as described above and I’m now stuck here with this error:

From the little I’ve been able to learn about Ubuntu it sounds like it’s missing a specific file or library? Have not found how to install this missing library yet. Any ideas much appreciated. Thanks.

NeedHelp305 commented May 8, 2021

Also tried the ./restore-keystore.ts tool in Ubuntu 18.04 and I got stuck with that one at this point with this error:

So I ran the suggested ‘npm fund’ which showed me this:

What am I doing wrong with the restore-keystore tool?

quangthienit1994 commented Dec 20, 2021

@strangedesign11 such that I could use a password cracking program to try to crack the spending password

I am really sorry but, If this was possible we would have a major vulnerability problem. Things is, with the current encryption algorithm and parameters, each verification takes around 50ms on a high-end CPU. If you’ve generated your passphrase using a passphrase manager, then it’s likely a quite secure passphrase, with quite many characters. The encryption is resistant to rainbow tables and dictionary attacks, so even with a passphrase of only 6 characters, it’d take you a few hundred years to brute-force it. Even with a modern GPU, for a long-enough passphrase it would just be unfeasible :/

Excuse me, Can you explain about algorithm of passphare ? I don’t see any document said about it.