nami: signTx's TransactionWitnessSet produce TextEnvelope decode error in cardano-cli

@alessandrokonrad . For cardano.signTx(), the output TransactionWitnessSet, does not tally the input required in cardano-cli, producing this error:

Command failed: transaction sign-witness  Error: buyer_witness_set_from_nami_signTx.witness: TextEnvelope decode error: DecoderErrorDeserialiseFailure "Shelley Witness" (DeserialiseFailure 0 "expected list len")

Seems like, the cborHex Nami produced after signTx() has extra 2 characters.

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 18 (1 by maintainers)

Most upvoted comments

Reference

@ZDust172 Here’s my blogpost on how to load signed tx https://srdjanstankovic.com/2021/12/24/how-to-sign-and-submit-cardano-cli-transaction-using-nami-wallet.html

Thanks! This should be a really helpful resource for others. I eventually opted to doing it a different way avoiding the cli altogether using the method here:

https://github.com/Emurgo/cardano-serialization-lib/issues/303

ZDust172 on Dec 24, 2021

Reference

@ZDust172 Here’s my blogpost on how to load signed tx https://srdjanstankovic.com/2021/12/24/how-to-sign-and-submit-cardano-cli-transaction-using-nami-wallet.html

pyropy on Dec 24, 2021

@jinglescode @pyropy Hi, how exactly are you guys signing the transactions in the CLI before signing it with Nami? I am attempting a similar method in #147 but the CLI still rejects my transaction.

I have pair of some random keys that I use to sign the tx, then load signed tx to nami via cardano-serialization-lib.

Thanks for the quick reply! So you’re just doing cardano-cli transaction sign --tx-body-file {FILE} --signing-key-file payment.skey then copying the generated hex CBOR into cardano.signTx()? If so I’m very puzzled by the ‘InvalidWitnessUTXOW’ error message I get as I’m doing exactly the same.

ZDust172 on Dec 18, 2021