hydra
hydra copied to clipboard
Implementation of the Hydra Head protocol
## Why Clients might have different requirements about the data they want from our API Server: * Some might not want to be fed the history of previous messages when...
## Why Hydra Heads should not need to be closed and re-opened just to add more funds. This will make Hydra Heads more flexible in enables use cases where long-living...
## What & Why We extend our [current benchmark](https://github.com/input-output-hk/hydra-poc/tree/73c209048479190f86e64857f101ec086365dbe4/hydra-cluster/bench) suite with **two** concrete scenarios to measure latency & throughput of actual Hydra Head configurations and transaction structure. Given the current...
## What & Why Currently, there is no mechanism to recover the current state of a Hydra Head when restarting the `hydra-node` (e.g. following a crash). As a consequence, the...
## Why * The `ServerOutput` data provides `Seen` and `Confirmed` transactions in a custom JSON format described in our [API doc](https://hydra.family/head-protocol/api-reference) * This makes integration with pre-existing thirdparty tools like...
## Why & What Currently, when a client connect (via WebSocket) to a Hydra node, the server replays the entire history of event through the connection. This is meant to...
## What & Why Although the ledger implementation used in the `hydra-node` is the same as in `cardano-node`, not all ledger rules make sense in a Hydra Head. For example,...
## What & Why This idea is based on a discussion between @KtorZ and @Quantumplation on what they called "phantom tokens": Generically minting assets in a Hydra Head would render...
## What & Why As a user if I want to commit inside a Head, I would need to send whatever I want to commit first to the internal wallet...
This can only be done when `v_head` is not parameterized by the initial/commit `Address` anymore. We would exchange finding inputs in collectCom/abort by address with finding them by looking at...