fix tui contestation deadline

[locallycompact]

Fixes the rendering of the TUI contestation deadline

[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-10-18 15:50:55.718469767 UTC
Max. memory units	14000000
Max. CPU units	10000000000
Max. tx size (kB)	16384

Script summary

Name	Hash	Size (Bytes)
νInitial	9bad424d8a3bc67f63acfe1b015b551e84a14d7d8818204089a021b5	4120
νCommit	171a1e6bdbc8aa96d957a65b3f505517386af06ba265e3f784741f67	2050
νHead	00a8a1475bd29c02c0e3ff02a2fc83607425cd9b94eaa9f2a3056ab1	9185
μHead	16bb32b8df4dfc6cefe5bbaad9174db1b61394bdeaf1b26e83024bf6*	4150

• 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	4744	11.80	4.66	0.49
2	4948	14.35	5.64	0.52
3	5153	16.38	6.40	0.56
5	5563	20.99	8.15	0.62
10	6589	32.94	12.71	0.80
38	12331	98.22	37.59	1.76

Cost of Commit Transaction

This is using ada-only outputs for better comparability.

UTxO	Tx size	% max Mem	% max CPU	Min fee ₳
1	599	12.64	4.97	0.31
2	784	16.34	6.64	0.36
3	972	20.18	8.36	0.42
5	1350	28.20	11.93	0.52
10	2283	50.91	21.81	0.82
18	3780	94.52	40.28	1.37

Cost of CollectCom Transaction

Parties	UTxO (bytes)	Tx size	% max Mem	% max CPU	Min fee ₳
1	57	815	23.43	9.35	0.44
2	114	1135	37.16	14.94	0.61
3	170	1455	52.78	21.36	0.79
4	227	1774	72.82	29.54	1.03
5	283	2104	91.36	37.30	1.25

Cost of Close Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	693	18.76	8.66	0.39
2	914	20.42	10.22	0.43
3	1121	22.56	11.94	0.47
5	1588	25.67	15.00	0.54
10	2722	34.18	22.87	0.71
50	10759	98.65	82.11	2.01

Cost of Contest Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	749	22.97	10.27	0.44
2	911	23.92	11.37	0.47
3	1168	26.69	13.52	0.51
5	1590	29.62	16.32	0.58
10	2744	39.74	24.88	0.77
43	9332	95.68	74.36	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	4967	21.12	9.14	0.61
2	5388	35.46	15.54	0.79
3	5825	53.30	23.49	1.01
4	6309	73.74	32.62	1.26
5	6459	89.95	39.64	1.45

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	4771	8.81	3.73	0.46
5	1	57	4802	9.98	4.47	0.47
5	5	285	4950	15.30	7.70	0.55
5	10	570	5123	21.65	11.61	0.63
5	20	1137	5484	34.76	19.61	0.81
5	30	1706	5841	47.51	27.45	0.99
5	40	2271	6199	60.72	35.50	1.17
5	50	2846	6564	73.58	43.40	1.35
5	70	3986	7281	99.71	59.37	1.70

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-10-18 15:43:07.024118921 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)	75.546026545
P99	182.2727718099999ms
P95	147.49526074999997ms
P50	67.5212445ms
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)	10.422311616
P99	23.04449579999997ms
P95	20.2734959ms
P50	8.819961ms
Number of Invalid txs	0