|
1 | | -# Known issues & limitations |
| 1 | +# Known issues and limitations |
2 | 2 |
|
3 | | -Please be aware of the following known issues and limitations before running `hydra-node` on the Cardano `--mainnet`; as an incredibly technical project, Hydra in its current form requires an elevated level of understanding of the underlying infrastructure. Without the expertise required to operate a `hydra-node`, users may put their funds at risk if they are unfamiliar with the implementation and usage process. |
| 3 | +Before running a Hydra node on the Cardano mainnet, it is important to be aware of several known issues and limitations. Operating a Hydra node requires a deep understanding of the underlying infrastructure, and you may risk your funds if you are unfamiliar with the implementation and usage processes. |
4 | 4 |
|
5 | 5 | ### Head protocol limits |
6 | 6 |
|
7 | | -As transaction sizes and execution budgets are limited on Cardano: |
| 7 | +Due to the limitations on transaction sizes and execution budgets on Cardano, the Hydra protocol has the following constraints: |
8 | 8 |
|
9 | | -- The protocol can only handle a maximum number of participants in a Head (see [cost of collectcom transaction](/benchmarks/transaction-cost/#cost-of-collectcom-transaction)). Upon startup, the `hydra-node` will inform you of the current configured maximum when trying to configure too many peers. |
| 9 | +- The protocol can only handle a maximum number of participants in a head see [the cost of CollectCom transaction](https://hydra.family/head-protocol/unstable/benchmarks/transaction-cost/#cost-of-collectcom-transaction). When attempting to configure too many peers, the Hydra node will inform you of the current configured maximum. |
10 | 10 |
|
11 | | -It's currently possible to be denied access to funds by other protocol participants at various stages in a Hydra Head because of the complexity or size of the UTxO being committed or created while the Head is open: |
| 11 | +Currently, participants may be denied access to their funds by other protocol participants at different stages within a Hydra head because of the complexity or size of the UTXO being committed or created while the head is open: |
12 | 12 |
|
13 | | -- The head cannot be _finalized_ if holding more than ~80 assets (see [cost of fanout transaction](https://hydra.family/head-protocol/benchmarks/transaction-cost/#cost-of-fanout-transaction) for latest numbers), although it can be _closed_ |
14 | | -- Tokens minted and not burnt in an _open_ head will prevent it from being _finalized_ |
15 | | -- If one or more participants commit UTxO too large to be processed together in a `CollectCom` or `Abort` transaction, the Head will be stuck in the _initialising_ stage |
| 13 | +- The Hydra head cannot be _finalized_ if it holds more than approximately 80 assets (see [the cost of FanOut transaction](https://hydra.family/head-protocol/benchmarks/transaction-cost/#cost-of-fanout-transaction) for latest numbers), although it can be _closed_ |
| 14 | +- Tokens that are minted and not burned within an open Hydra head will prevent the head from being _finalized_ |
| 15 | +- If one or more participants commit UTXOs that are too large to be processed together in a `CollectCom` or `Abort` transaction, the Hydra head will remain stuck in the _initialising_ stage. |
16 | 16 |
|
17 | | -There are couple of items in the roadmap around reducing the risk of locking up funds in a Hydra Head: |
| 17 | +See these resources for additional information about reducing the risk of locking up funds in a Hydra head: |
18 | 18 |
|
19 | | -- [Directly open heads](https://github.com/input-output-hk/hydra/issues/1329) |
20 | | -- [Always abortable Head](https://github.com/input-output-hk/hydra/issues/699) |
21 | | -- [Limit size/complexity of UTxOs in the Head](https://github.com/input-output-hk/hydra/issues/698) |
22 | | -- [Only sign closable snapshots](https://github.com/input-output-hk/hydra/issues/370) |
| 19 | +* [Directly open heads](https://github.com/input-output-hk/hydra/issues/1329) |
| 20 | +* [Always abortable head](https://github.com/input-output-hk/hydra/issues/699) |
| 21 | +* [Limit size/complexity of UTXOs in the head](https://github.com/input-output-hk/hydra/issues/698) |
| 22 | +* [Only sign closable snapshots](https://github.com/input-output-hk/hydra/issues/370) |
23 | 23 |
|
24 | 24 | ### Training wheels |
25 | 25 |
|
26 | | -- There is a hard-coded limit on **mainnet** network where you can |
27 | | - only commit up to 100 ADA into the Hydra head. This is only a safety |
28 | | - precaution and is going to be increased as we gain more experience |
29 | | - in running Hydra heads on the mainnet. |
30 | | - |
| 26 | +There is a hard-coded limit on the **mainnet** where only up to 100 ada can be committed into the Hydra head. This is a safety precaution and will be increased as more experience is gained in running Hydra heads on the mainnet. |
| 27 | + |
31 | 28 | ### Known bugs |
32 | 29 |
|
33 | | -Refer also to the project repository issue tracker for [known issues](https://github.com/input-output-hk/hydra/issues?q=is%3Aissue+is%3Aopen+label%3A%22bug+%3Abug%3A%22) with the code. Should you discover any security relevant problems, please follow our [security policy](https://github.com/input-output-hk/hydra?tab=security-ov-file#readme). |
| 30 | +Refer to the project repository issue tracker for [known issues](https://github.com/input-output-hk/hydra/issues?q=is%3Aissue+is%3Aopen+label%3A%22bug+%3Abug%3A%22). If you discover any security-relevant problems, please follow our [security policy](https://github.com/input-output-hk/hydra?tab=security-ov-file#readme). |
0 commit comments