hydra
hydra copied to clipboard
input-output-hk
Implementation of the Hydra Head protocol
## Why Transactions driving the head state-machine may not end up in a block even though they have been submitted successfully for a variety of reasons (local rollback, forks later...
## Why In the work stream to mature the Hydra Head protocol enough to aim for a mainnet release, we have been [running our implementation against a formal model](https://github.com/input-output-hk/hydra-poc/issues/194) and...
## Why Although the Hydra Head protocol has been peer-reviewed as a [research paper](https://eprint.iacr.org/2020/299.pdf) and the security it provides proven, this does not guarantee our implementation indeed provides the same...
## Why The current implementation of the Hydra Head cannot always abort a Head initialization. This is because the abort transaction is too big (> 16kB), especially if all it's...
## What & Why We want Hydra Heads to be secure. This means that we can close & fan out the L2 state at any point throughout the life-cycle of...
We might have a bigger problem on our strategy with `--start-chain-from`: Today, we wanted to start a hydra node from the beginning of the devnet to recover/see an already open...
## Why To optimize resource usage, users might want to have a single `hydra-node` be able to maintain and interact with multiple Hydra heads. If the peer nodes of multiple...
Using the same model as #375, but with the `Hydra.Chain.Direct` transaction construction and observation interleaved when performing the state transitions. This should include transaction validation (phase 1 + 2) in...
## Why * streamline, simplify, enable open-source contributions * that for, a potential IO internal user: Marlowe will be a guest and evaluate Hydra as a potential puzzle piece in...
## What & Why How we deal with changes and upgrades to various parts of the Hydra system. This is only about changes we issue, for Cardano network changes, see:...
Metadata
Owner
Metadata
Implementation of the Hydra Head protocol