Fix for the hydrate function and 0.22.1 release

[noonio]

This is a small patch release (+ the code itself) to fix the ReplayingState stalling bug that was being observed.

There is some follow-up work to be done in #2086 ; but this never-the-less represents an improvement.

Fixes #2089

[github-actions]

Transaction cost differences

No cost or size differences found

[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-06-27 14:33:40.679742352 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	be6ebc744208c660bf0fdc1cfbb5157477cd305de5b1777e575cbb4c	14665
μHead	1f47a42d1d6edc32ccd834acb19d5db3b2a5232f0bd7eaa8908dc519*	5284
ν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	5836	10.52	3.34	0.52
2	6039	12.75	4.05	0.55
3	6239	14.68	4.64	0.58
5	6645	18.38	5.79	0.63
10	7646	29.35	9.26	0.79
43	14279	98.73	30.85	1.80

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	739	3.38	1.73	0.22
3	917	4.36	2.33	0.24
5	1276	6.41	3.60	0.28
10	2173	12.13	7.25	0.40
54	10078	98.61	68.52	1.88

CollectCom transaction costs

Parties	UTxO (bytes)	Tx size	% max Mem	% max CPU	Min fee ₳
1	56	524	24.43	7.12	0.42
2	114	636	33.33	9.64	0.52
3	169	747	44.00	12.61	0.63
4	227	858	53.82	15.31	0.73
5	284	974	56.00	16.22	0.76
6	338	1081	71.89	20.52	0.93
7	394	1192	84.67	23.95	1.06
8	452	1303	87.61	25.10	1.10

Cost of Increment Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	1748	22.83	7.57	0.47
2	1886	24.73	8.81	0.50
3	2052	26.85	10.23	0.53
5	2322	29.78	12.50	0.58
10	3225	41.10	19.70	0.77
43	7856	98.36	60.13	1.72

Cost of Decrement Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	606	22.77	7.34	0.41
2	807	25.45	8.75	0.45
3	946	26.60	9.75	0.48
5	1136	28.04	11.45	0.51
10	2068	41.77	18.64	0.71
40	6497	98.92	54.49	1.63

Close transaction costs

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	673	27.37	8.80	0.46
2	794	30.76	10.46	0.51
3	868	31.84	11.36	0.53
5	1281	34.75	13.88	0.59
10	1998	43.83	20.15	0.74
36	5890	95.26	54.43	1.57

Contest transaction costs

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	676	33.69	10.49	0.53
2	842	35.73	11.79	0.56
3	954	37.70	13.05	0.59
5	1291	42.47	15.95	0.67
10	1973	53.06	22.60	0.83
29	5060	99.14	50.28	1.54

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	5783	27.01	9.04	0.69
2	5971	36.65	12.33	0.80
3	5976	41.43	13.83	0.85
4	6141	53.45	17.86	0.98
5	6372	64.11	21.54	1.10
6	6478	70.84	23.87	1.18
7	6531	78.95	26.47	1.27
8	6856	95.30	32.09	1.45
9	6759	98.12	32.87	1.48

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	5834	19.19	6.41	0.61
10	1	57	5868	21.67	7.37	0.64
10	5	284	6003	30.24	10.74	0.74
10	10	570	6174	39.52	14.45	0.85
10	20	1138	6512	60.46	22.69	1.09
10	30	1705	6852	79.83	30.38	1.32
10	39	2216	7155	98.55	37.75	1.53

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-06-27 14:37:32.158107729 UTC

Baseline Scenario

Number of nodes	1
Number of txs	300
Avg. Confirmation Time (ms)	4.527261560
P99	9.472089849999989ms
P95	5.682182550000001ms
P50	4.280053499999999ms
Number of Invalid txs	0

Memory data

Time	Used	Free
2025-06-27 14:36:15.905870116 UTC	0m	0;
2025-06-27 14:36:20.905915604 UTC	3	0;
2025-06-27 14:36:25.905830319 UTC	8	0;
2025-06-27 14:36:30.905890679 UTC	1	0;
2025-06-27 14:36:35.905783128 UTC	1	0;
2025-06-27 14:36:40.905882046 UTC	1	0;

Three local nodes

Number of nodes	3
Number of txs	900
Avg. Confirmation Time (ms)	29.868759188
P99	49.10912783999998ms
P95	41.93480045ms
P50	28.170433ms
Number of Invalid txs	0

Memory data

Time	Used	Free
2025-06-27 14:36:54.901604676 UTC	0m	0;
2025-06-27 14:36:59.901708739 UTC	3	0;
2025-06-27 14:37:04.902083128 UTC	4	0;
2025-06-27 14:37:09.901750788 UTC	21	0;
2025-06-27 14:37:14.901742649 UTC	19	0;
2025-06-27 14:37:19.901790532 UTC	2	0;
2025-06-27 14:37:24.90173427 UTC	2	0;
2025-06-27 14:37:29.901738652 UTC	2	0;