-
Notifications
You must be signed in to change notification settings - Fork 86
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
Fix some wording in the testnet tutorial #1482
Conversation
ch1bo
commented
Jul 5, 2024
- Inconsistent title
- The network we use is called 'preprod'
- Clarify that machine needs to be accessible from the internet (to connect to each other)
- Call unspent transaction outputs UTxO with lower case x as everywhere else in our docs
- CHANGELOG update not needed
- Documentation updated
- Haddocks update not needed
- No new TODOs introduced or explained herafter
- Inconsistent title - The network we use is called 'preprod' - Clarify that machine needs to be accessible from the internet (to connect to each other) - Call unspent transaction outputs UTxO with lower case x as everywhere else in our docs
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 TransactionThis is using ada-only outputs for better comparability.
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.
End-To-End Benchmark ResultsThis page is intended to collect the latest end-to-end benchmarks results produced by Hydra's Continuous Integration system from the latest Please take those results with a grain of salt as they are currently produced from very limited cloud VMs and not controlled hardware. Instead of focusing on the absolute results, the emphasis should be on relative results, eg. how the timings for a scenario evolve as the code changes. Generated at 2024-07-05 08:00:15.044198907 UTC Baseline Scenario
Three local nodes
|