Skip to content
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

Changelog updates & demo fixes #459

Merged
merged 3 commits into from
Aug 16, 2022
Merged

Changelog updates & demo fixes #459

merged 3 commits into from
Aug 16, 2022

Conversation

ch1bo
Copy link
Member

@ch1bo ch1bo commented Aug 16, 2022

⛵ Updated changelog with recent reference script changes

⛵ Make seed-devnet.sh usable without docker and update instructions

ch1bo added 3 commits August 15, 2022 18:53
Also ignore the testnet/ vasil-testnet/ directories by default.
This was not the case anymore due to the docker run for hydra-node. The
current solution is not perfect, but follows the same scheme as used for
the cardano-cli. An alternative could be to have more granular
instructions.


```mdx-code-block
<TerminalWindow>
./seed-devnet.sh $(which cardano-cli)
export CARDANO_NODE_SOCKET_PATH=devnet/ipc/node.socket
./seed-devnet.sh $(which cardano-cli) "cabal exec hydra-node --"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is slightly weird 🤔 ... Why not $(which hydra-node) too for consistency? I mean, this boils down to the same thing given how it is invoked but, I don't know, the example feels off to me 😅

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is kind of highlighting both ways. The hydra-node executable would only be in scope if one would be using the nix-shell -A demo environment and below we also use cabal exec invocations. Not sure which way is more clear 🤷

@github-actions
Copy link

Transactions Costs

Sizes and execution budgets for Hydra protocol transactions. Note that unlisted parameters are currently using arbitrary values and results are not fully deterministic and comparable to previous runs.

Metadata
Generated at 2022-08-16 09:43:13.84878384 UTC
Max. memory units 14000000.00
Max. CPU units 10000000000.00
Max. tx size (kB) 16384

Cost of Init Transaction

Parties Tx size % max Mem % max CPU
1 4832 9.43 3.72
2 5038 12.47 4.92
3 5247 14.09 5.53
5 5651 17.02 6.63
10 6678 28.22 10.99
46 14060 99.01 38.25

Cost of Commit Transaction

Currently only one UTxO per commit allowed (this is about to change soon)

UTxO Tx size % max Mem % max CPU
1 5771 19.86 8.01

Cost of CollectCom Transaction

Parties Tx size % max Mem % max CPU
1 13057 20.68 8.29
2 13378 36.46 14.76
3 13771 56.27 22.97
4 14023 76.28 31.28

Cost of Close Transaction

Parties Tx size % max Mem % max CPU
1 9260 7.59 2.99
2 9492 8.97 3.81
3 9720 10.58 4.59
5 10052 12.14 5.49
10 10883 16.27 7.84
30 14181 31.68 16.79
71 16305 41.90 15.86

Cost of Contest Transaction

Parties Tx size % max Mem % max CPU
1 9363 8.60 3.51
2 9528 9.34 3.95
3 9658 9.72 4.24
5 10022 11.72 5.32
10 10882 16.20 7.80
30 14220 32.42 17.07
43 16369 42.78 23.03

Cost of Abort Transaction

Parties Tx size % max Mem % max CPU
1 13494 22.50 9.35
2 14028 43.12 18.94
3 14279 61.24 26.81
4 14323 77.49 33.90

Cost of FanOut Transaction

Involves spending head output and burning head tokens. Uses ada-only UTxO for better comparability.

UTxO Tx size % max Mem % max CPU
1 13549 10.64 4.61
2 13456 11.40 5.19
3 13556 13.55 6.32
5 13564 15.96 7.83
10 13866 24.63 12.64
50 15245 84.88 47.60
59 15571 98.85 55.63

@github-actions
Copy link

Unit Test Results

247 tests  ±0   241 ✔️ ±0   12m 47s ⏱️ +6s
  89 suites ±0       6 💤 ±0 
    5 files   ±0       0 ±0 

Results for commit 4d87bf2. ± Comparison against base commit 5d4369e.

@ch1bo ch1bo merged commit 1e7a7d1 into master Aug 16, 2022
@ch1bo ch1bo deleted the ch1bo/demo-fixes branch August 16, 2022 21:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants