-
Notifications
You must be signed in to change notification settings - Fork 88
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
Mutation framework improval #679
Conversation
There is no point in mutating transactions to be come inconsistent. Instead we want to focus on mutating to expose flaws in our plutus scripts.
This should not correctly update the transaction inputs while keeping the redeemer pointers consistent.
This would result in a problem with redeemers.
Transactions CostsSizes and execution budgets for Hydra protocol transactions. Note that unlisted parameters are currently using
Cost of Init Transaction
Cost of Commit TransactionCurrently only one UTxO per commit allowed (this is about to change soon)
Cost of CollectCom Transaction
Cost of Close Transaction
Cost of Contest Transaction
Cost of Abort TransactionSome variation because of random mixture of still initial and already committed outputs.
Cost of FanOut TransactionInvolves spending head output and burning head tokens. Uses ada-only UTxO for better comparability.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good. Although I would prefer the Maybe Text
to be after the label.. but this can be done in another PR.
Improve the Mutation framework by adding optional error messages to make sure we are failing for the right reason.
To check before merging: