Skip to content
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

the alonzo UTxO rule to use alonzo minfee function #2938

Merged
merged 1 commit into from
Jul 28, 2022

Conversation

JaredCorduan
Copy link
Contributor

This PR cherry picks the commit from #2936 for the release branch release/1.0.0. The cherry pick required a bit of massaging due to the glorious recent cleanup in #2901, but can be compared line by line with #2936 to check that is is semantically the same.

Additionally, a new golden test for the alonzo fee calculation has been
added, using the block from:
IntersectMBO/cardano-node#4228 (comment)
Copy link
Contributor

@teodanciu teodanciu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Diffing the diffs, I noticed that this PR adds HasField "txrdmrs" (Core.Witnesses era) (Redeemers era) to feesOK function, whereas #2936 didn't.
Also, in #2936, HasField "_prices" was added as constraints to utxoTransition and STS (AlonzoUTXO era) instance, whereas in this PR we're only adding it to feesOK. Perhaps these are necessary because of the other changes that were left behind on this branch!
The rest looks the same to me 👍

@JaredCorduan
Copy link
Contributor Author

I am going to merge, even though ci/hydra:Cardano:cardano-ledger-specs:required is reporting Pending. If you follow the link, all the tests have actually passed.

@JaredCorduan JaredCorduan merged commit c7c63da into release/1.0.0 Jul 28, 2022
@iohk-bors iohk-bors bot deleted the jc/fix-alonzo-minfee-on-release-1-0-0 branch July 28, 2022 20:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants