Quickfix for the network tests to use the correct format for the published script addresses

[noonio]

The recent PR #1782 removed behaviour that the network tests relied on (as they use the latest code from this repo) but broke the demo.

I think the essential lesson is at least a few things:

1. We need to test the demo in CI
2. One script doing two things is confusing

[github-actions]

Transaction cost differences

Script summary

Name	Size (Bytes)
νInitial	-
νCommit	-
νHead	-
μHead	-
νDeposit	-

Init transaction costs

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	-	-	-	-
2	-	-	-	-
3	-	-	-	-
5	-	-	-	-
10	-	-	-	-
44	-	-	-	-

Commit transaction costs

UTxO	Tx size	% max Mem	% max CPU	Min fee ₳
1	-	-	-	-
2	-	-	-	-
3	-	-	-	-
5	-	-	-	-
10	-	-	-	-
54	-	-	-	-

CollectCom transaction costs

Parties	UTxO (bytes)	Tx size	% max Mem	% max CPU	Min fee ₳
1	-	-	-	-	-
2	-	-	-	-	-
3	-	-	-	-	-
4	-	-	-	-	-
5	-	-	-	-	-
6	-	-	-	-	-
7	-	-	-	-	-
8	-	-	-	-	-
9	-	-	-	-	-
10	-	-	-	-	-

Cost of Increment Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	-	-	-	-
2	-	-	-	-
3	-	+0.38	+0.09	-
5	-	+0.39	+0.09	-
10	-	-	-	-
43	-	-	-	-

Cost of Decrement Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	-	-	-	-
2	-	-	-	-
3	-	-	-	-
5	-	-	-	-
10	-	-	-	-
45	-	-	-	-

Close transaction costs

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	-	-	-	-
2	-	-	-	-
3	-	-	-	-
5	-	-	-	-
10	-	-	-	-
41	-	-	-	-

Contest transaction costs

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	-	-	-	-
2	-	-	-	-
3	-	-	-	-
5	-	-	-	-
10	-	-	-	-
33	-	-	-	-

FanOut transaction costs

UTxO, Parties	UTxO (bytes)	Tx size	% max Mem	% max CPU	Min fee ₳
(0, 10)	-	-	-	-	-
(1, 10)	-	-	-	-	-
(5, 10)	-	-	-	-	-
(10, 10)	-	-	-	-	-
(20, 10)	-	-	-	-	-
(40, 10)	-	-	-	-	-
(41, 10)	-	-	-	-	-

[github-actions]

Transaction 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	2025-01-13 15:05:53.328735453 UTC
Max. memory units	14000000
Max. CPU units	10000000000
Max. tx size (kB)	16384

Script summary

Name	Hash	Size (Bytes)
νInitial	c8a101a5c8ac4816b0dceb59ce31fc2258e387de828f02961d2f2045	2652
νCommit	61458bc2f297fff3cc5df6ac7ab57cefd87763b0b7bd722146a1035c	685
νHead	5350e9d521552ebfd9e846fd70c3b801f716fc14296134ec0fb71e97	14492
μHead	6b49dc4e571207d615dba01996548cb610b0caa85c30423d169d0091*	5612
νDeposit	ae01dade3a9c346d5c93ae3ce339412b90a0b8f83f94ec6baa24e30c	1102

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

Init transaction costs

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	6165	10.33	3.30	0.53
2	6365	12.04	3.82	0.56
3	6566	14.09	4.46	0.59
5	6969	18.52	5.87	0.65
10	7974	28.88	9.14	0.80
44	14814	98.21	30.92	1.82

Commit transaction costs

This uses ada-only outputs for better comparability.

UTxO	Tx size	% max Mem	% max CPU	Min fee ₳
1	558	2.44	1.16	0.20
2	743	3.38	1.73	0.22
3	920	4.36	2.33	0.24
5	1276	6.41	3.60	0.28
10	2176	12.13	7.25	0.40
54	10061	98.61	68.52	1.88

CollectCom transaction costs

Parties	UTxO (bytes)	Tx size	% max Mem	% max CPU	Min fee ₳
1	57	525	25.04	7.27	0.43
2	114	636	32.98	9.56	0.51
3	171	747	39.93	11.64	0.59
4	228	862	51.86	14.84	0.71
5	283	969	60.52	17.37	0.81
6	339	1081	75.14	21.23	0.96
7	396	1192	75.74	21.73	0.97
8	450	1303	87.34	25.04	1.09

Cost of Increment Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	1797	23.75	7.93	0.48
2	2001	26.18	9.45	0.52
3	2107	28.08	10.67	0.55
5	2453	31.47	13.20	0.61
10	2977	36.99	18.14	0.71
44	8089	98.26	61.21	1.74

Cost of Decrement Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	594	22.40	7.25	0.41
2	734	23.47	8.19	0.43
3	853	24.96	9.27	0.46
5	1341	33.15	12.91	0.57
10	2128	42.12	18.76	0.72
45	6994	98.07	57.78	1.67

Close transaction costs

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	684	26.99	8.72	0.46
2	741	29.74	10.07	0.50
3	948	30.21	11.07	0.52
5	1176	35.60	13.99	0.59
10	2034	43.64	20.26	0.74
37	6073	94.39	55.24	1.58

Contest transaction costs

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	683	33.35	10.42	0.52
2	803	35.29	11.68	0.55
3	895	36.73	12.68	0.58
5	1271	41.65	15.75	0.66
10	2087	53.55	23.14	0.84
32	5319	99.47	52.56	1.57

Abort transaction costs

There is some variation due to the random mixture of initial and already committed outputs.

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	6078	26.12	8.85	0.69
2	6186	34.60	11.72	0.79
3	6302	43.58	14.73	0.89
4	6451	52.87	17.89	0.99
5	6648	63.18	21.42	1.11
6	6633	69.69	23.48	1.17
7	6876	79.74	26.99	1.29
8	6876	82.59	27.92	1.32
9	6979	90.85	30.63	1.41

FanOut transaction costs

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 ₳
10	0	0	6163	17.82	6.07	0.61
10	5	284	6331	27.98	10.15	0.73
10	10	570	6502	37.77	14.09	0.84
10	30	1711	7186	77.15	29.92	1.31
10	40	2275	7519	96.02	37.53	1.53
10	41	2337	7558	98.50	38.51	1.56

End-to-end benchmark results

This page is intended to collect the latest end-to-end benchmark results produced by Hydra's continuous integration (CI) system from the latest master code.

Please note that these results are approximate as they are currently produced from limited cloud VMs and not controlled hardware. Rather than focusing on the absolute results, the emphasis should be on relative results, such as how the timings for a scenario evolve as the code changes.

Generated at 2025-01-13 15:08:57.642566726 UTC

Baseline Scenario

Number of nodes	1
Number of txs	300
Avg. Confirmation Time (ms)	5.252127000
P99	10.79313971999999ms
P95	6.695189250000002ms
P50	5.0127690000000005ms
Number of Invalid txs	0

Three local nodes

Number of nodes	3
Number of txs	900
Avg. Confirmation Time (ms)	24.201943877
P99	120.68468542999997ms
P95	31.009685399999995ms
P50	21.395542ms
Number of Invalid txs	0

[github-actions]

Test Results

  5 files  ±0  165 suites  ±0   31m 54s ⏱️ +51s
561 tests ±0  559 ✅ ±0  2 💤 ±0  0 ❌ ±0 
563 runs  ±0  561 ✅ ±0  2 💤 ±0  0 ❌ ±0 

Results for commit a8f6f52. ± Comparison against base commit 5748b3c.

♻️ This comment has been updated with latest results.