hydra
hydra copied to clipboard
input-output-hk
Implementation of the Hydra Head protocol
Presently, it reports differences https://github.com/cardano-scaling/hydra/pull/1700#issuecomment-2410364453 - but almost all of these are because of variations in the generators, not functional changes. If possible, remove this noise by only displaying differences...
Follow-up of #1057 ### Why When implementing incremental decommits in #1344, we significantly increased the complexity of snapshots used in the `TxTrace` tests and switched from a "ahead of time"...
--- * [ ] CHANGELOG updated or not needed * [ ] Documentation updated or not needed * [ ] Haddocks updated or not needed * [ ] No new...
### Why For purposes of monitoring adoption, number of entities involved with Hydra usage and simplifying classification of the data, an opt-in naming protocol for Hydra nodes would be very...
https://github.com/input-output-hk/hydra/actions/runs/8003565955/job/21859136773 Seems like the `nix develop` invocation in the workflow fails fails to download from github when run from the workflow runner. Manually invoking `nix develop` in an interactive shell...
### Why When a Hydra head is opened, a part of the underlying ledger state gets locked up and made available off-chain to a small group of participants. While this...
## Why TODO: detail this * Making the first start experience of opening a head more delightful than using the `hydra-tui` ## What * Create or extend a web-SDK to...
Rename `ScriptInfo` to disambiguate between Hydra's ScriptInfo type and the PlutusV3 ScriptInfo type
[Hydra ScriptInfo type](https://github.com/cardano-scaling/hydra/blob/47410de12832515055295ef6af774b8075d1fb2c/hydra-plutus/src/Hydra/Contract.hs#L23) [Plutus ScriptInfo type](https://github.com/IntersectMBO/plutus/blob/f912edcc9584e0d89f8f86e4f55804d0c0aee52d/plutus-ledger-api/src/PlutusLedgerApi/V3/Contexts.hs#L444)
Metadata
Owner
Metadata
Implementation of the Hydra Head protocol