-
Notifications
You must be signed in to change notification settings - Fork 126
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
44 lovelace missing in calculated fee (12.0.0-beta3) #681
Comments
Hi @kxbt-del , thanks for letting know, we will investigate and fix it asap |
@kxbt-del could you also provide code to reproduce this issue ? |
There's a bunch of stuff in there, iterating collateral, exunits etc. but the essence of building the tx is roughly this:
FWIW the only thing that differs between the HF and pre-HF branch is the CSL version change. |
Why do you modify witness set after |
fair point, legacy leftover. Removing it does not seem to affect anything though |
It might affect redeemer index at least, could you try to not use these lines
|
removed them, problem remains. |
Okie, preparing test to find the issue |
@kxbt-del which other tool did you use to modify a tx ? CSL do not serialize sets under tag 258 cardano-serialization-lib/rust/src/serialization/witnesses/vkeywitnesses.rs Lines 13 to 19 in b765c78
|
There are 2 more things that may be relevant. When signing TX, I'm using
and then the
I believe the witness set combining can be adjusted given your new set logic in CSL, there's one case where the transaction is additionally signed by the platform after the wallet provides it's own sig. |
Could you check without signing by the platform ? |
Sorry for the confusion - the "sign by platform" was for context, to make it known that it does happen in one case. It is not the case for this transaction. So here what we see is what we get. |
Just reproduced whole your tx, and didn't get this "tag 258", CSL do not serialize it and it looks like:
|
Could you recheck that your code has no other tools that manipulates tx cbor |
ok confirmed. what i send:
(only see what gets submitted to the node:
there we see 2 additional entries with |
The platform is using |
hey, it's being looked into as we speak. Will be in touch when I have results. |
Thanks @kxbt-del for update |
So, the results are in - cardano-api is always adding this new optional set tag. You aren't and in cases where our platform needs to counter-sign a tx, it causes discrepancies in the calculated fees. Weird move by IOG, b/c it's obvious that this may happen if the tag is optional 😄 One thing is though - the tag is on all sets, not just vkwits, so i can see that being a "complication" |
@kxbt-del did you create an issue on cardano-api repo ? |
Since 13.0.0 all sets will be serialized with a tag 258 |
Heya, I'm testing 12.0.0-beta3 transactions against a Preview 9.1.0 node.
After upgrading all the breaking changes, submitting a minting tx results in a 44 lovelace deficit in calculated fees. I'm using
add_change_if_needed
to calculate the fees.Am I still missing something here or is there some kind of a bug present?
Error:
Transaction:
Decoded:
The text was updated successfully, but these errors were encountered: