Fehler in der Cardano-App von Ledger

[root_s2yse8vt]

Up

-1

Down

::

Wir haben eine Transaktion erzeugt, die auf eine Signatur wartet. Wenn wir diese Transaktion an die Methode \`signTx\` der Browser-Wallet-Api übergeben (\`signTx\` wie erwähnt \[here\]([https://www.cardano-caniuse.io/](https://www.cardano-caniuse.io/))), bemerken wir eine Anomalie, da die angezeigte Transaktions-ID nicht mit der unserer Transaktion übereinstimmt. Nachdem wir die Signatur mit dem Ledger-Gerät durchgeführt haben, lehnt Eternl die Signatur mit der Meldung „Tx serialization mismatch between Ledger and source transaction“ ab, wie im Screenshot gezeigt.
Die Hexadezimalzahl der Transaktion, die wir haben, ist angegeben.[here\]([https://pastebin.com/AxP7MKsd](https://pastebin.com/AxP7MKsd)) aufgrund der Beschränkung der Beitragslänge.

Dies hat die ID „481af00b740f6fe63979f9da14331349120999146d2ad566a9b86c6a58bc9e“, aber die vom Ledger angezeigte ID ist anders und wird im Bild angezeigt.

​

[Tx serialization mismatch as informed by Eternl](https://preview.redd.it/pyoix71ynl5b1.png?width=1572&format=png&auto=webp&s=b4194d6fd3d0815388306c0eb7778489caf9513a)

​

[Different transaction hash shown in ledger #1](https://preview.redd.it/lyep1gglml5b1.jpg?width=4032&format=pjpg&auto=webp&s=875a08cbefec948a180fde6570efe0d1b08bb178)

[Different transaction hash shown in ledger #2](https://preview.redd.it/vao6073oml5b1.jpg?width=4032&format=pjpg&auto=webp&s=c132834296c40e5f560790e9760880d3844eabed)

Falls dies nicht das richtige Forum ist, um dieses Problem anzusprechen, bitte ich um einen Hinweis, wo ich es tun kann. Ich glaube, der Hauptcode für diese Anwendung befindet sich \[here\]([https://github.com/LedgerHQ/app-cardano](https://github.com/LedgerHQ/app-cardano)), aber anscheinend kann ich dort kein Problem aufwerfen.

[ggsou]

Up

0

Down

::

One more thing that I can add. The outputs in my transaction are all in post alonzo format (https://github.com/input-output-hk/cardano-ledger/blob/e31573a166f2b183b69653138863a0bd23c97fd6/eras/babbage/test-suite/cddl-files/babbage.cddl#L87-L92) if I deserialize my transaction using Cardano Multiplatform Library ([https://github.com/dcSpark/cardano-multiplatform-lib](https://github.com/dcSpark/cardano-multiplatform-lib)) and serialize it back, I end up with slightly different CBOR (see [https://pastebin.com/JJ5xLpz9](https://pastebin.com/JJ5xLpz9) ) where outputs which could be simplified to alonzo format, got simplified into it. This transaction has id: „19316b763e9f1093b58dd8c33f6a5929137ffc40d9a64da3a7da96276215bb5a“ and I am successfully able to sign it. But shouldn’t I be able to sign the original transaction too? This is adding complication of using CML which is something we aren’t willing to do and also it results in different transaction hash than what we would expect.

[ggsou]

Up

0

Down

::

Note: The pastebin link I have shared above is no longer working, here is the drive link: [https://drive.google.com/file/d/16SuCmYkvvvqwdO0jGlZBpnUmjG_Rlklj/view?usp=sharing](https://drive.google.com/file/d/16SuCmYkvvvqwdO0jGlZBpnUmjG_Rlklj/view?usp=sharing).

[ggsou]

Up

0

Down

::

It’s solved. The issue was that keys in the map present in `transaction_body` (as mentioned in [CDDL](https://github.com/input-output-hk/cardano-ledger/blob/master/eras/babbage/test-suite/cddl-files/babbage.cddl)) part of the CBOR was not sorted which is a requirement pushed by [CIP 21]([https://cips.cardano.org/cips/cip21/](https://cips.cardano.org/cips/cip21/)). Sorting for it resolved the issue.

[Littlefinger_13]

Up

0

Down

::

Hi! I don’t know, if this helps you, but you are not in Mainnet. You have tADA (testnet ADA) in your account, and you are in the Pre-Prod Testnet environment.

If this is something you didn’t want, you can always change to Mainnet, by pressing the Pre-Prod box, on the down-right corner of Eternl (you can see it in your first picture).

Now, if you want to sign a Pre-prod Testnet transaction with your Ledger, maybe there lies the problem. Maybe, because it is a different type of transaction, but from the same underlying account, Ledger might not support it.

Also, the previous Testnet environment of Cardano died last September, so Ledger might not support signing transactions from the newer (Pre-Prod) one.

But, if you want to play with Pre-Prod environment, you can always do it by creating a hot wallet with Eternl, using some Cardano Faucet to get some tADA, and doing what you please thereafter.

Good luck with your problem!

P.S. Cardano’s subreddit is being closed as a protest, for the next 2 days, because of Reddit changing its policy with its free (until now) API. When it gets open, you can ask there too.

[pringles_ledger]

Up

0

Down

::

Hey – can you try using a different wallet like Typhon and let us know if you face the same issue?

Connect to Typhon: https://support.ledger.com/hc/en-us/articles/7309117078813-Connect-your-Ledger-Cardano-ADA-account-to-Typhon?support=true

If the issue persists then please reach out to us at https://support.ledger.com/hc/en-us via the Contact Us button in the bottom right so that we can escalate this case to our dev team for further review.

Let us know if you have any other questions.

[Autor]

Beiträge