-
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
feat(docs): add glossary page #494
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.
|
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 don't want to maintain two explanations of a single term.
5712445
to
027edf2
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 also tried the replacement feature as documented here https://github.com/woondossier/docusaurus-terminology#use-patterns-to-reference-a-term, but it seems not to work.
The whole plugin feels super inefficient and unnecessarily hard to maintain :(
Maybe we should just write a glossary.md
page ourselves and have it contain a single list of explanations? I don't see why we need this parsing/auto-generating of glossary page etc. -> it does not appear to be worth its weight.
027edf2
to
f4d430d
Compare
# Glossary | ||
|
||
### Contestation Period | ||
The time window between closing the head and `fan out` allowed to `contest`. |
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 is a bit unclear 🤔
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.
What about: "The time window between closing of the head and the last possible contest from a head participant."
Based on a plugin: https://gitlab.grnet.gr/terminology/docusaurus-terminology
We like to keep it simple and the plugin was too heavyweight for our use.
866ecd9
to
9ff1d83
Compare
Co-authored-by: Matthias Benkort <[email protected]>
9ff1d83
to
baee5fb
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.
Much better 😌
Fixes #495