-
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
Hydra node cannot handle time conversion once 3k slots have passed #523
Conversation
This will have time conversions fail after some point
Test are still failing though ase we are passing a const time handle.
This one uses also the interpreter and is more consistent with the conversion in the other direction. Under the hood, it should be using the same functionality.
Any PastHorizonException will include these locations
This is to make clear we are actually only generating one timeHandle at a time
- We do this so that we have better access to generated system time
- getTimeHandle is now moved to TimeHandle module since arbitrary instance needs it
- getTimeHandle is now moved to TimeHandle module since arbitrary instance needs it
- Add a TODO about converting TimeHandleSpec to property test
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.
|
fix #487