-
Notifications
You must be signed in to change notification settings - Fork 721
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] - DecoderFailure of burning token TX #5898
Comments
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days. |
Is this issue still happening with latest node and cardano-api? |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days. |
This issue was closed because it has been stalled for 120 days with no activity. Remove stale label or comment or this will be closed in 60 days. |
External
Area
Tx submission
Summary
In our system we construct a burning TX using Cardano Serialisation Lib (CSL) on a browser frontend and then send it serialised as CBOR to our backend where we deserialise it, do some validation and then submit it to our local node. This has been working perfectly fine for a long time now, but recently we ran into very strange DecoderFailure errors with 2 such burning TXs, when we submitted them:
We are using CSL 11.5.0 and Cardano Node 8.9.1 with cardano-api 8.39.3.0.
We decoded the TXs both with cardano-cli as well as CSL but we could not find anything suspicious - we have the CBORs of the 2 TXs attached.
3c6def41927725728b20a13dcd9b195c4e8adc45e656eb7d31c1f91220ef1d45_cbor.txt
b373fc4e57ef514e5169fcc3709d25b26713b7f2e87136d2bdb856d487d5ade4_cbor.txt
The text was updated successfully, but these errors were encountered: