what is the solution for closed issue #2985, I have the exact same error occurred while importing

[keedlein]

does anyone here know the solution to this issue?

Or is there still a bug existing in the import function? So whenever user tried to import secret.key file, a spending password window will prompt asking you to assign a new password to your imported wallet, but later on no matter what you do, you will see that ambiguous error message "An error occurred".

[danielmain]

#2985 (comment)

[keedlein]

im waiting for the support answering my submitted ticket for quite some time already, that's why I tried to ask it here, just wanna know if there's a hope..... :(

thank you for spending time to reply this tho, maybe there's hope somewhere

[konratmueller]

I'm in the same situation.

Importing a secret.key into Daedalus shows the correct balance and even the 2017 transactions are shown correctly.

But spending those very old UTxOs is not possible. It seems the private key creation does not account for old bugs in address derivation.

I've tried ByronRecovery by @ilap. It seems, that the secret.key file has a different root-public-key. Replacing that file pub key with the one, that cardano-address generates from the root.prv key results in ilaps tool printing

        "is-empty-passphrase": true,
        "has-valid-encryption": true,

But obviously doesn't do that with the root.pub included in the secret.key file.

We are talking about a rather large sum here which can't be accessed.

Is there any way with current tooling to generate those old addresses from the root.prv key to verify the derivation paths and potentially handcraft a transaction to migrate the funds to a shelley address?