I have been using adalite.io to sign stakepool registration certificates with my hardware wallet. This workflow has worked in the past. Recently, I’ve tried to sign a new one and I get the error below. The cardano-hw-cli however, signs this transaction correctly and I am able to submit.
Parser error: Invalid transaction format. Failed to parse stakepool registration certificate.
![Screen Shot 2024-05-21 at 2.50.50 PM](https://us1.discourse-cdn.com/flex015/uploads/cardano/original/3X/4/3/4352d01de9cb4bf438a5143665a4fcd22f8e57a4.png)
Because the hw-cli seems to sign the transaction correctly, I feel like I can assume the transaction format is okay. For completeness, i’m posting the transaction building code as well.
cardano-cli transaction build-raw \
${tx_in} \
--mary-era \
${tx_out} \
--invalid-hereafter $slotNumber \
--fee ${fee} \
--certificate-file pool.cert \
--out-file tx-pool.raw
Built using cardano-cli 8.20.3.0
Can anyone give me any inisight to how I can fix this?
I understand there is a change to the Ledger Cardano app soon, or maybe already. So if you are using Ledger, it might be because of that.
Well I had a similar error a few weeks ago and the solution for me was adding --mary-era
, but I see that you already did that. To be certain: that was also included in your tx before you used the hw-cli? I used a tx constructed with the same parameters as in your example and it worked.
This can’t be the case, because you get the error when you select the raw tx file, right? So your Ledger didn’t come into play yet…
Maybe Adalite did an update recently and now you have to use another era?
Or maybe you’re using an outdated version of cardano-cli that handles that era parameter different, try using a more recent one.
Or maybe you’re using an outdated version of cardano-cli that handles that era parameter different, try using a more recent one.
I did state cardano-cli 8.20.3.0 and I believe that’s pretty recent.
I am planning on checking adalite again periodically. It does seem like an adalite problem since cardano-hw-cli successfully signed.
That isn’t the latest version though…
If the problem persists after using the latest cli, try using other era flags and see what that gives…