-
Notifications
You must be signed in to change notification settings - Fork 84
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
Align HeadLogic: Transaction pruning #740
Conversation
Transactions CostsSizes and execution budgets for Hydra protocol transactions. Note that unlisted parameters are currently using
Script summary
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.
|
297afdf
to
5ac4960
Compare
fe854de
to
2496457
Compare
5ac4960
to
7bef68a
Compare
2496457
to
6efdf2d
Compare
151fb49
to
913d27d
Compare
6efdf2d
to
79771ec
Compare
913d27d
to
cc46ab3
Compare
79771ec
to
85c7c40
Compare
c3b8845
to
42df7a6
Compare
This seems to have the exact same semantics according to our current behavior tests, but is more in-line to what is in the spec.
This also makes sure to update the seenUTxO, so might improve the "getting stuck" behavior. On the other hand, this semantics seem identical at least based in the current behavior tests.
This circumvents the "should not happen" case where a transaction `canApply`, but then it fails when we determine the new seenUTxO'.
85c7c40
to
d03d659
Compare
seenTxs
by their applicability to the new requested snapshot instead by theirEq
uality or id.[ ] CHANGELOG updated[ ] Documentation updated