Fix URLs to download software and add some help text

[ghost]

This PR depends on #1182 and seems to be needed for releasing version 0.14.0: It fixes the tutorial on Mac OS ARM64 architecture.

---

• CHANGELOG updated or not needed
• Documentation updated or not needed
• Haddocks updated or not needed
• No new TODOs introduced or explained herafter

[github-actions]

Test Results

373 tests   368 ✔️  22m 46s ⏱️
127 suites      5 💤
    5 files        0 ❌

Results for commit d718182.

♻️ This comment has been updated with latest results.

[github-actions]

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	2023-12-01 14:50:56.798016222 UTC
Max. memory units	14000000
Max. CPU units	10000000000
Max. tx size (kB)	16384

Script summary

Name	Hash	Size (Bytes)
νInitial	4868d5365af5120ae0b3c93b819d3452a3cbdcc98595da2a7ae765b5	4069
νCommit	171a1e6bdbc8aa96d957a65b3f505517386af06ba265e3f784741f67	2050
νHead	e89b0c4a6155bac2434d1e500bd49c155b2b56744ccf5a0efa72a82e	9092
μHead	6849328242b5912ad218f134378e6baff11f3e74f7e36dcf8e13d53e*	4062

• The minting policy hash is only usable for comparison. As the script is parameterized, the actual script is unique per Head.

Cost of Init Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	4589	10.87	4.31	0.47
2	4787	12.97	5.11	0.50
3	4985	15.42	6.05	0.54
5	5394	19.67	7.67	0.60
10	6395	30.76	11.90	0.77
41	12628	99.67	38.21	1.79

Cost of Commit Transaction

This is using ada-only outputs for better comparability.

UTxO	Tx size	% max Mem	% max CPU	Min fee ₳
1	532	12.22	4.81	0.31
2	720	15.93	6.48	0.36
3	907	19.77	8.20	0.41
5	1287	27.87	11.80	0.52
10	2228	50.58	21.69	0.81
18	3726	94.20	40.16	1.36

Cost of CollectCom Transaction

Parties	UTxO (bytes)	Tx size	% max Mem	% max CPU	Min fee ₳
1	57	480	22.88	9.12	0.42
2	114	590	34.80	14.01	0.56
3	170	700	48.12	19.54	0.71
4	227	810	65.89	26.83	0.91
5	283	920	83.95	34.33	1.12
6	337	1031	97.87	40.45	1.28

Cost of Close Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	483	16.11	7.02	0.35
2	759	19.47	9.98	0.41
3	934	21.10	11.56	0.45
5	1258	24.48	14.67	0.51
10	2031	32.40	22.17	0.66
50	8930	96.85	83.55	1.93

Cost of Contest Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	566	21.37	9.71	0.42
2	693	22.75	11.01	0.44
3	950	25.21	13.10	0.49
5	1260	28.75	16.26	0.56
10	2037	36.91	23.69	0.71
45	7950	98.93	79.16	1.87

Cost of Abort Transaction

Some variation because of random mixture of still initial and already committed outputs.

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	4521	20.10	8.74	0.57
2	4695	33.67	14.84	0.74
3	4846	50.30	22.29	0.93
4	4958	63.32	27.93	1.08
5	5119	84.61	37.48	1.33

Cost of FanOut Transaction

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

Parties	UTxO	UTxO (bytes)	Tx size	% max Mem	% max CPU	Min fee ₳
5	0	0	4416	8.98	3.78	0.44
5	1	57	4453	10.37	4.61	0.46
5	5	285	4597	15.70	7.84	0.54
5	10	569	4775	22.18	11.81	0.62
5	20	1139	5135	34.92	19.66	0.80
5	30	1708	5496	48.14	27.70	0.98
5	40	2278	5856	60.89	35.55	1.16
5	50	2846	6214	74.11	43.60	1.34
5	69	3927	6897	98.80	58.72	1.68

End-To-End Benchmark Results

This page is intended to collect the latest end-to-end benchmarks results produced by Hydra's Continuous Integration system from the latest master code.

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 2023-12-01 14:43:24.913373893 UTC

3-nodes Scenario

A rather typical setup, with 3 nodes forming a Hydra head.

Number of nodes	3
Number of txs	900
Avg. Confirmation Time (ms)	23.153671632
P99	118.66438093ms
P95	32.06626154999999ms
P50	19.679673ms
Number of Invalid txs	0

Baseline Scenario

This scenario represents a minimal case and as such is a good baseline against which to assess the overhead introduced by more complex setups. There is a single hydra-node d with a single client submitting single input and single output transactions with a constant UTxO set of 1.

Number of nodes	1
Number of txs	300
Avg. Confirmation Time (ms)	4.003098070
P99	6.341243419999987ms
P95	4.669076000000001ms
P50	3.8736110000000004ms
Number of Invalid txs	0

[ch1bo]

Seems like you mixed up the urls

[v0d1ch]

I guess no way to check these links before a release 📦