-
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
Implement liveness property in dynamic logic #497
Conversation
Also update iohkNix to not get a deprecation warning from the crypto overlay.
…dency Getting the package from hackage is not a problem, but our upstream dependencies are not fit for latest hackage versions and we did not want to bother chasing constraints at this point.
This is due to the new 1.0.0 interface of quickcheck-dynamic
This kind of duplicates ClientInput
Unfortunately, this was requiring to ditch record syntax as GADTs seem not to allow duplicate record fields with differing return types.
This keeps the conversion back to simple utxos out of the model.
Instead of requiring a Show instance on monitoring function we can pattern match as suggested by Max.
This gives us a Show instance for monitoring failures
…ition in the model
This requires introduction of 2 new actions in the model: * Wait to give the underlying runner time to process messages * ObserveConfirmedTx to check what's been observed by each node
st <- getModelStateDL | ||
(party, payment) <- forAllQ (withGenQ (genPayment st) (const [])) | ||
let newTx = Model.NewTx party payment | ||
action newTx |
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.
Could: inline newTx
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.
Thanks. This PR is still a draft, I just refreshed it following a discussion we had with @pgrange who was interested in having a look at what we are currently working on concretely.
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 #467