Conversation
awcjack
commented
Mar 30, 2026
- CHANGELOG updated or not needed
- Documentation updated or not needed
- Haddocks updated or not needed
- No new TODOs introduced or explained herafter
Transaction costsSizes and execution budgets for Hydra protocol transactions. Note that unlisted parameters are currently using
Script summary
|
| Parties | Tx size | % max Mem | % max CPU | Min fee ₳ |
|---|---|---|---|---|
| 1 | 5837 | 10.64 | 3.38 | 0.52 |
| 2 | 6035 | 12.25 | 3.87 | 0.54 |
| 3 | 6242 | 14.29 | 4.51 | 0.57 |
| 5 | 6640 | 18.62 | 5.87 | 0.64 |
| 10 | 7647 | 28.94 | 9.11 | 0.79 |
| 43 | 14281 | 98.99 | 30.94 | 1.80 |
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 | 738 | 3.38 | 1.73 | 0.22 |
| 3 | 920 | 4.36 | 2.33 | 0.24 |
| 5 | 1283 | 6.41 | 3.60 | 0.28 |
| 10 | 2173 | 12.13 | 7.25 | 0.40 |
| 54 | 10066 | 98.61 | 68.52 | 1.88 |
CollectCom transaction costs
| Parties | UTxO (bytes) | Tx size | % max Mem | % max CPU | Min fee ₳ |
|---|---|---|---|---|---|
| 1 | 57 | 525 | 18.29 | 5.75 | 0.36 |
| 2 | 114 | 640 | 25.34 | 7.88 | 0.44 |
| 3 | 170 | 747 | 30.06 | 9.39 | 0.49 |
| 4 | 228 | 858 | 38.53 | 11.89 | 0.59 |
| 5 | 281 | 969 | 45.69 | 14.05 | 0.66 |
| 6 | 337 | 1081 | 48.74 | 15.17 | 0.70 |
| 7 | 393 | 1192 | 55.19 | 17.18 | 0.77 |
| 8 | 450 | 1303 | 74.56 | 22.55 | 0.97 |
| 9 | 505 | 1414 | 75.77 | 23.09 | 0.99 |
Cost of Increment Transaction
| Parties | Tx size | % max Mem | % max CPU | Min fee ₳ |
|---|---|---|---|---|
| 1 | 1817 | 17.89 | 6.25 | 0.42 |
| 2 | 1941 | 18.98 | 7.24 | 0.44 |
| 3 | 2216 | 21.64 | 8.71 | 0.49 |
| 5 | 2378 | 23.58 | 10.61 | 0.52 |
| 10 | 3221 | 30.77 | 16.11 | 0.66 |
| 50 | 9422 | 91.00 | 60.67 | 1.74 |
Cost of Decrement Transaction
| Parties | Tx size | % max Mem | % max CPU | Min fee ₳ |
|---|---|---|---|---|
| 1 | 623 | 16.65 | 6.00 | 0.36 |
| 2 | 783 | 18.77 | 7.27 | 0.39 |
| 3 | 877 | 19.04 | 8.02 | 0.40 |
| 5 | 1243 | 21.45 | 10.06 | 0.45 |
| 10 | 1855 | 27.05 | 15.06 | 0.56 |
| 50 | 8097 | 87.55 | 59.68 | 1.64 |
Close transaction costs
| Parties | Tx size | % max Mem | % max CPU | Min fee ₳ |
|---|---|---|---|---|
| 1 | 643 | 21.93 | 7.29 | 0.41 |
| 2 | 807 | 23.31 | 8.36 | 0.43 |
| 3 | 1067 | 24.37 | 9.39 | 0.46 |
| 5 | 1373 | 26.98 | 11.50 | 0.51 |
| 10 | 2092 | 34.49 | 17.09 | 0.64 |
| 50 | 8034 | 96.35 | 62.19 | 1.73 |
Contest transaction costs
| Parties | Tx size | % max Mem | % max CPU | Min fee ₳ |
|---|---|---|---|---|
| 1 | 625 | 24.80 | 8.08 | 0.44 |
| 2 | 852 | 27.41 | 9.55 | 0.48 |
| 3 | 997 | 28.95 | 10.66 | 0.50 |
| 5 | 1203 | 31.53 | 12.73 | 0.55 |
| 10 | 2127 | 41.97 | 19.21 | 0.72 |
| 42 | 6859 | 99.75 | 57.53 | 1.67 |
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 | 5818 | 23.74 | 8.34 | 0.66 |
| 2 | 5955 | 31.46 | 11.08 | 0.75 |
| 3 | 6063 | 38.82 | 13.72 | 0.83 |
| 4 | 6283 | 48.54 | 17.24 | 0.94 |
| 5 | 6370 | 54.22 | 19.18 | 1.01 |
| 6 | 6590 | 63.62 | 22.50 | 1.12 |
| 7 | 6701 | 71.09 | 25.07 | 1.20 |
| 8 | 6886 | 83.46 | 29.41 | 1.34 |
| 9 | 6818 | 82.01 | 28.86 | 1.32 |
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 | 17.66 | 6.12 | 0.59 |
| 10 | 10 | 570 | 6174 | 36.12 | 13.80 | 0.81 |
| 10 | 20 | 1137 | 6511 | 53.09 | 20.93 | 1.02 |
| 10 | 45 | 2562 | 7363 | 99.27 | 40.08 | 1.57 |
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 2026-03-30 10:44:42.167806677 UTC
Baseline Scenario
| Number of nodes | 1 |
|---|---|
| Number of txs | 300 |
| Avg. Confirmation Time (ms) | 5.978716876 |
| P99 | 11.788842709999992ms |
| P95 | 8.763637750000001ms |
| P50 | 5.5088360000000005ms |
| Number of Invalid txs | 0 |
| Fanout outputs | 1 |
Three local nodes
| Number of nodes | 3 |
|---|---|
| Number of txs | 900 |
| Avg. Confirmation Time (ms) | 50.022836818 |
| P99 | 82.40000745ms |
| P95 | 70.41665034999998ms |
| P50 | 48.4068665ms |
| Number of Invalid txs | 0 |
| Fanout outputs | 3 |