Fix monitoring of confirmed snapshots

[ch1bo]

The code was too strict on tracing 'LogicOutcome's. Closes #1896

---

• CHANGELOG update not needed (fixes a bug introduced in API Server as event sink #1860)
• Documentation update not needed
• Haddocks update not needed
• No new TODOs introduced

[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	-	-	-	-
40	-	-	-	-

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	-	-	-	-	-

Cost of Increment Transaction

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

Cost of Decrement Transaction

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

Close transaction costs

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

Contest transaction costs

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

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)	-	-	-	-	-
(37, 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-03-13 17:56:31.440917352 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	0e35115a2c7c13c68ecd8d74e4987c04d4539e337643be20bb3274bd	14756
μHead	57166715eadb8d3135964325c016eea546c21e1c0aae974ca67df9a5*	5541
ν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	6093	10.80	3.35	0.53
2	6295	13.35	4.15	0.57
3	6493	15.71	4.88	0.60
5	6897	19.98	6.17	0.66
10	7904	31.18	9.61	0.82
40	13939	98.61	30.29	1.78

Commit transaction costs

This uses ada-only outputs for better comparability.

UTxO	Tx size	% max Mem	% max CPU	Min fee ₳
1	561	2.44	1.16	0.20
2	742	3.38	1.73	0.22
3	922	4.36	2.33	0.24
5	1277	6.41	3.60	0.28
10	2167	12.13	7.25	0.40
54	10068	98.61	68.52	1.88

CollectCom transaction costs

Parties	UTxO (bytes)	Tx size	% max Mem	% max CPU	Min fee ₳
1	57	525	26.44	7.58	0.44
2	113	636	34.81	9.96	0.53
3	170	747	45.83	12.98	0.65
4	228	858	54.93	15.58	0.74
5	281	969	67.53	18.99	0.88
6	339	1081	73.71	20.91	0.94
7	393	1192	76.67	22.02	0.98
9	507	1414	98.93	28.20	1.22

Cost of Increment Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	1749	24.40	7.93	0.48
2	1925	26.69	9.39	0.52
3	2017	27.63	10.26	0.54
5	2467	33.61	13.69	0.63
10	3299	45.22	20.81	0.81
38	7438	99.70	57.04	1.69

Cost of Decrement Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	604	23.99	7.61	0.43
2	747	25.63	8.73	0.45
3	824	25.35	9.29	0.46
5	1247	32.59	12.65	0.56
10	1969	42.41	18.67	0.71
39	6231	98.16	53.37	1.60

Close transaction costs

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	673	29.19	9.21	0.48
2	798	32.80	10.92	0.53
3	972	32.81	11.67	0.54
5	1291	37.14	14.42	0.61
10	2132	48.36	21.49	0.79
35	5833	99.62	54.64	1.61

Contest transaction costs

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	678	35.99	11.01	0.55
2	820	38.15	12.33	0.58
3	1030	41.02	13.96	0.63
5	1162	43.97	15.96	0.67
10	2176	59.55	24.67	0.90
27	4591	98.30	47.99	1.49

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	5976	28.29	9.32	0.71
2	6046	36.31	11.92	0.80
3	6164	45.43	14.93	0.90
4	6286	55.22	18.15	1.00
5	6450	65.76	21.66	1.12
6	6650	77.04	25.51	1.25
7	6717	86.54	28.50	1.35
8	7059	97.82	32.39	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	6091	21.04	6.93	0.64
10	1	57	6125	22.25	7.45	0.65
10	5	284	6260	30.31	10.59	0.75
10	10	570	6431	41.61	14.95	0.88
10	20	1141	6773	62.72	23.14	1.12
10	30	1704	7108	83.57	31.25	1.36
10	37	2106	7349	97.76	36.79	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-03-13 17:59:31.520687623 UTC

Baseline Scenario

Number of nodes	1
Number of txs	300
Avg. Confirmation Time (ms)	4.488506033
P99	7.06865682ms
P95	5.420751050000001ms
P50	4.3216470000000005ms
Number of Invalid txs	0

Memory data

Time	Used	Free
2025-03-13 17:58:15.547302256 UTC	942M	6192M
2025-03-13 17:58:20.547344221 UTC	1072M	6008M
2025-03-13 17:58:25.547305625 UTC	1077M	6003M
2025-03-13 17:58:30.547354355 UTC	1078M	6002M
2025-03-13 17:58:35.547344387 UTC	1081M	5998M
2025-03-13 17:58:40.547353747 UTC	1081M	5998M

Three local nodes

Number of nodes	3
Number of txs	900
Avg. Confirmation Time (ms)	28.801903690
P99	42.14914474ms
P95	37.601842000000005ms
P50	27.7992215ms
Number of Invalid txs	0

Memory data

Time	Used	Free
2025-03-13 17:58:53.600373005 UTC	978M	6110M
2025-03-13 17:58:58.600422857 UTC	1227M	5861M
2025-03-13 17:59:03.600806234 UTC	1276M	5754M
2025-03-13 17:59:08.600483322 UTC	1293M	5682M
2025-03-13 17:59:13.600412571 UTC	1302M	5672M
2025-03-13 17:59:18.600491064 UTC	1304M	5670M
2025-03-13 17:59:23.600484526 UTC	1304M	5669M
2025-03-13 17:59:28.600454353 UTC	1315M	5658M