input-output-hk/daedalus

I want to solve the problem that "created_invalid_transaction" is output by migration

zktky opened this issue · 5 comments

zktky commented

In daedalus 4.11.0, wallet was restored from sercret.key.
On daedalus, synchronization is completed and the balance is displayed normally, but when I try to move to shelly-wallet, an error is displayed.

I don't know the solution on daedalus, so I tried Migrations using Cardano Wallet Backend API, but Create a migration plan is returned normally,
Migrate fails.

It seems that there is an error in the signature part of transaction. Is there any solution?

■Create a migration plan (Succeed)
https://input-output-hk.github.io/cardano-wallet/api/edge/#operation/createByronWalletMigrationPlan

curl -X POST -H "Content-Type: application/json" --cacert "$HOME/Library/Application Support/Daedalus Mainnet/tls/client/ca.crt" \
  --cert "$HOME/Library/Application Support/Daedalus Mainnet/tls/client/client.pem" \
  -d '{"addresses": ["The_recipient_addresses"]}' \
  https://localhost:{daedalus_local_port}/v2/byron-wallets/{walletId}/migrations/plan 

{
    "balance_selected": {
        "ada": {
            "quantity": **********,
            "unit": "lovelace"
        },
        "assets": []
    },
    "total_fee": {
        "quantity": *******,
        "unit": "lovelace"
    },
    "selections": [
        {
            "withdrawals": [],
            "inputs": [
                {
                    "address": "********************************************************",
                    "id": "******************************************************",
                    "index": 0,
                    "amount": {
                        "quantity": ******,
                        "unit": "lovelace"
                    },
                    "derivation_path": [
                        "0H",
                        "*********"
                    ],
                    "assets": []
                },
                ...
            ],
            "outputs": [
                {
                    "address": "The_recipient_addresses",
                    "amount": {
                        "quantity": ******,
                        "unit": "lovelace"
                    },
                    "assets": []
                }
            ],
            "deposits_taken": [],
            "change": [],
            "deposits_returned": [],
            "collateral": []
        }
    ],
    "balance_leftover": {
        "ada": {
            "quantity": 0,
            "unit": "lovelace"
        },
        "assets": []
    }
}

■Create a migration plan (Error)
https://input-output-hk.github.io/cardano-wallet/api/edge/#operation/migrateByronWallet

curl -X POST -H "Content-Type: application/json" --cacert "$HOME/Library/Application Support/Daedalus Mainnet/tls/client/ca.crt" \
  --cert "$HOME/Library/Application Support/Daedalus Mainnet/tls/client/client.pem" \
  -d '{"passphrase": "*******","addresses": ["The_recipient_addresses"]}' \
  https://localhost:{daedalus_local_port}/v2/byron-wallets/{walletId}/migrations

{
    "code": "created_invalid_transaction",
    "message": "The submitted transaction was rejected by the local node. Here's an error message that may help with debugging: TxValidationErrorInMode (ShelleyTxValidationError ShelleyBasedEraAlonzo (ApplyTxError [UtxowFailure (WrappedShelleyEraFailure (MissingVKeyWitnessesUTXOW (WitHashes (fromList [KeyHash \"*****************************\",KeyHash \"*****************************\"]))))])) AlonzoEraInCardanoMode"
}
danielmain commented

Hi @zktky can you help us to reproduce your error? If you are one of the users trying to recover a secret.key that was generated by Daedalus 0.8.0 (which was not a public release) I would ask you to contact our Zendesk support.

zktky commented

Hi @danielmain
I thought it could be solved by a technical problem, so I posted it here, but I will check with support.
Also, if you would like to consult with us in a technical area, thank you.

zktky commented

Hi @danielmain
I thought it could be solved by a technical problem, so I posted it here, but I will check with support.
Also, if you would like to consult with us in a technical area, thank you.

danielmain commented

Please contact our Zendesk support.

zktky commented

Thank you. Contact support