-
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
Upper tx validity could be very big on close/contest #615
Conversation
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.
|
bd27a57
to
8bcd180
Compare
61fcaa7
to
d0ca777
Compare
d0ca777
to
aa549f4
Compare
docs/adr/CloseTx-validity-bounds-and-deadline-calculation-DoS.md
Outdated
Show resolved
Hide resolved
docs/adr/CloseTx-validity-bounds-and-deadline-calculation-DoS.md
Outdated
Show resolved
Hide resolved
7e532bd
to
97421f5
Compare
ce1d292
to
d91550e
Compare
This is required if we have long contestation periods which would exceed the time horizon in which we can convert time <-> slot. 60 seconds seems reasonable for all networks we know right now. Lower contestation periods will still use that as the delay and a user will need to pick the right --contestation-period for a network anyways.
bae846a
to
8f45cda
Compare
1f32cae
to
3030a69
Compare
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.
I think this is good to go! Minor comments and some documentation would be perfect, but also fine if you want to get it merged now.
Why
If the tx has too high upper validity bound it can cause large wait times since we are using this upper validity when checking the expected deadline.
What
Take a look at the ADR21 for context
To check before merging: