From 3e7bd6bea84002d316c138f54a18e4d250326ccf Mon Sep 17 00:00:00 2001 From: Sebastian Nagel Date: Thu, 11 Jul 2024 09:46:33 +0200 Subject: [PATCH] Update org/repository links (#1493) Kept some of the old docker image references on input-output-hk as these docker images don't exist in the new org. --- .github/ISSUE_TEMPLATE/config.yaml | 6 +- .github/ISSUE_TEMPLATE/feature_idea.yml | 2 +- .github/workflows/README.md | 2 +- .github/workflows/docker.yaml | 2 +- .../workflows/explorer/docker-compose.yaml | 2 +- .github/workflows/publish-docs.yaml | 2 +- CHANGELOG.md | 214 +++++++++--------- CONTRIBUTING.md | 14 +- README.md | 12 +- SECURITY.md | 6 +- SUPPORT.md | 4 +- cardano-api-classy/cardano-api-classy.cabal | 2 +- demo/docker-compose.yaml | 12 +- demo/seed-devnet.sh | 2 +- ...1-11-25_012-top-down-test-driven-design.md | 2 +- .../adr/2022-02-14_014-hydra-script-tokens.md | 4 +- docs/adr/2022-03-17_015-admin-api.md | 2 +- docs/adr/2022-04-13_018-single-state.md | 4 +- .../adr/2022-12-06_022-model-based-testing.md | 4 +- docs/adr/2023-04-26_023-local-chain-state.md | 6 +- ...023-06-19_024-event-sourced-persistence.md | 2 +- docs/adr/2023-08-18_025-resource-based-api.md | 2 +- ..._026-stateless-observation-construction.md | 4 +- docs/adr/2023-09-09_027-network-resilience.md | 2 +- docs/adr/2023-12-06_029-use-cbor-for-tx.md | 14 +- docs/benchmarks/index.md | 2 +- docs/docs/configuration.md | 2 +- .../dev/architecture/architecture-c4.puml | 18 +- docs/docs/dev/architecture/index.md | 2 +- docs/docs/dev/architecture/networking.md | 4 +- docs/docs/dev/specification.md | 2 +- docs/docs/getting-started.md | 2 +- docs/docs/how-to/commit-blueprint.md | 2 +- docs/docs/how-to/operating-hydra.md | 4 +- docs/docs/index.md | 2 +- docs/docs/installation.md | 6 +- docs/docs/known-issues.md | 8 +- docs/docs/tutorial/index.md | 12 +- docs/docusaurus.config.js | 14 +- docs/sidebars.js | 2 +- .../src/components/DocumentMetadata/index.tsx | 4 +- docs/standalone/audit-guidelines.md | 14 +- docs/standalone/contribute.md | 4 +- hydra-cardano-api/hydra-cardano-api.cabal | 2 +- .../hydra-chain-observer.cabal | 2 +- hydra-cluster/README.md | 2 +- hydra-cluster/hydra-cluster.cabal | 2 +- hydra-explorer/hydra-explorer.cabal | 2 +- hydra-node/hydra-node.cabal | 2 +- hydra-node/json-schemas/api.yaml | 2 +- hydra-node/json-schemas/logs.yaml | 2 +- .../src/Hydra/Ledger/Cardano/Builder.hs | 2 +- hydra-node/src/Hydra/Logging.hs | 2 +- hydra-plutus-extras/hydra-plutus-extras.cabal | 2 +- hydra-plutus/hydra-plutus.cabal | 2 +- hydra-prelude/hydra-prelude.cabal | 2 +- hydra-test-utils/hydra-test-utils.cabal | 2 +- hydra-test-utils/src/Test/Hydra/Prelude.hs | 2 +- hydra-tui/hydra-tui.cabal | 2 +- plutus-cbor/plutus-cbor.cabal | 2 +- plutus-merkle-tree/plutus-merkle-tree.cabal | 2 +- release.sh | 4 +- .../aws/docker/docker-compose.yaml | 4 +- .../aws/scripts/configure-testnet.sh | 2 +- sample-node-config/gcp/docker-compose.yaml | 2 +- .../gcp/scripts/configure-testnet.sh | 2 +- sample-node-config/nixos/README.md | 2 +- sample-node-config/nixos/hydraw.nix | 2 +- spec/short.bib | 2 +- testnets/README.md | 2 +- 70 files changed, 245 insertions(+), 245 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/config.yaml b/.github/ISSUE_TEMPLATE/config.yaml index f362dcd1536..87a9599fca3 100644 --- a/.github/ISSUE_TEMPLATE/config.yaml +++ b/.github/ISSUE_TEMPLATE/config.yaml @@ -1,13 +1,13 @@ blank_issues_enabled: true contact_links: - name: Contributing guidelines - url: https://github.com/input-output-hk/hydra/blob/master/CONTRIBUTING.md + url: https://github.com/cardano-scaling/hydra/blob/master/CONTRIBUTING.md about: Some rules & processes we honor. - name: Feature ideas - url: https://github.com/input-output-hk/hydra/discussions/categories/ideas + url: https://github.com/cardano-scaling/hydra/discussions/categories/ideas about: Maybe someone else had the same or a similar idea already? - name: All issues - url: https://github.com/input-output-hk/hydra/issues + url: https://github.com/cardano-scaling/hydra/issues about: Check whether your issue is not already covered here. diff --git a/.github/ISSUE_TEMPLATE/feature_idea.yml b/.github/ISSUE_TEMPLATE/feature_idea.yml index 44e1f42d928..3650fc8e7e5 100644 --- a/.github/ISSUE_TEMPLATE/feature_idea.yml +++ b/.github/ISSUE_TEMPLATE/feature_idea.yml @@ -8,7 +8,7 @@ body: value: | **Thank you for contributing to our project!** :green_heart: - Instead of opening this issue, consider [starting a new idea discussion](https://github.com/input-output-hk/hydra/discussions/new?category=ideas). + Instead of opening this issue, consider [starting a new idea discussion](https://github.com/cardano-scaling/hydra/discussions/new?category=ideas). That way, we can discuss & refine your idea together, before we adopt it as a feature into the roadmap. - type: textarea diff --git a/.github/workflows/README.md b/.github/workflows/README.md index 7b2727ac237..e862589b7dd 100644 --- a/.github/workflows/README.md +++ b/.github/workflows/README.md @@ -22,7 +22,7 @@ sudo chown "$(whoami)" /srv/var/cardano # Add the server as a github runner -In the project settings, go to Actions/Runners and click on [New self-hosted runner](https://github.com/input-output-hk/hydra/settings/actions/runners/new) and follow the procedure. +In the project settings, go to Actions/Runners and click on [New self-hosted runner](https://github.com/cardano-scaling/hydra/settings/actions/runners/new) and follow the procedure. :warning: When asked, add the following label to this runner: `cardano` diff --git a/.github/workflows/docker.yaml b/.github/workflows/docker.yaml index 4166bcb09ba..1dfd760f8f4 100644 --- a/.github/workflows/docker.yaml +++ b/.github/workflows/docker.yaml @@ -59,7 +59,7 @@ jobs: VERSION_NAME=${{github.ref_name}} # Use 'FROM' instruction to use docker build with --label echo "FROM ${{matrix.target}}" | docker build \ - --label org.opencontainers.image.source=https://github.com/input-output-hk/hydra \ + --label org.opencontainers.image.source=https://github.com/cardano-scaling/hydra \ --label org.opencontainers.image.licenses=Apache-2.0 \ --label org.opencontainers.image.created=$(date -Is) \ --label org.opencontainers.image.revision=${{github.sha}} \ diff --git a/.github/workflows/explorer/docker-compose.yaml b/.github/workflows/explorer/docker-compose.yaml index 92ba8328262..d2ced1e8732 100644 --- a/.github/workflows/explorer/docker-compose.yaml +++ b/.github/workflows/explorer/docker-compose.yaml @@ -17,7 +17,7 @@ services: restart: always hydra-explorer: - image: ghcr.io/input-output-hk/hydra-explorer:0.17.0 + image: ghcr.io/cardano-scaling/hydra-explorer:0.17.0 volumes: - /srv/var/cardano/state-preview:/data ports: diff --git a/.github/workflows/publish-docs.yaml b/.github/workflows/publish-docs.yaml index e82fc6b865f..8773a0e8487 100644 --- a/.github/workflows/publish-docs.yaml +++ b/.github/workflows/publish-docs.yaml @@ -19,7 +19,7 @@ jobs: - name: 📥 Checkout repository uses: actions/checkout@v4 with: - repository: input-output-hk/hydra + repository: cardano-scaling/hydra ref: release # Also ensure we have all history with all tags fetch-depth: 0 diff --git a/CHANGELOG.md b/CHANGELOG.md index 7893660bf4e..f586ba12a7b 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -14,7 +14,7 @@ changes. - Tested with `cardano-node 8.11.0` and `cardano-cli 8.23.1.0`. -- **BREAKING** Changes to the `hydra-node` API `/commit` endpoint [#1463](https://github.com/input-output-hk/hydra/pull/1463): +- **BREAKING** Changes to the `hydra-node` API `/commit` endpoint [#1463](https://github.com/cardano-scaling/hydra/pull/1463): - Removed the check that prevented committing UTxOs from an internal `hydra-node` wallet. - `SpendingNodeUtxoForbidden` error was removed. @@ -24,31 +24,31 @@ changes. ## [0.17.0] - 2024-05-20 -- **BREAKING** Change `hydra-node` API `/commit` endpoint for committing from scripts [#1380](https://github.com/input-output-hk/hydra/pull/1380): +- **BREAKING** Change `hydra-node` API `/commit` endpoint for committing from scripts [#1380](https://github.com/cardano-scaling/hydra/pull/1380): - Instead of the custom `witness` extension of `UTxO`, the endpoint now accepts a _blueprint_ transaction together with the `UTxO` which is spent in this transaction. - Usage is still the same for commiting "normal" `UTxO` owned by public key addresses. - Spending from a script `UTxO` now needs the `blueprintTx` request type, which also unlocks more involved use-cases, where the commit transaction should also satisfy script spending constraints (like additional signers, validity ranges etc.) - _DEPRECATED_ the `GetUTxO` client input and `GetUTxOResponse` server output. Use `GET /snapshot/utxo` instead. -- Update navigation and re-organized documentation website https://hydra.family [#1440](https://github.com/input-output-hk/hydra/pull/1440) +- Update navigation and re-organized documentation website https://hydra.family [#1440](https://github.com/cardano-scaling/hydra/pull/1440) - Updated logos - Removed localization as it got outdated and on-demand site translation tools exist. -- Add `GET /snapshot/utxo` API endpoint to query confirmed UTxO set on demand. [#1398](https://github.com/input-output-hk/hydra/pull/1398) +- Add `GET /snapshot/utxo` API endpoint to query confirmed UTxO set on demand. [#1398](https://github.com/cardano-scaling/hydra/pull/1398) - Always responds with the last confirmed UTxO -- Set [CORS](https://fetch.spec.whatwg.org/#http-cors-protocol) headers on `hydra-node` API to allow requests from any origin `*`. [#1434](https://github.com/input-output-hk/hydra/pull/1434) +- Set [CORS](https://fetch.spec.whatwg.org/#http-cors-protocol) headers on `hydra-node` API to allow requests from any origin `*`. [#1434](https://github.com/cardano-scaling/hydra/pull/1434) -- `hydra-node` logs will now report `NetworkEvents` to distinguish between `ConnectivityEvent`s and `ReceivedMessage`s on the network. [#1396](https://github.com/input-output-hk/hydra/pull/1396) +- `hydra-node` logs will now report `NetworkEvents` to distinguish between `ConnectivityEvent`s and `ReceivedMessage`s on the network. [#1396](https://github.com/cardano-scaling/hydra/pull/1396) - Hydra now uses a versioned protocol for handshaking. In the event of a node attempting to connect using a different version of the networking protocol, a `HandshakeFailure` event will be recorded in the logs and sent as a server - output on the API. [#1381](https://github.com/input-output-hk/hydra/pull/1381) + output on the API. [#1381](https://github.com/cardano-scaling/hydra/pull/1381) - Make `hydra-cluster --devnet` more configurable - - Now it is idle by default again and a `--busy` will make it busy respending the same UTxO. [#1420](https://github.com/input-output-hk/hydra/pull/1420) + - Now it is idle by default again and a `--busy` will make it busy respending the same UTxO. [#1420](https://github.com/cardano-scaling/hydra/pull/1420) ## [0.16.0] - 2024-04-03 @@ -77,7 +77,7 @@ changes. - Provide more details about why a command failed. Added the state of the head logic at the point of failure. -- Fix a bug where the `hydra-node` would not correctly observe a contest transaction and fail to fanout a head [#1260](https://github.com/input-output-hk/hydra/issues/1260). +- Fix a bug where the `hydra-node` would not correctly observe a contest transaction and fail to fanout a head [#1260](https://github.com/cardano-scaling/hydra/issues/1260). - Add `contestationDeadline` to the `HeadIsContested` output on the `hydra-node` API. @@ -85,37 +85,37 @@ changes. - Enhance `hydra-cluster --devnet` mode to produce a constant stream of snaphsots by re-spending the sandbox UTxO. -- Reduce cost of transactions submitted by `hydra-node` by better estimating fees in internal wallet [#1315](https://github.com/input-output-hk/hydra/pull/1315). +- Reduce cost of transactions submitted by `hydra-node` by better estimating fees in internal wallet [#1315](https://github.com/cardano-scaling/hydra/pull/1315). - Fix conversion of `Conway` blocks in `hydra-node` and `hydra-chain-observer`. This also includes tests that verify `hydra-node` working on Conway networks like `sanchonet` and the `hydra-explorer` observing heads on `sanchonet`. - Fix a bug in the contest observation where contesters were extracted from the input instead of the output datum. - [#1266](https://github.com/input-output-hk/hydra/pull/1266) + [#1266](https://github.com/cardano-scaling/hydra/pull/1266) ## [0.15.0] - 2024-01-18 - Tested with `cardano-node 8.7.3` and `cardano-cli 8.17.0.0`. -- **BREAKING** Remove head state from `hydra-node` chain layer [#1196](https://github.com/input-output-hk/hydra/pull/1196): +- **BREAKING** Remove head state from `hydra-node` chain layer [#1196](https://github.com/cardano-scaling/hydra/pull/1196): - Not maintain head state in the chain layer anymore and all decision making (whether it's "our" head) is now fully contained in the logic layer. - This is a breaking change on the persisted `state` file, which now only stores so-called `spendableUTxO`. This raises a `PersistenceException` if an incompatible `state` file is loaded. - Heads need to be closed before upgrade to this version, as wiping `state` in the `--persistence-dir` is needed. - This also changes the `NodeOptions` log output because of internal restructuring of chain layer configuration. -- New `offline` sub-command for `hydra-node` [#1118](https://github.com/input-output-hk/hydra/pull/1118), [#1222](https://github.com/input-output-hk/hydra/pull/1222): +- New `offline` sub-command for `hydra-node` [#1118](https://github.com/cardano-scaling/hydra/pull/1118), [#1222](https://github.com/cardano-scaling/hydra/pull/1222): - Initializes a head with given `--initial-utxo` parameter, and does not connect to the Cardano network. - Transactions submitted on the L2 are validated as usual, where the offline chain simulates time passing in slots. - The `--ledger-genesis` option allows to give a shelley genesis file to configure start time and slot length of the simulated chain time. -- Prepare `hydra-node` for the upcoming `Conway` hard-fork [#1177](https://github.com/input-output-hk/hydra/issues/1177): +- Prepare `hydra-node` for the upcoming `Conway` hard-fork [#1177](https://github.com/cardano-scaling/hydra/issues/1177): - Interactions with `cardano-node` are updated to work in both, `Babbage` and `Conway` era. - Unsupported eras are reported as error when starting. - Add a default for `hydra-node --node-id` (`"hydra-node-1"`) to simplify configuration. -- Fix `hydra-node` API reference & schema for `/protocol-parameters` [#1241](https://github.com/input-output-hk/hydra/pull/1241). This now matches the JSON returned by `cardano-cli query protocol-parameters`, expected at `hydra-node --ledger-protocol-parameters` and produced by the API endpoint. +- Fix `hydra-node` API reference & schema for `/protocol-parameters` [#1241](https://github.com/cardano-scaling/hydra/pull/1241). This now matches the JSON returned by `cardano-cli query protocol-parameters`, expected at `hydra-node --ledger-protocol-parameters` and produced by the API endpoint. - The `hydra-cluster` binary can bootstrap `cardano-node`s running on public networks using `mithril-client`. @@ -130,10 +130,10 @@ changes. - Sign the head identifier as part of snapshot signature and verify it on-chain. This fully addresses security advisory - [CVE-2023-42806](https://github.com/input-output-hk/hydra/security/advisories/GHSA-gr36-mc6v-72qq). + [CVE-2023-42806](https://github.com/cardano-scaling/hydra/security/advisories/GHSA-gr36-mc6v-72qq). - Switched to using inline datums instead of (optionally) published datums in - transactions. [#1162](https://github.com/input-output-hk/hydra/pull/1162) + transactions. [#1162](https://github.com/cardano-scaling/hydra/pull/1162) - Upgraded toolchain to GHC 9.6 and a newer `plutus-tx` compiler. @@ -143,7 +143,7 @@ changes. - **BREAKING** Introduced messages resending logic in the `Network` layer to improve reliability in the face of connection issues. - [#188](https://github.com/input-output-hk/hydra/issues/188) This persists + [#188](https://github.com/cardano-scaling/hydra/issues/188) This persists network messages on disk in order to gracefully handle crashes and detects inconsistencies between persisted state and configuration. @@ -153,30 +153,30 @@ changes. - Removed hard-coded deposit of 2₳ from internal wallet. Now the wallet does only use as much deposit for script outputs as minimally needed and reduces the Ada locked throughout a head life-cycle. - [#1176](https://github.com/input-output-hk/hydra/pull/1176) + [#1176](https://github.com/cardano-scaling/hydra/pull/1176) - Clients are notified when head initialization is ignored via a new `IgnoredHeadInitializing` API server output. This helps detecting misconfigurations of credentials and head parameters (which need to match). - [#529](https://github.com/input-output-hk/hydra/issues/529) + [#529](https://github.com/cardano-scaling/hydra/issues/529) - Removed false positive `PostTxOnChainFailed` error from API outputs when the collect transaction of another `hydra-node` was "faster" than ours. - [#839](https://github.com/input-output-hk/hydra/issues/839) + [#839](https://github.com/cardano-scaling/hydra/issues/839) - Hydra node API `submit-transaction` endpoint now accepts three types of encoding: Base16 encoded CBOR string, a TextEnvelope with CBOR and full JSON. - [#1111](https://github.com/input-output-hk/hydra/issues/1111) + [#1111](https://github.com/cardano-scaling/hydra/issues/1111) - Improved `gen-hydra-keys` command to not overwrite keys if they are present - already. [#1136](https://github.com/input-output-hk/hydra/issues/1136) + already. [#1136](https://github.com/cardano-scaling/hydra/issues/1136) - Add a `hydra-chain-observer` executable to subscribe to a chain and just observe Hydra Head transactions (with minimal information right now). - [#1158](https://github.com/input-output-hk/hydra/pull/1158) + [#1158](https://github.com/cardano-scaling/hydra/pull/1158) - Fixed `hydra-tui` key bindings for exiting in dialogs. - [#1159](https://github.com/input-output-hk/hydra/issues/1159) + [#1159](https://github.com/cardano-scaling/hydra/issues/1159) ## [0.13.0] - 2023-10-03 @@ -335,15 +335,15 @@ running a head: - Repurpose `log-filter` executable to compute duration of events and effects. -[#774]: https://github.com/input-output-hk/hydra/pull/774 -[#215]: https://github.com/input-output-hk/hydra/issues/215 -[#196]: https://github.com/input-output-hk/hydra/issues/196 -[#922]: https://github.com/input-output-hk/hydra/pull/922 -[#863]: https://github.com/input-output-hk/hydra/pull/863 -[#849]: https://github.com/input-output-hk/hydra/issues/849 -[#927]: https://github.com/input-output-hk/hydra/issues/927 -[#932]: https://github.com/input-output-hk/hydra/issues/932 -[#849]: https://github.com/input-output-hk/hydra/pull/859 +[#774]: https://github.com/cardano-scaling/hydra/pull/774 +[#215]: https://github.com/cardano-scaling/hydra/issues/215 +[#196]: https://github.com/cardano-scaling/hydra/issues/196 +[#922]: https://github.com/cardano-scaling/hydra/pull/922 +[#863]: https://github.com/cardano-scaling/hydra/pull/863 +[#849]: https://github.com/cardano-scaling/hydra/issues/849 +[#927]: https://github.com/cardano-scaling/hydra/issues/927 +[#932]: https://github.com/cardano-scaling/hydra/issues/932 +[#849]: https://github.com/cardano-scaling/hydra/pull/859 ## [0.10.0] - 2023-05-11 @@ -446,7 +446,7 @@ head again. https://hydra.family/head-protocol/unstable. [#803](803) [#805](805) [#783](783) - Add the - [specification](https://github.com/input-output-hk/hydra/tree/master/spec) to + [specification](https://github.com/cardano-scaling/hydra/tree/master/spec) to the repository and [website](https://hydra.family/head-protocol/dev/specification). [#693](693) @@ -468,30 +468,30 @@ head again. - Added `genTxIn` and `arbitrary` instance for `TxIn`. - Added `getChainPoint`. -[185]: https://github.com/input-output-hk/hydra/issues/185 -[380]: https://github.com/input-output-hk/hydra/issues/380 -[693]: https://github.com/input-output-hk/hydra/issues/693 -[713]: https://github.com/input-output-hk/hydra/issues/713 -[764]: https://github.com/input-output-hk/hydra/pull/764 -[766]: https://github.com/input-output-hk/hydra/pull/766 -[772]: https://github.com/input-output-hk/hydra/pull/772 -[777]: https://github.com/input-output-hk/hydra/pull/777 -[783]: https://github.com/input-output-hk/hydra/pull/783 -[784]: https://github.com/input-output-hk/hydra/issues/784 -[786]: https://github.com/input-output-hk/hydra/pull/786 -[803]: https://github.com/input-output-hk/hydra/pull/803 -[805]: https://github.com/input-output-hk/hydra/pull/805 -[808]: https://github.com/input-output-hk/hydra/pull/808 -[813]: https://github.com/input-output-hk/hydra/pull/813 -[825]: https://github.com/input-output-hk/hydra/pull/825 -[826]: https://github.com/input-output-hk/hydra/pull/826 -[826]: https://github.com/input-output-hk/hydra/pull/826 -[837]: https://github.com/input-output-hk/hydra/issues/837 -[839]: https://github.com/input-output-hk/hydra/issues/839 +[185]: https://github.com/cardano-scaling/hydra/issues/185 +[380]: https://github.com/cardano-scaling/hydra/issues/380 +[693]: https://github.com/cardano-scaling/hydra/issues/693 +[713]: https://github.com/cardano-scaling/hydra/issues/713 +[764]: https://github.com/cardano-scaling/hydra/pull/764 +[766]: https://github.com/cardano-scaling/hydra/pull/766 +[772]: https://github.com/cardano-scaling/hydra/pull/772 +[777]: https://github.com/cardano-scaling/hydra/pull/777 +[783]: https://github.com/cardano-scaling/hydra/pull/783 +[784]: https://github.com/cardano-scaling/hydra/issues/784 +[786]: https://github.com/cardano-scaling/hydra/pull/786 +[803]: https://github.com/cardano-scaling/hydra/pull/803 +[805]: https://github.com/cardano-scaling/hydra/pull/805 +[808]: https://github.com/cardano-scaling/hydra/pull/808 +[813]: https://github.com/cardano-scaling/hydra/pull/813 +[825]: https://github.com/cardano-scaling/hydra/pull/825 +[826]: https://github.com/cardano-scaling/hydra/pull/826 +[826]: https://github.com/cardano-scaling/hydra/pull/826 +[837]: https://github.com/cardano-scaling/hydra/issues/837 +[839]: https://github.com/cardano-scaling/hydra/issues/839 ## [0.9.0] - 2023-03-02 -:dragon_face: Renamed the repository from `hydra-poc` to [`hydra`](https://github.com/input-output-hk/hydra)! +:dragon_face: Renamed the repository from `hydra-poc` to [`hydra`](https://github.com/cardano-scaling/hydra)! :warning: Delete your persistence directory! @@ -509,23 +509,23 @@ Only when this procedure has been applied to all Hydra nodes can you open a new ### Changes to `hydra-node` - **BREAKING** Changes in the persistence format - [#725](https://github.com/input-output-hk/hydra/pull/725), - [#745](https://github.com/input-output-hk/hydra/pull/745). + [#725](https://github.com/cardano-scaling/hydra/pull/725), + [#745](https://github.com/cardano-scaling/hydra/pull/745). - **BREAKING** Changes to the API: + Removed `TxSeen` and `TxExpired` server outputs. Use the `TxValid` and `TxInvalid` responses instead. + All participants now see `TxValid` for all valid transactions (it replaces `TxSeen`). + Renamed `ReadyToCommit -> HeadIsInitializing` - + Added a `headId` to most server outputs. [#678](https://github.com/input-output-hk/hydra/pull/678) - + Added a `timestamp` and a monotonic `seq`uence number. [#618](https://github.com/input-output-hk/hydra/pull/618) + + Added a `headId` to most server outputs. [#678](https://github.com/cardano-scaling/hydra/pull/678) + + Added a `timestamp` and a monotonic `seq`uence number. [#618](https://github.com/cardano-scaling/hydra/pull/618) - **BREAKING** Addressed short-comings in `hydra-plutus` scripts - [#452](https://github.com/input-output-hk/hydra/pull/452) and improved their + [#452](https://github.com/cardano-scaling/hydra/pull/452) and improved their performance / reduced cost - [#652](https://github.com/input-output-hk/hydra/pull/652), - [#701](https://github.com/input-output-hk/hydra/pull/701), - [#709](https://github.com/input-output-hk/hydra/pull/709). Roughly the cost of + [#652](https://github.com/cardano-scaling/hydra/pull/652), + [#701](https://github.com/cardano-scaling/hydra/pull/701), + [#709](https://github.com/cardano-scaling/hydra/pull/709). Roughly the cost of transactions according to our [benchmarks](https://hydra.family/head-protocol/benchmarks/transaction-cost/) changed: @@ -545,17 +545,17 @@ Only when this procedure has been applied to all Hydra nodes can you open a new node will close the head 60s after submitting the close transaction and other parties will have another 60s to contest. This means the deadline may be up `2 * --contestation-period` after a close transaction. - [#615](https://github.com/input-output-hk/hydra/pull/615) and + [#615](https://github.com/cardano-scaling/hydra/pull/615) and [ADR21](https://hydra.family/head-protocol/adr/21/) + If hydra-node receives a `init` transaction with _not matching_ `--contestation-period` then this tx is ignored which implies that all parties need to agree on the same value for contestation period. + Removed `contestationPeriod` from the `Init` API request payload. + The deadline get's pushed by `--contestation-period` **on each** contest - transaction. [#716](https://github.com/input-output-hk/hydra/pull/716) + transaction. [#716](https://github.com/cardano-scaling/hydra/pull/716) - Change the way the internal wallet initializes its state. - [#621](https://github.com/input-output-hk/hydra/pull/621) + [#621](https://github.com/cardano-scaling/hydra/pull/621) + The internal wallet does now always query ledger state and parameters at the tip. This should fix the `AcquireFailure` issues. @@ -596,7 +596,7 @@ Only when this procedure has been applied to all Hydra nodes can you open a new [CHaP](https://input-output-hk.github.io/cardano-haskell-packages/all-packages/) + Makes configuration of binary-caches easier to discover (you get asked about adding them). + Will make bumping dependencies (e.g. cardano-node) easier. - + Build commands for binaries and docker images change, see updated [Contribution Guidelines](https://github.com/input-output-hk/hydra/blob/master/CONTRIBUTING.md) + + Build commands for binaries and docker images change, see updated [Contribution Guidelines](https://github.com/cardano-scaling/hydra/blob/master/CONTRIBUTING.md) ## [0.8.1] - 2022-11-17 @@ -605,77 +605,77 @@ Only when this procedure has been applied to all Hydra nodes can you open a new + The `chainState` does not include read-only chain context information anymore (is smaller now). + Include the `chainState` in `InvalidStateToPost` errors. + Moved received transaction ids into `RolledForward` log message. - + Reduce log size by removing ChainContext. [#598](https://github.com/input-output-hk/hydra/issues/598) + + Reduce log size by removing ChainContext. [#598](https://github.com/cardano-scaling/hydra/issues/598) -- **BREAKING** Changed internal wallet logs to help with debugging [#600](https://github.com/input-output-hk/hydra/pull/600) +- **BREAKING** Changed internal wallet logs to help with debugging [#600](https://github.com/cardano-scaling/hydra/pull/600) + Split `ApplyBlock` into `BeginUpdate` and `EndUpdate` + Split `InitializedWallet` into `BeginInitialize` and `EndInitialize` -- After restarting `hydra-node`, clients will receive the whole history. [#580](https://github.com/input-output-hk/hydra/issues/580) +- After restarting `hydra-node`, clients will receive the whole history. [#580](https://github.com/cardano-scaling/hydra/issues/580) + This history will be stored in the `server-output` file in `--persistence-dir`. + Clients should use `Greetings` to identify the end of a [restart/replay of events](https://hydra.family/head-protocol/docs/api-behavior#replay-of-past-server-outputs). -- Fixed observing the chain for Hydra L1 transactions after restart. [599](https://github.com/input-output-hk/hydra/issues/599) +- Fixed observing the chain for Hydra L1 transactions after restart. [599](https://github.com/cardano-scaling/hydra/issues/599) -- `hydra-cardano-api` now published on [Cardano Haskell Packages (CHaP)](https://input-output-hk.github.io/cardano-haskell-packages/package/hydra-cardano-api-0.8.0/). [#504](https://github.com/input-output-hk/hydra/issues/504) +- `hydra-cardano-api` now published on [Cardano Haskell Packages (CHaP)](https://input-output-hk.github.io/cardano-haskell-packages/package/hydra-cardano-api-0.8.0/). [#504](https://github.com/cardano-scaling/hydra/issues/504) ## [0.8.0] - 2022-10-27 - **BREAKING** Hydra keys now use the text envelope format. + `hydra-tools` executable now produces keys in the same format as cardano keys so this should make key handling simpler. - + Take a look at the [example](https://github.com/input-output-hk/hydra/blob/master/docs/docs/getting-started/quickstart.md#hydra-keys) on how to use `hydra-tools` to generate necessary hydra keys. + + Take a look at the [example](https://github.com/cardano-scaling/hydra/blob/master/docs/docs/getting-started/quickstart.md#hydra-keys) on how to use `hydra-tools` to generate necessary hydra keys. - **BREAKING** hydra-node command line flag `--node-id` is now mandatory. + Instead of `Host` we are using the `node-id` in the server messages like + `PeerConnected/Disconnected` which are also used in + the TUI to distinguish between different connected peers. + This also changes the way how `NodeId`s are represented on the API. -- **BREAKING** Keep track of `contestationDeadline` instead of `remainingContestationPeriod` and fix `ReadyToFanout`. [#483](https://github.com/input-output-hk/hydra/pull/483) +- **BREAKING** Keep track of `contestationDeadline` instead of `remainingContestationPeriod` and fix `ReadyToFanout`. [#483](https://github.com/cardano-scaling/hydra/pull/483) + Clients can now rely on `ReadyToFanout`, such that sending a `Fanout` input after seeing this output will never be "too early". + The `HeadIsClosed` server output now contains the deadline instead of the remaining time. + See `hydra-tui` for an example how to use the `contestationDeadline` and `ReadyToFanout`. + See [ADR20](./docs/adr/2022-08-02_020-handling-time.md) for details and the rationale. - **BREAKING** Several changes to the API: - + The `InitialSnapshot` only contains the `initialUTxO` as the rest of the information was useless. [#533](https://github.com/input-output-hk/hydra/pull/533) - + Renamed `CannotSpendInput -> InternalWalletError` and `CannotCoverFees -> NotEnoughFuel`. [#582](https://github.com/input-output-hk/hydra/pull/582) + + The `InitialSnapshot` only contains the `initialUTxO` as the rest of the information was useless. [#533](https://github.com/cardano-scaling/hydra/pull/533) + + Renamed `CannotSpendInput -> InternalWalletError` and `CannotCoverFees -> NotEnoughFuel`. [#582](https://github.com/cardano-scaling/hydra/pull/582) -- **BREAKING** Changed logs to improve legibility and trace on-chain posting errors. [#472](https://github.com/input-output-hk/hydra/pull/472) +- **BREAKING** Changed logs to improve legibility and trace on-chain posting errors. [#472](https://github.com/cardano-scaling/hydra/pull/472) + Strip chain layer logs to only contain `TxId` instead of full transactions in the nominal cases. + Renamed log entry prefixes `Processing -> Begin` and `Processed -> End`. + Added `PostingFailed` log entry. - **BREAKING** The `hydra-cluster` executable (our smoke test) does require `--publish-hydra-scripts` or `--hydra-scripts-tx-id` now as it may be provided with pre-published hydra scripts. -- The `hydra-node` does persist L1 and L2 states on disk now: [#187](https://github.com/input-output-hk/hydra/issues/187) +- The `hydra-node` does persist L1 and L2 states on disk now: [#187](https://github.com/cardano-scaling/hydra/issues/187) + New `--persistence-dir` command line argument to configure location. + Writes two JSON files `headstate` and `chainstate` to the persistence directory. + While introspectable, modification of these files is not recommended. - *Fixed bugs* in `hydra-node`: - + Crash after `3k` blocks because of a failed time conversion. [#523](https://github.com/input-output-hk/hydra/pull/523) - + Internal wallet was losing memory of spent fuel UTxOs in presence of transaction failures. [#525](https://github.com/input-output-hk/hydra/pull/525) - + Node does not see some UTxOs sent to the internal wallet on startup. [#526](https://github.com/input-output-hk/hydra/pull/526) - + Prevent transactions from being resubmitted for application over and over. [#485](https://github.com/input-output-hk/hydra/pull/485) + + Crash after `3k` blocks because of a failed time conversion. [#523](https://github.com/cardano-scaling/hydra/pull/523) + + Internal wallet was losing memory of spent fuel UTxOs in presence of transaction failures. [#525](https://github.com/cardano-scaling/hydra/pull/525) + + Node does not see some UTxOs sent to the internal wallet on startup. [#526](https://github.com/cardano-scaling/hydra/pull/526) + + Prevent transactions from being resubmitted for application over and over. [#485](https://github.com/cardano-scaling/hydra/pull/485) - Prevent misconfiguration of `hydra-node` by logging the command line options used and error out when: + provided number of Hydra parties exceeds a known working maximum (currently 4) + number of provided Cardano and Hydra keys is not the same -- Added a `hydra-tools` executable, to help with generating Hydra keys and get hold of the marker datum hash. [#474](https://github.com/input-output-hk/hydra/pull/474) +- Added a `hydra-tools` executable, to help with generating Hydra keys and get hold of the marker datum hash. [#474](https://github.com/cardano-scaling/hydra/pull/474) - Compute transaction costs as a "min fee" and report it in the [tx-cost benchmark](https://hydra.family/head-protocol/benchmarks/transaction-cost/). - Update [hydra-node-options](https://hydra.family/head-protocol/docs/getting-started/quickstart/#hydra-node-options) section in docs. -- Publish test results on [website](https://hydra.family/head-protocol/benchmarks/tests/hydra-node/hspec-results). [#547](https://github.com/input-output-hk/hydra/pull/547) +- Publish test results on [website](https://hydra.family/head-protocol/benchmarks/tests/hydra-node/hspec-results). [#547](https://github.com/cardano-scaling/hydra/pull/547) - Improved `hydra-tui` user experience: - + Fixed too fast clearing of errors and other feedback [#506](https://github.com/input-output-hk/hydra/pull/506) - + Introduced a pending state to avoid resubmission of transactions [#526](https://github.com/input-output-hk/hydra/pull/526) - + Can show full history (scrollable) [#577](https://github.com/input-output-hk/hydra/pull/577) + + Fixed too fast clearing of errors and other feedback [#506](https://github.com/cardano-scaling/hydra/pull/506) + + Introduced a pending state to avoid resubmission of transactions [#526](https://github.com/cardano-scaling/hydra/pull/526) + + Can show full history (scrollable) [#577](https://github.com/cardano-scaling/hydra/pull/577) -- Build & publish static Linux x86_64 executables on each [release](https://github.com/input-output-hk/hydra/releases/tag/0.8.0) :point_down: [#546](https://github.com/input-output-hk/hydra/pull/546) +- Build & publish static Linux x86_64 executables on each [release](https://github.com/cardano-scaling/hydra/releases/tag/0.8.0) :point_down: [#546](https://github.com/cardano-scaling/hydra/pull/546) ## [0.7.0] - 2022-08-23 @@ -690,19 +690,19 @@ Only when this procedure has been applied to all Hydra nodes can you open a new + Need to provide a `--hydra-scripts-tx-id` to the `hydra-node` containing the current (`--script-info`) Hydra scripts. + Added the `publish-scripts` sub-command to `hydra-node` to publish the current Hydra scripts. -- Added a `hydra-cluster` executable, which runs a single scenario against a known network (smoke test) [#430](https://github.com/input-output-hk/hydra/pull/430) [#423](https://github.com/input-output-hk/hydra/pull/430). +- Added a `hydra-cluster` executable, which runs a single scenario against a known network (smoke test) [#430](https://github.com/cardano-scaling/hydra/pull/430) [#423](https://github.com/cardano-scaling/hydra/pull/430). -- Use deadline when posting a `fanoutTx` instead of the current slot [#441](https://github.com/input-output-hk/hydra/pull/441). +- Use deadline when posting a `fanoutTx` instead of the current slot [#441](https://github.com/cardano-scaling/hydra/pull/441). - The user manual is now also available in Japanese thanks to @btbf! :jp: -- Fixed display of remaining contestation period in `hydra-tui` [#437](https://github.com/input-output-hk/hydra/pull/437). +- Fixed display of remaining contestation period in `hydra-tui` [#437](https://github.com/cardano-scaling/hydra/pull/437). ## [0.6.0] - 2022-06-22 #### Added -- Implement on-chain contestation logic [#192](https://github.com/input-output-hk/hydra/issues/192): +- Implement on-chain contestation logic [#192](https://github.com/cardano-scaling/hydra/issues/192): + Node will automatically post a `Contest` transaction when it observes a `Close` or `Contest` with an obsolete snapshot + Posting a fan-out transaction is not possible before the contestation dealine has passed @@ -720,18 +720,18 @@ Only when this procedure has been applied to all Hydra nodes can you open a new #### Fixed -- Head script to check UTxO hash upon closing the head correctly [#338](https://github.com/input-output-hk/hydra/pull/338). Previously it was possible to close the head with arbitrary UTxO. -- Clients can fanout a Head closed without any off-chain transactions (eg. with initial snapshot) [#395](https://github.com/input-output-hk/hydra/issues/395) +- Head script to check UTxO hash upon closing the head correctly [#338](https://github.com/cardano-scaling/hydra/pull/338). Previously it was possible to close the head with arbitrary UTxO. +- Clients can fanout a Head closed without any off-chain transactions (eg. with initial snapshot) [#395](https://github.com/cardano-scaling/hydra/issues/395) ## [0.5.0] - 2022-05-06 #### Added -- Start `hydra-node` tracking the chain starting at a previous point using new `--start-chain-from` command line option [#300](https://github.com/input-output-hk/hydra/issues/300). +- Start `hydra-node` tracking the chain starting at a previous point using new `--start-chain-from` command line option [#300](https://github.com/cardano-scaling/hydra/issues/300). + This is handy to re-initialize a stopped (or crashed) `hydra-node` with an already inititalized Head + Note that off-chain state is NOT persisted, but this feature is good enough to continue opening or closing/finalizing a Head -- Handle rollbacks [#184](https://github.com/input-output-hk/hydra/issues/184) +- Handle rollbacks [#184](https://github.com/cardano-scaling/hydra/issues/184) + Not crash anymore on rollbacks + Rewind the internal head state to the point prior to rollback point + Added `RolledBack` server output, see [API reference](https://hydra.family/head-protocol/api-reference) @@ -740,7 +740,7 @@ Only when this procedure has been applied to all Hydra nodes can you open a new - [Hydra Network](https://hydra.family/head-protocol/dev/networking) section on the website about networking requirements and considerations - [Benchmarks](https://hydra.family/head-protocol/benchmarks) section on the website with continuously updated and published results on transaction costs of Hydra protocol transactions - + These are also performed and reported now on every PR -> [Example](https://github.com/input-output-hk/hydra/pull/340#issuecomment-1116247611) + + These are also performed and reported now on every PR -> [Example](https://github.com/cardano-scaling/hydra/pull/340#issuecomment-1116247611) - New architectural decision records: + [ADR-0017: UDP for Hydra networking](https://hydra.family/head-protocol/adr/17) @@ -756,7 +756,7 @@ Only when this procedure has been applied to all Hydra nodes can you open a new - **BREAKING** Switch to Ed25519 keys and proper EdDSA signatures for the Hydra Head protocol + The `--hydra-signing-key` and consequently `--hydra-verification-key` are now longer and not compatible with previous versions! -- **BREAKING** The Hydra plutus scripts have changed in course of finalizing [#181](https://github.com/input-output-hk/hydra/issues/181) +- **BREAKING** The Hydra plutus scripts have changed in course of finalizing [#181](https://github.com/cardano-scaling/hydra/issues/181) + All Hydra protocol transactions need to be signed by a Head participant now + This changes the script address(es) and the current `hydra-node` would not detect old Heads on the testnet. @@ -767,14 +767,14 @@ Only when this procedure has been applied to all Hydra nodes can you open a new #### Fixed -- Reject commit transactions locking a UTxO locked by Byron addresses, part of [#182](https://github.com/input-output-hk/hydra/issues/182) +- Reject commit transactions locking a UTxO locked by Byron addresses, part of [#182](https://github.com/cardano-scaling/hydra/issues/182) + This would render a Head unclosable because Byron addresses are filtered out by the ledger and not visible to plutus scripts - Fix instructions in [demo setup without docker](https://hydra.family/head-protocol/docs/getting-started/demo/without-docker) to use `0.0.0.0` and correct paths. #### Known Issues -- TUI quickly flashes an error on fanout. This is because all nodes try to post a fanout transaction, but only one of the participants' transactions wins. Related to [#279](https://github.com/input-output-hk/hydra/issues/279) +- TUI quickly flashes an error on fanout. This is because all nodes try to post a fanout transaction, but only one of the participants' transactions wins. Related to [#279](https://github.com/cardano-scaling/hydra/issues/279) - Recipient addresses to send money to in the TUI are inferred from the current UTXO set. If a party does not commit a UTXO or consumes all its UTXO in a Head, it won't be able to send or receive anything anymore. - TUI crashes when user tries to post a new transaction without any UTXO remaining. - The internal wallet of hydra-node requires a UTXO to be marked as "fuel" to drive the Hydra protocol transactions. See [user manual](https://hydra.family/head-protocol/docs/getting-started/demo/with-docker/#seeding-the-network). @@ -784,8 +784,8 @@ Only when this procedure has been applied to all Hydra nodes can you open a new #### Added - Our [user manual 📖](https://hydra.family/head-protocol) is now available! It includes installation and usage instructions, a full API reference and also a knowledge base about Hydra concepts. The manual will be an ever-evolving source of documentation that we'll maintain alongside the project. -- Support multiple Heads per Cardano network by identifying and distinguishing transactions of individual Head instances [#180](https://github.com/input-output-hk/hydra/issues/180). -- Mint and burn state token used to thread state across the OCV state machine, and participation tokens for each party in the head [#181](https://github.com/input-output-hk/hydra/issues/181) +- Support multiple Heads per Cardano network by identifying and distinguishing transactions of individual Head instances [#180](https://github.com/cardano-scaling/hydra/issues/180). +- Mint and burn state token used to thread state across the OCV state machine, and participation tokens for each party in the head [#181](https://github.com/cardano-scaling/hydra/issues/181) - Provide (mandatory) command-line options `--ledger-genesis` and `--ledger-protocol-parameters` to configure the ledger that runs _inside a head_. Options are provided as filepath to JSON files which match formats from `cardano-cli` and `cardano-node` [#180](https://github.com/input-output-hk/hydra/issues/180). - Created [hydra-cardano-api](https://hydra.family/head-protocol/haddock/hydra-cardano-api/) as wrapper around [cardano-api](https://github.com/input-output-hk/cardano-node/tree/master/cardano-api#cardano-api) specialized to the latest Cardano's era, and with useful extra utility functions. - Two new architectural decision records: @@ -795,16 +795,16 @@ Only when this procedure has been applied to all Hydra nodes can you open a new #### Changed - `--network-magic` option for the `hydra-node` and `hydra-tui` has been changed to `--network-id`. Also, the `hydra-tui` command-line used to default to mainnet when not provided with any `--network-magic` option, it doesn't anymore, `--network-id` is mandatory. [#180](https://github.com/input-output-hk/hydra/issues/180) -- Optimize the `CollectCom` transition of the on-chain Hydra contract to allow collecting commits from more than 2 parties! [#254](https://github.com/input-output-hk/hydra/issues/254) +- Optimize the `CollectCom` transition of the on-chain Hydra contract to allow collecting commits from more than 2 parties! [#254](https://github.com/cardano-scaling/hydra/issues/254) - Use a faucet to distribute funds in test suites and the `demo/` setup. - Internally, better decouple the management of the on-chain head state from the network component. While not visible to the end user, this improvement paves the way for better handling rollbacks and on-chain _"instability"_ of newly posted transactions. [#184](https://github.com/input-output-hk/hydra/issues/184) - Internally, improved and consolidate generators used for property-based testing to cover a wider range of cases, be more consistent and also faster (avoiding to generate too large nested data-structures). #### Fixed -- `Hydra.Network.Ouroboros` not using hard-coded valency values anymore to allow more than 7 peer connections [#203](https://github.com/input-output-hk/hydra/issues/203). -- Build issues due to explicit packages list in nix shell [#223](https://github.com/input-output-hk/hydra/issues/223). -- `hydra-tui` to show form focus, indicate invalid fields in dialogs and only allow valid values to be submitted [#224](https://github.com/input-output-hk/hydra/issues/224). +- `Hydra.Network.Ouroboros` not using hard-coded valency values anymore to allow more than 7 peer connections [#203](https://github.com/cardano-scaling/hydra/issues/203). +- Build issues due to explicit packages list in nix shell [#223](https://github.com/cardano-scaling/hydra/issues/223). +- `hydra-tui` to show form focus, indicate invalid fields in dialogs and only allow valid values to be submitted [#224](https://github.com/cardano-scaling/hydra/issues/224). - Repaired benchmarks and improved collected metrics; in particular, benchmarks now collect CPU usage and provide average confirmation times over 5s windows. - Fixed a bug in the Fanout transaction scheduling and submission where clients would attempt to post a fanout transaction before a 'Close' transaction is even observed. Now, every participant of the head will attempt to post a fanout a transaction after they successfully observed a transaction. Of course, the layer 1 will enforce that only one fanout is posted [#279](https://github.com/input-output-hk/hydra/issues/279). diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 61cf809febb..5be24bc733d 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -30,7 +30,7 @@ The documentation is also available in multiple languages and we can easily add ### Bug reports -[Submit an issue](https://github.com/input-output-hk/hydra/issues/new/choose) +[Submit an issue](https://github.com/cardano-scaling/hydra/issues/new/choose) using the "Bug report :bug:" template. It's very important that you fill the template as thoroughly as possible. @@ -40,9 +40,9 @@ Feature ideas are precursors to high-level features items, which will be discussed and fleshed out to ideally become items on our feature roadmap. We use the [Ideas discussions -category](https://github.com/input-output-hk/hydra/discussions/categories/ideas) +category](https://github.com/cardano-scaling/hydra/discussions/categories/ideas) to discuss and vote on feature ideas, but you can also [submit an -issue](https://github.com/input-output-hk/hydra/issues/new/choose) using the +issue](https://github.com/cardano-scaling/hydra/issues/new/choose) using the "Feature idea :thought_balloon:" template and we convert that to a discussion. We expect a description of @@ -118,7 +118,7 @@ before we merge any contributions. ### Coding standards Make sure to follow our [Coding -Standards](https://github.com/input-output-hk/hydra/wiki/Coding-Standards). +Standards](https://github.com/cardano-scaling/hydra/wiki/Coding-Standards). It includes guidelines on Haskell code style, but also on Git commit messages and some processes (TODO: clarify separation or unify with these guidelines). To propose new standards or changes to the existing standards, file an issue. @@ -188,7 +188,7 @@ During development + Make sure `CHANGELOG.md` is kept up-to-date with high-level, technical, but user-focused list of changes according to [keepachangelog](https://keepachangelog.com/en/1.0.0/) + Bump `UNRELEASED` version in `CHANGELOG.md` according to [semver](https://semver.org/) + Ensure `unstable` version of docker images is used in demo - - `sed -i.bak -e "s,\(ghcr.io/input-output-hk/hydra-[^:]*\):[^[:space:]]*,\1:unstable," demo/*` + - `sed -i.bak -e "s,\(ghcr.io/cardano-scaling/hydra-[^:]*\):[^[:space:]]*,\1:unstable," demo/*` + All `hydra-` packages are versioned the same, at latest on release their versions are aligned. + Other packages are versioned independently of `hydra-` packages and keep a dedicated changelog. @@ -213,7 +213,7 @@ To perform a release of next ``: `aarch64-darwin` (the same for `cardano-node` instead of `hydra`) * The just published `hydra-scripts-tx-id` from step 1 -[smoke-test]: https://github.com/input-output-hk/hydra/actions/workflows/smoke-test.yaml +[smoke-test]: https://github.com/cardano-scaling/hydra/actions/workflows/smoke-test.yaml ## Communication @@ -272,7 +272,7 @@ To conduct this meeting and write this report: + Store latest roadmap screenshot in slides and on [miro](https://miro.com/app/board/uXjVMA4bSao=/), with and without 💭 **idea** items + Check milestones and versions are consistent + Mark up and summarize notable changes in the roadmap to last month to support slides - - Update repository status in slides using + - Update repository status in slides using - Prepare invitation, by creating an event in discord, update the invitation used last month with it. - Send invitation to Hydra and Mithril #announcements channels on our discord server. diff --git a/README.md b/README.md index 96b1ecc3aca..f448c1ff38d 100644 --- a/README.md +++ b/README.md @@ -2,8 +2,8 @@

Implementation of the Hydra scalability protocols.

- - + +
## :sunrise_over_mountains: Introduction @@ -50,8 +50,8 @@ The quickest way to get a `hydra-node` running is to use our [docker images](https://github.com/orgs/input-output-hk/packages?repo_name=hydra). ```sh -docker pull ghcr.io/input-output-hk/hydra-node -docker run --rm ghcr.io/input-output-hk/hydra-node --help +docker pull ghcr.io/cardano-scaling/hydra-node +docker run --rm ghcr.io/cardano-scaling/hydra-node --help ``` Get started with the [user manual 📖](https://hydra.family/head-protocol/docs/getting-started)! @@ -83,8 +83,8 @@ The best way to contribute is to provide feedback. Give the [demo](./demo) a spi Should you have any questions, ideas or issues, we would like to hear from you: - #ask-hydra on the IOG [Discord server](https://discord.gg/Qq5vNTg9PT) -- create a Github [Discussion](https://github.com/input-output-hk/hydra/discussions) -- open a Github [Issue](https://github.com/input-output-hk/hydra/issues/new) +- create a Github [Discussion](https://github.com/cardano-scaling/hydra/discussions) +- open a Github [Issue](https://github.com/cardano-scaling/hydra/issues/new) Please follow our [Contributing Guidelines](./CONTRIBUTING.md) and [Code of Conduct](./CODE-OF-CONDUCT.md). diff --git a/SECURITY.md b/SECURITY.md index fca31e2a665..6afb463f8b4 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -16,7 +16,7 @@ how we will respond to and remediate such reports. If you discover a security vulnerability in Hydra, we encourage you to responsibly disclose it to us. To report a vulnerability, please use the [private reporting form on -GitHub](https://github.com/input-output-hk/hydra/security/advisories/new) +GitHub](https://github.com/cardano-scaling/hydra/security/advisories/new) to draft a new _Security advisory_. Please include as much details as needed to clearly qualify the issue: @@ -91,13 +91,13 @@ report security vulnerabilities to us. ## Contact Information To report a security vulnerability, please use [GitHub -form](https://github.com/input-output-hk/hydra/security/advisories/new). +form](https://github.com/cardano-scaling/hydra/security/advisories/new). ## Revision of Policy This Security Vulnerability Disclosure Policy may be updated or revised as necessary. Please check the latest version of this policy -on the [Hydra repository](https://github.com/input-output-hk/hydra/blob/master/SECURITY.md). +on the [Hydra repository](https://github.com/cardano-scaling/hydra/blob/master/SECURITY.md). ## Conclusion diff --git a/SUPPORT.md b/SUPPORT.md index 319b750e7ce..1135893d80c 100644 --- a/SUPPORT.md +++ b/SUPPORT.md @@ -5,8 +5,8 @@ these communication channels to reach the Hydra team and get answers in a way where others can benefit from it as well: - #ask-hydra on the IOG [Discord server](https://discord.gg/Qq5vNTg9PT) -- create a Github [Discussion](https://github.com/input-output-hk/hydra/discussions) -- open a Github [Issue](https://github.com/input-output-hk/hydra/issues/new) +- create a Github [Discussion](https://github.com/cardano-scaling/hydra/discussions) +- open a Github [Issue](https://github.com/cardano-scaling/hydra/issues/new) # Reporting a Vulnerability diff --git a/cardano-api-classy/cardano-api-classy.cabal b/cardano-api-classy/cardano-api-classy.cabal index fc966c1b695..babdf253d58 100644 --- a/cardano-api-classy/cardano-api-classy.cabal +++ b/cardano-api-classy/cardano-api-classy.cabal @@ -13,7 +13,7 @@ license-files: source-repository head type: git - location: https://github.com/input-output-hk/hydra + location: https://github.com/cardano-scaling/hydra common project-config default-language: GHC2021 diff --git a/demo/docker-compose.yaml b/demo/docker-compose.yaml index 7a73f63b91d..fc1bbc62330 100644 --- a/demo/docker-compose.yaml +++ b/demo/docker-compose.yaml @@ -21,7 +21,7 @@ services: hydra-node-1: # NOTE: Make sure to use the same image in ./seed-devnet.sh - image: ghcr.io/input-output-hk/hydra-node:0.17.0 + image: ghcr.io/cardano-scaling/hydra-node:0.17.0 build: context: ../ target: hydra-node @@ -56,7 +56,7 @@ services: hydra-node-2: # NOTE: Make sure to use the same image in ./seed-devnet.sh - image: ghcr.io/input-output-hk/hydra-node:0.17.0 + image: ghcr.io/cardano-scaling/hydra-node:0.17.0 build: context: ../ target: hydra-node @@ -91,7 +91,7 @@ services: hydra-node-3: # NOTE: Make sure to use the same image in ./seed-devnet.sh - image: ghcr.io/input-output-hk/hydra-node:0.17.0 + image: ghcr.io/cardano-scaling/hydra-node:0.17.0 build: context: ../ target: hydra-node @@ -125,7 +125,7 @@ services: restart: always hydra-tui-1: - image: ghcr.io/input-output-hk/hydra-tui:0.17.0 + image: ghcr.io/cardano-scaling/hydra-tui:0.17.0 build: context: ../ target: hydra-tui @@ -142,7 +142,7 @@ services: ipv4_address: 172.16.238.11 hydra-tui-2: - image: ghcr.io/input-output-hk/hydra-tui:0.17.0 + image: ghcr.io/cardano-scaling/hydra-tui:0.17.0 build: context: ../ target: hydra-tui @@ -159,7 +159,7 @@ services: ipv4_address: 172.16.238.21 hydra-tui-3: - image: ghcr.io/input-output-hk/hydra-tui:0.17.0 + image: ghcr.io/cardano-scaling/hydra-tui:0.17.0 build: context: ../ target: hydra-tui diff --git a/demo/seed-devnet.sh b/demo/seed-devnet.sh index 7843a9dc23f..c17951f6320 100755 --- a/demo/seed-devnet.sh +++ b/demo/seed-devnet.sh @@ -49,7 +49,7 @@ function hnode() { docker run --rm -it \ --pull always \ -v ${SCRIPT_DIR}/devnet:/devnet \ - ghcr.io/input-output-hk/hydra-node:0.17.0 -- ${@} + ghcr.io/cardano-scaling/hydra-node:0.17.0 -- ${@} fi } diff --git a/docs/adr/2021-11-25_012-top-down-test-driven-design.md b/docs/adr/2021-11-25_012-top-down-test-driven-design.md index ac5c9511a34..af49387769e 100644 --- a/docs/adr/2021-11-25_012-top-down-test-driven-design.md +++ b/docs/adr/2021-11-25_012-top-down-test-driven-design.md @@ -31,4 +31,4 @@ We tactically drop to _Unit tests_ level when dealing with the protocol's "fine ## Consequences * Development of each "feature", whether new or change to existing one, should start with a test defined at the highest level possible, but no higher -* A detailed presentation of the various testing layers is available in the [wiki](https://github.com/input-output-hk/hydra/wiki/Testing-Strategy) +* A detailed presentation of the various testing layers is available in the [wiki](https://github.com/cardano-scaling/hydra/wiki/Testing-Strategy) diff --git a/docs/adr/2022-02-14_014-hydra-script-tokens.md b/docs/adr/2022-02-14_014-hydra-script-tokens.md index bdf19969390..b42915731ba 100644 --- a/docs/adr/2022-02-14_014-hydra-script-tokens.md +++ b/docs/adr/2022-02-14_014-hydra-script-tokens.md @@ -34,10 +34,10 @@ Accepted * Heads can be identified by looking for the `ST` in `init`, `collectCom`, `close`, `contest` or `fanout` transactions, or the `PT` in `commit` transactions. In both cases, the `CurrencySymbol == HeadId` * Our scripts become simpler as we only need to check that ST/PT are paid forward, instead of needing to check datums -* The datum produced by `commit` txs (and consumed by `collectCom`) is `Just SerializedTxOut`, which is simpler than also keeping the participant which committed in the datum (compare to full life-cycle of [0.3.0](https://github.com/input-output-hk/hydra/tree/0.3.0/docs/images/on-chain-full.jpg)). +* The datum produced by `commit` txs (and consumed by `collectCom`) is `Just SerializedTxOut`, which is simpler than also keeping the participant which committed in the datum (compare to full life-cycle of [0.3.0](https://github.com/cardano-scaling/hydra/tree/0.3.0/docs/images/on-chain-full.jpg)). * The `v_head` script validator does not need to be parameterized, which makes discovering new Heads (and also tracking them for metrics) easier as the address to watch for is common to all Heads (of the same `v_head` version). -* The `v_head` script (path) for the abort life-cycle can be implemented already much safer by checking that all PTs are burned on the `abort` transaction (counting inputs in abort life-cycle of [0.3.0](https://github.com/input-output-hk/hydra/tree/0.3.0/docs/images/on-chain-abort.jpg)). +* The `v_head` script (path) for the abort life-cycle can be implemented already much safer by checking that all PTs are burned on the `abort` transaction (counting inputs in abort life-cycle of [0.3.0](https://github.com/cardano-scaling/hydra/tree/0.3.0/docs/images/on-chain-abort.jpg)). * Updated diagrams for the [full](img/on-chain-full.jpg) and [abort](img/on-chain-abort.jpg) on-chain life-cycles of a Hydra Head. ## Follow-up questions diff --git a/docs/adr/2022-03-17_015-admin-api.md b/docs/adr/2022-03-17_015-admin-api.md index abeb38333cd..12e93c869a6 100644 --- a/docs/adr/2022-03-17_015-admin-api.md +++ b/docs/adr/2022-03-17_015-admin-api.md @@ -16,7 +16,7 @@ Draft * This poses significant challenges for operating a _cluster_ of Hydra nodes as one needs to know beforehand everything about the cluster, then pass a large number of arguments to some program or docker-compose file, before any node can be started * This is a pain that's been felt first-hand for benchmarking and testing purpose * Having static network configuration is probably not sustainable in the long run, even if we don't add any fancy multihead capabilities to the node, as it would make it significantly harder to have automated creation of Heads. -* There's been an [attempt](https://github.com/input-output-hk/hydra/pull/222) at providing a file-based network configuration but this was deemed unconvincing +* There's been an [attempt](https://github.com/cardano-scaling/hydra/pull/222) at providing a file-based network configuration but this was deemed unconvincing * [Hydra paper (sec. 4, p. 13)](https://eprint.iacr.org/2020/299.pdf) explicitly assumes the existence of a _setup_ phase * This _setup_ is currently left aside, e.g. exchange of keys for setting up multisig and identifying peers. The [hydra-node](https://github.com/input-output-hk/hydra/blob/abailly-iohk/admin-api-adr/hydra-node/exe/hydra-node/Main.hs#L41) executable is statically configured and those things are assumed to be known beforehand diff --git a/docs/adr/2022-04-13_018-single-state.md b/docs/adr/2022-04-13_018-single-state.md index ee1304eabc0..84d77a05b54 100644 --- a/docs/adr/2022-04-13_018-single-state.md +++ b/docs/adr/2022-04-13_018-single-state.md @@ -14,7 +14,7 @@ Superseded by [ADR 23](/adr/23) and [ADR 26](/adr/26) * Currently the `hydra-node` maintains two pieces of state during the life-cycle of a Hydra Head: 1. A `HeadState tx` provided by the `HydraHead tx m` handle interface and part of the `Hydra.Node` module. It provides the basis for the main `hydra-node` business logic in `Hydra.Node.processNextEvent` and `Hydra.HeadLogic.update` - [Creation](https://github.com/input-output-hk/hydra/blob/a98e2907c4e425de2736782793383aad63132c14/hydra-node/src/Hydra/Node.hs#L256-L257), [Usage](https://github.com/input-output-hk/hydra/blob/a98e2907c4e425de2736782793383aad63132c14/hydra-node/src/Hydra/Node.hs#L174) + [Creation](https://github.com/cardano-scaling/hydra/blob/a98e2907c4e425de2736782793383aad63132c14/hydra-node/src/Hydra/Node.hs#L256-L257), [Usage](https://github.com/cardano-scaling/hydra/blob/a98e2907c4e425de2736782793383aad63132c14/hydra-node/src/Hydra/Node.hs#L174) 2. `SomeOnChainHeadState` is kept in the `Hydra.Chain.Direct` to keep track of the latest known head state, including notable transaction outputs and information how to spend it (e.g. scripts and datums) [Code](https://github.com/input-output-hk/hydra/blob/a98e2907c4e425de2736782793383aad63132c14/hydra-node/src/Hydra/Chain/Direct.hs#L156-L162), [Usage 1](https://github.com/input-output-hk/hydra/blob/a98e2907c4e425de2736782793383aad63132c14/hydra-node/src/Hydra/Chain/Direct.hs#L449), [Usage 2](https://github.com/input-output-hk/hydra/blob/a98e2907c4e425de2736782793383aad63132c14/hydra-node/src/Hydra/Chain/Direct.hs#L414), [Usage 3](https://github.com/input-output-hk/hydra/blob/a98e2907c4e425de2736782793383aad63132c14/hydra-node/src/Hydra/Chain/Direct.hs#L349-L352) (There are other unrelated things kept in memory like the event history in the API server or a peer map in the network heartbeat component.) @@ -28,7 +28,7 @@ Superseded by [ADR 23](/adr/23) and [ADR 26](/adr/26) type ChainCallback tx m = OnChainTx tx -> m () ``` * Given by the usage sites above, the `Hydra.Chain.Direct` module requires additional info to do both, construct protocol transactions with `postTx` as well as observe potential `OnChainTx` ([here](https://github.com/input-output-hk/hydra/blob/a98e2907c4e425de2736782793383aad63132c14/hydra-node/src/Hydra/Chain/Direct.hs#L333-L336)). Hence we see that, operation of the `Hydra.Chain.Direct` component (and likely any implementing the interface fully) is **inherently stateful**. -* We are looking at upcoming features to [handle rollbacks](https://github.com/input-output-hk/hydra/issues/185) and dealing with [persisting the head state](https://github.com/input-output-hk/hydra/issues/187). +* We are looking at upcoming features to [handle rollbacks](https://github.com/cardano-scaling/hydra/issues/185) and dealing with [persisting the head state](https://github.com/cardano-scaling/hydra/issues/187). - Both could benefit from the idea, that the `HeadState` is just a result of pure `Event` processing (a.k.a event sourcing). - Right now the `HeadState` kept in `Hydra.Node` alone, is not enough to fully describe the state of the `hydra-node`. Hence it would not be enough to just persist all the `Event`s and replaying them to achieve persistence, nor resetting to some previous `HeadState` in the presence of a rollback. diff --git a/docs/adr/2022-12-06_022-model-based-testing.md b/docs/adr/2022-12-06_022-model-based-testing.md index b80afd74870..fab0bc80f86 100644 --- a/docs/adr/2022-12-06_022-model-based-testing.md +++ b/docs/adr/2022-12-06_022-model-based-testing.md @@ -12,7 +12,7 @@ Accepted ## Context -- We have been experimenting with [quickcheck-dynamic](https://hackage.org/packages/quickcheck-dynamic) for a while, leading to the implementation of basic [Model-Based tests](https://github.com/input-output-hk/hydra/blob/master/hydra-node/test/Hydra/ModelSpec.hs) for the Hydra Head Protocol +- We have been experimenting with [quickcheck-dynamic](https://hackage.org/packages/quickcheck-dynamic) for a while, leading to the implementation of basic [Model-Based tests](https://github.com/cardano-scaling/hydra/blob/master/hydra-node/test/Hydra/ModelSpec.hs) for the Hydra Head Protocol - These tests fill a gap in our testing strategy, between [BehaviorSpec](https://github.com/input-output-hk/hydra/blob/master/hydra-node/test/Hydra/BehaviorSpec.hs) tests which test a "network" of nodes but only at the level of the off-chain Head logic, and [EndToEndSpec](https://github.com/input-output-hk/hydra/blob/master/hydra-cluster/test/Test/EndToEndSpec.hs) tests which test a full blown network of nodes interconnected through real network connections and to a real cardano-node: - The former are fast but do not test the complete lifecycle of a Head. Furthermore, they are only unit tests so do not provide coverage into various corner cases that could arise in practice - The latter exercise the full lifecycle but are very slow and brittle @@ -20,7 +20,7 @@ Accepted ## Decision -- We will maintain and evolve the [Model](https://github.com/input-output-hk/hydra/blob/master/hydra-node/test/Hydra/Model.hs) over time to cover more features +- We will maintain and evolve the [Model](https://github.com/cardano-scaling/hydra/blob/master/hydra-node/test/Hydra/Model.hs) over time to cover more features - Key properties of the whole system should be written-down as proper `DynamicLogic` properties and thoroughly tested using quickcheck-dynamic. This includes but is not limited to: - Liveness of the Head - Consistency of the Head diff --git a/docs/adr/2023-04-26_023-local-chain-state.md b/docs/adr/2023-04-26_023-local-chain-state.md index 4f87d85c49c..097a93fd102 100644 --- a/docs/adr/2023-04-26_023-local-chain-state.md +++ b/docs/adr/2023-04-26_023-local-chain-state.md @@ -18,13 +18,13 @@ Accepted - Having the `headState` containing the `chainState` made persistency easier to deal with: we ensure that we always save cohesive states. - When opening our first head on mainnet we suffered from a [commit/rollback - issue](https://github.com/input-output-hk/hydra/issues/784) that was the + issue](https://github.com/cardano-scaling/hydra/issues/784) that was the result of a race condition in the management of the `chainState` as implemented in the context of [ADR 18](/adr/18). - Reproducing the issue by introducing rollbacks in the model based tests, we discovered that, as a client of a hydra-node, we had no idea how to deal with the rollback event as it is defined now. -- [#185](https://github.com/input-output-hk/hydra/issues/185) plans to improve +- [#185](https://github.com/cardano-scaling/hydra/issues/185) plans to improve rollback management. The following picture details the race condition through an exemple: @@ -59,7 +59,7 @@ testing. - A copy of the `chainState` is kept in the `headState` to keep the benefits of [ADR 18](/adr/18) regarding persistency. - The `RolledBack` output is removed from the API unless actionable by users or - [#185](https://github.com/input-output-hk/hydra/issues/185) implemented. + [#185](https://github.com/cardano-scaling/hydra/issues/185) implemented. ## Consequences diff --git a/docs/adr/2023-06-19_024-event-sourced-persistence.md b/docs/adr/2023-06-19_024-event-sourced-persistence.md index b5fb2ed84b5..9fd2e4c4081 100644 --- a/docs/adr/2023-06-19_024-event-sourced-persistence.md +++ b/docs/adr/2023-06-19_024-event-sourced-persistence.md @@ -53,6 +53,6 @@ sequenceDiagram - New possibilities this change introduces with respect to `ServerOutput` handling and client's access to a head's state: - Instead of having the `HeadLogic` emits directly a `ClientEffect`, the latter could be the result of a client-centric _interpretation_ of a `StateChanged`. - - Pushing this a little further, we could maintain a _Query Model_ for clients with a dedicated [Query API](https://github.com/input-output-hk/hydra/discussions/686) to ease implementation of stateless clients. + - Pushing this a little further, we could maintain a _Query Model_ for clients with a dedicated [Query API](https://github.com/cardano-scaling/hydra/discussions/686) to ease implementation of stateless clients. - Calling `StateChanged` an _event_ while treating it in the code alongside _effects_ might introduce some confusion as we already use the word [Event](https://github.com/input-output-hk/hydra/blob/45913954eb18ef550a31017daa443cee6720a00c/hydra-node/src/Hydra/HeadLogic.hs#L64) to designate the inputs (a.k.a. commands) to the Head logic state machine. We might want at some later point to unify the terminology. diff --git a/docs/adr/2023-08-18_025-resource-based-api.md b/docs/adr/2023-08-18_025-resource-based-api.md index 86fcb791fb9..dacfbab935e 100644 --- a/docs/adr/2023-08-18_025-resource-based-api.md +++ b/docs/adr/2023-08-18_025-resource-based-api.md @@ -50,7 +50,7 @@ Draft - Inclusion of the whole UTxO set in the head is not always desirable and filtering by address would be beneficial. (not addressed in this ADR though, relevant discussion - [#797](https://github.com/input-output-hk/hydra/discussions/797)) + [#797](https://github.com/cardano-scaling/hydra/discussions/797)) - As [ADR-15](/adr/15) also proposes, some clients may not need (or should not have) access to administrative information. diff --git a/docs/adr/2023-09-08_026-stateless-observation-construction.md b/docs/adr/2023-09-08_026-stateless-observation-construction.md index 37ef5497686..57738a71880 100644 --- a/docs/adr/2023-09-08_026-stateless-observation-construction.md +++ b/docs/adr/2023-09-08_026-stateless-observation-construction.md @@ -38,7 +38,7 @@ Draft where `InitialState`, `OpenState` and `ClosedState` hold elaborate information about the currently tracked Hydra head. -- We face [difficulties](https://github.com/input-output-hk/hydra/issues/529) to +- We face [difficulties](https://github.com/cardano-scaling/hydra/issues/529) to provide sufficient user feedback when an `initTx` was observed but (for example) keys do not match our expectation. @@ -48,7 +48,7 @@ Draft and `API` layers. - We want to build a [Hydra head - explorer](https://github.com/input-output-hk/hydra/issues/696), which should + explorer](https://github.com/cardano-scaling/hydra/issues/696), which should be able to keep track and discover Hydra heads and their state changes even when the heads were initialized before starting the explorer. diff --git a/docs/adr/2023-09-09_027-network-resilience.md b/docs/adr/2023-09-09_027-network-resilience.md index 0af41ced888..8e0f588bacb 100644 --- a/docs/adr/2023-09-09_027-network-resilience.md +++ b/docs/adr/2023-09-09_027-network-resilience.md @@ -31,7 +31,7 @@ Therefore, the scope of this ADR is to address only point 1. above: Ensure broad * We are currently using the [ouroboros-framework](https://github.com/input-output-hk/ouroboros-network) and [typed-protocols](https://github.com/input-output-hk/typed-protocols) network stack as a mere [transport](https://osi-model.com/transport-layer/) layer. * Being built on top of TCP, ouroboros multiplexer (Mux) provides the same reliability guarantees, plus the multiplexing capabilities of course * It also takes care of reconnecting to peers when a failure is detected which relieves us from doing so, but any reconnection implies a reset of each peer's state machine which means we need to make sure any change to the state of pending/received messages is handled by the applicative layer - * Our [FireForget protocol](https://github.com/input-output-hk/hydra/blob/8a8e0829964132bde8949e5249a1ab303af92fb8/hydra-node/src/Hydra/Network/Ouroboros/Type.hs#L31) ignores connections/disconnections + * Our [FireForget protocol](https://github.com/cardano-scaling/hydra/blob/8a8e0829964132bde8949e5249a1ab303af92fb8/hydra-node/src/Hydra/Network/Ouroboros/Type.hs#L31) ignores connections/disconnections * Ouroboros/typed-protocols provides enough machinery to implement a reliable broadcast protocol, for example by reusing existing `[KeepAlive](https://github.com/input-output-hk/ouroboros-network/tree/master/ouroboros-network-protocols/src/Ouroboros/Network/Protocol/KeepAlive)` protocol and building a more robust point-to-point protocol than what we have now * There is a minor limitation, namely that the subscription mechanism does not handle connections invidually, but as a set of equivalent point-to-point full duplex connections whose size (valency) needs to be maintained at a certain threshold, which means that unless backed in the protocol itself, protocol state-machine and applications are not aware of the identity of the remote peer * We have built our `Network` infrastructure over the concept of relatively independent layers, each implementing a similar interface with different kind of messages, to `broadcast` messages to all peers and be notified of incoming messages through a `callback`. diff --git a/docs/adr/2023-12-06_029-use-cbor-for-tx.md b/docs/adr/2023-12-06_029-use-cbor-for-tx.md index cdca10e68e4..1e113981aee 100644 --- a/docs/adr/2023-12-06_029-use-cbor-for-tx.md +++ b/docs/adr/2023-12-06_029-use-cbor-for-tx.md @@ -13,15 +13,15 @@ Proposed ## Context * The [Hydra.Ledger.Cardano](https://github.com/input-output-hk/hydra/blob/b2dc5a0da4988631bd2c1e94b66ba6217d5db595/hydra-node/src/Hydra/Ledger/Cardano.hs#L127) module provides `ToJSON/FromJSON` instances for `Tx` and [AlonzoTx](https://github.com/input-output-hk/hydra/blob/b2dc5a0da4988631bd2c1e94b66ba6217d5db595/hydra-node/src/Hydra/Ledger/Cardano/Json.hs#L361) - * We have specified this format as part of [Hydra API](https://github.com/input-output-hk/hydra/blob/b2dc5a0da4988631bd2c1e94b66ba6217d5db595/hydra-node/json-schemas/api.yaml#L1473) + * We have specified this format as part of [Hydra API](https://github.com/cardano-scaling/hydra/blob/b2dc5a0da4988631bd2c1e94b66ba6217d5db595/hydra-node/json-schemas/api.yaml#L1473) * These instances appear in a few places as part of Hydra API: - * In the [ServerOutput](https://github.com/input-output-hk/hydra/blob/b2dc5a0da4988631bd2c1e94b66ba6217d5db595/hydra-node/src/Hydra/API/ServerOutput.hs#L51) sent by the node to clients - * In the [HydraNodeLog](https://github.com/input-output-hk/hydra/blob/b2dc5a0da4988631bd2c1e94b66ba6217d5db595/hydra-node/src/Hydra/Node.hs#L122) as part of Hydra's logging output - * In the [StateChanged](https://github.com/input-output-hk/hydra/blob/b2dc5a0da4988631bd2c1e94b66ba6217d5db595/hydra-node/src/Hydra/HeadLogic/Outcome.hs#L46) events which are persisted and allow hydra-node to restart gracefully after stopping + * In the [ServerOutput](https://github.com/cardano-scaling/hydra/blob/b2dc5a0da4988631bd2c1e94b66ba6217d5db595/hydra-node/src/Hydra/API/ServerOutput.hs#L51) sent by the node to clients + * In the [HydraNodeLog](https://github.com/cardano-scaling/hydra/blob/b2dc5a0da4988631bd2c1e94b66ba6217d5db595/hydra-node/src/Hydra/Node.hs#L122) as part of Hydra's logging output + * In the [StateChanged](https://github.com/cardano-scaling/hydra/blob/b2dc5a0da4988631bd2c1e94b66ba6217d5db595/hydra-node/src/Hydra/HeadLogic/Outcome.hs#L46) events which are persisted and allow hydra-node to restart gracefully after stopping * In other places the hydra-node produces, expects, or accepts a CBOR-encoded transaction: - * In the [Network.Message](https://github.com/input-output-hk/hydra/blob/b2dc5a0da4988631bd2c1e94b66ba6217d5db595/hydra-node/src/Hydra/Network/Message.hs#L20) exchanged between the nodes - * In the [ClientInput](https://github.com/input-output-hk/hydra/blob/b2dc5a0da4988631bd2c1e94b66ba6217d5db595/hydra-node/src/Hydra/API/ClientInput.hs#L9) from clients submitting `NewTx` commands - * In the [HTTPServer](https://github.com/input-output-hk/hydra/blob/b2dc5a0da4988631bd2c1e94b66ba6217d5db595/hydra-node/src/Hydra/API/HTTPServer.hs#L297) API + * In the [Network.Message](https://github.com/cardano-scaling/hydra/blob/b2dc5a0da4988631bd2c1e94b66ba6217d5db595/hydra-node/src/Hydra/Network/Message.hs#L20) exchanged between the nodes + * In the [ClientInput](https://github.com/cardano-scaling/hydra/blob/b2dc5a0da4988631bd2c1e94b66ba6217d5db595/hydra-node/src/Hydra/API/ClientInput.hs#L9) from clients submitting `NewTx` commands + * In the [HTTPServer](https://github.com/cardano-scaling/hydra/blob/b2dc5a0da4988631bd2c1e94b66ba6217d5db595/hydra-node/src/Hydra/API/HTTPServer.hs#L297) API * Note that in the latter 2 cases, the hydra-node _accepts_ a hex-CBOR-encoded _JSON string_ to represent a transaction and this particular case is handled directly in the [FromJSON](https://github.com/input-output-hk/hydra/blob/b2dc5a0da4988631bd2c1e94b66ba6217d5db595/hydra-node/src/Hydra/Ledger/Cardano/Json.hs#L388) instance for transactions where 3 different representations are even accepted: * JSON object detailing the transaction * A JSON string representing CBOR-encoding of a transaction diff --git a/docs/benchmarks/index.md b/docs/benchmarks/index.md index 6841256df8b..1e4988073c8 100644 --- a/docs/benchmarks/index.md +++ b/docs/benchmarks/index.md @@ -7,7 +7,7 @@ sidebar_position: 1 This section provides up-to-date data about the known limitations Hydra Head on-chain protocol. Cardano transactions (and blocks) have limits on the transaction size, execution cost, number of inputs and outputs which are dependent on the network parameters and which impact the capabilities of the Head protocol: How many parties can take part in a Head, how many UTxO can be committed to the Head, how many can be fan-out... As the on-chain scripts and transactions mature and are optimised, and the underlying Cardano chain evolves with increased parameters and more efficient scripts execution, those limits will change. -The data provided in those pages is _generated_ by Hydra's [Continuous Integration](https://github.com/input-output-hk/hydra/actions/workflows/ci-nix.yaml) process and thus guaranteed to reflect the current state of the code. +The data provided in those pages is _generated_ by Hydra's [Continuous Integration](https://github.com/cardano-scaling/hydra/actions/workflows/ci-nix.yaml) process and thus guaranteed to reflect the current state of the code. ```mdx-code-block import DocCardList from '@theme/DocCardList'; diff --git a/docs/docs/configuration.md b/docs/docs/configuration.md index cb3adadc025..fc64bce35ff 100644 --- a/docs/docs/configuration.md +++ b/docs/docs/configuration.md @@ -34,7 +34,7 @@ hydra-node gen-hydra-key --output-file my-key This command creates two files: `my-key.sk` and `my-key.vk` containing Hydra keys suitable for use inside a head. -For demonstration purposes, we also provide demo key pairs (`alice.{vk,sk}`, `bob.{vk,sk}`, and `carol.{vk,sk}`) in our [demo folder](https://github.com/input-output-hk/hydra/tree/master/demo). These demo keys should not be used in production. +For demonstration purposes, we also provide demo key pairs (`alice.{vk,sk}`, `bob.{vk,sk}`, and `carol.{vk,sk}`) in our [demo folder](https://github.com/cardano-scaling/hydra/tree/master/demo). These demo keys should not be used in production. ### Contestation period diff --git a/docs/docs/dev/architecture/architecture-c4.puml b/docs/docs/dev/architecture/architecture-c4.puml index f66c9c519bf..693f7a85cca 100644 --- a/docs/docs/dev/architecture/architecture-c4.puml +++ b/docs/docs/dev/architecture/architecture-c4.puml @@ -5,14 +5,14 @@ title "Hydra Components" AddElementTag("external", $bgColor="#23aa12") Container_Boundary(hydra_node, "Hydra Node") { - Component(persistence, "Persistence", "JSON/FS", "Persists state of the head on disk", $link="https://github.com/input-output-hk/hydra/blob/master/hydra-node/src/Hydra/Persistence.hs") - Component(head_logic, "Head Logic", "", "Maintains internal Head state and processes events", $link="https://github.com/input-output-hk/hydra/blob/master/hydra-node/src/Hydra/HeadLogic.hs") - Component(api_server, "API Server", "", "Handle client commands & queries and serves outputs", $link="https://github.com/input-output-hk/hydra/blob/master/hydra-node/src/Hydra/API/Server.hs") - Component(chain, "Chain", "", "Connection to Cardano\nObserve txs on-chain and post tx to chain", $link="https://github.com/input-output-hk/hydra/blob/master/hydra-node/src/Hydra/Chain.hs") - Component(wallet, "Wallet", "", "Embedded Wallet to sign transactions and pay fees", $link="https://github.com/input-output-hk/hydra/blob/master/hydra-node/src/Hydra/Chain/Direct/Wallet.hs") - Component(network, "Network", "", "Manages connections to peers", $link="https://github.com/input-output-hk/hydra/blob/master/hydra-node/src/Hydra/Network.hs") - Component(logging, "Logging", "", "Dump JSON to stdout", $link="https://github.com/input-output-hk/hydra/blob/master/hydra-node/src/Hydra/Logging.hs") - Component(monitoring, "Monitoring", "", "Exposes Prometheus metrics", $link="https://github.com/input-output-hk/hydra/blob/master/hydra-node/src/Hydra/Logging/Monitoring.hs") + Component(persistence, "Persistence", "JSON/FS", "Persists state of the head on disk", $link="https://github.com/cardano-scaling/hydra/blob/master/hydra-node/src/Hydra/Persistence.hs") + Component(head_logic, "Head Logic", "", "Maintains internal Head state and processes events", $link="https://github.com/cardano-scaling/hydra/blob/master/hydra-node/src/Hydra/HeadLogic.hs") + Component(api_server, "API Server", "", "Handle client commands & queries and serves outputs", $link="https://github.com/cardano-scaling/hydra/blob/master/hydra-node/src/Hydra/API/Server.hs") + Component(chain, "Chain", "", "Connection to Cardano\nObserve txs on-chain and post tx to chain", $link="https://github.com/cardano-scaling/hydra/blob/master/hydra-node/src/Hydra/Chain.hs") + Component(wallet, "Wallet", "", "Embedded Wallet to sign transactions and pay fees", $link="https://github.com/cardano-scaling/hydra/blob/master/hydra-node/src/Hydra/Chain/Direct/Wallet.hs") + Component(network, "Network", "", "Manages connections to peers", $link="https://github.com/cardano-scaling/hydra/blob/master/hydra-node/src/Hydra/Network.hs") + Component(logging, "Logging", "", "Dump JSON to stdout", $link="https://github.com/cardano-scaling/hydra/blob/master/hydra-node/src/Hydra/Logging.hs") + Component(monitoring, "Monitoring", "", "Exposes Prometheus metrics", $link="https://github.com/cardano-scaling/hydra/blob/master/hydra-node/src/Hydra/Logging/Monitoring.hs") Component(ledger, "Cardano Ledger", "", "Maintains Layer 2 State", $tags="external") Lay_U(head_logic, persistence) @@ -30,7 +30,7 @@ Container(hydra_node_peer, "Hydra Node (peer)", "Local cardano-node") Container(cardano_node, "Cardano Node", "Local cadano-node") Container(cardano_node_peer, "Cardano Node (peer)", "Local cardano-node") Container(hydra_client, "Hydra Client", "") -Component(smart_contracts, "Hydra Smart Contracts", "Plutus", "On-chain smart contracts controlling the behaviour of the protocol on-chain", $link="https://github.com/input-output-hk/hydra/tree/master/hydra-plutus") +Component(smart_contracts, "Hydra Smart Contracts", "Plutus", "On-chain smart contracts controlling the behaviour of the protocol on-chain", $link="https://github.com/cardano-scaling/hydra/tree/master/hydra-plutus") Rel(chain, smart_contracts, "Use", "") BiRel_D(chain, cardano_node, "", "N2C protocol") BiRel_L(cardano_node, cardano_node_peer, "", "N2N protocol") diff --git a/docs/docs/dev/architecture/index.md b/docs/docs/dev/architecture/index.md index c1bda2c9bd6..0e630c5182a 100644 --- a/docs/docs/dev/architecture/index.md +++ b/docs/docs/dev/architecture/index.md @@ -31,7 +31,7 @@ Messages are exchanged between nodes on different internal transitions and are a The messages exchanged through the _Hydra Network_ layer between participants are authenticated: Each message is -[signed](https://github.com/input-output-hk/hydra/issues/727) using +[signed](https://github.com/cardano-scaling/hydra/issues/727) using the Hydra signing key of the emitting party which is identified by the corresponding verification key. When a message with an unknown or incorrect signature is received, it is dropped and a notification diff --git a/docs/docs/dev/architecture/networking.md b/docs/docs/dev/architecture/networking.md index 37f91b823c6..11a8c0dec00 100644 --- a/docs/docs/dev/architecture/networking.md +++ b/docs/docs/dev/architecture/networking.md @@ -47,7 +47,7 @@ Discussion quickly derived on performance, with Neil Davies giving some interest - Within cardano network, propagation of a single empty block takes 400ms (to reach 10K nodes) - ouroboros network should withstand 1000s of connections (there are some system-level limits) - Modelling Hydra network - - A logical framework for modelling performance of network associate CDF with time for a message to appear at all nodes (this is what is done in the [hydra-sim](https://github.com/input-output-hk/hydra-sim) + - A logical framework for modelling performance of network associate CDF with time for a message to appear at all nodes (this is what is done in the [hydra-sim](https://github.com/cardano-scaling/hydra-sim) - We could define a layer w/ the semantics we expect, eg. Snocket = PTP connection w/ ordered guaranteed messages delivery. Do we need that in Hydra? - How about [Wireguard](https://wireguard.io)? It's a very interesting approach, with some shortcomings: - no global addressing scheme @@ -57,7 +57,7 @@ Discussion quickly derived on performance, with Neil Davies giving some interest ## Cardano Networking -See [this wiki page](https://github.com/input-output-hk/hydra.wiki/blob/master/Networking.md#L1) for detailed notes about how Cardano network works and uses Ouroboros. +See [this wiki page](https://github.com/cardano-scaling/hydra.wiki/blob/master/Networking.md#L1) for detailed notes about how Cardano network works and uses Ouroboros. - Cardano is a global network spanning 1000s of nodes, with nodes coming and going and a widely varying topology. Its main purpose is _block propagation_: Blocks produced by some nodes according to the consensus rules needs to reach every node in the network in less than 20 seconds. - Nodes cannot be connected to all other nodes, as such block diffusion occurs through some form of _gossipping_ whereby a node is connected to a limited set of peers with which it exchanges blocks diff --git a/docs/docs/dev/specification.md b/docs/docs/dev/specification.md index 61d045f3c50..0e9c7f96b75 100644 --- a/docs/docs/dev/specification.md +++ b/docs/docs/dev/specification.md @@ -1,6 +1,6 @@ # Specification -The specification is currently written in LaTeX and can be [edited](https://github.com/input-output-hk/hydra/tree/master/spec) in the Hydra repository. You can view the rendered version below or download it for fullscreen viewing [here](/hydra-spec.pdf). +The specification is currently written in LaTeX and can be [edited](https://github.com/cardano-scaling/hydra/tree/master/spec) in the Hydra repository. You can view the rendered version below or download it for fullscreen viewing [here](/hydra-spec.pdf). import HydraSpecUrl from '@site/static/hydra-spec.pdf'; diff --git a/docs/docs/getting-started.md b/docs/docs/getting-started.md index d793758f1df..19a115ec9e1 100644 --- a/docs/docs/getting-started.md +++ b/docs/docs/getting-started.md @@ -25,7 +25,7 @@ These instructions have been tested only on Linux environments (Ubuntu, NixOS). All commands below are written as if executed from the `demo` folder in the project repository. Ensure you clone the repository, switch into the `demo` folder, and pull the latest Docker images: ```shell -git clone git@github.com:input-output-hk/hydra.git +git clone git@github.com:cardano-scaling/hydra.git cd hydra/demo docker compose pull ``` diff --git a/docs/docs/how-to/commit-blueprint.md b/docs/docs/how-to/commit-blueprint.md index 81bcbc6f8ab..f102b29f023 100644 --- a/docs/docs/how-to/commit-blueprint.md +++ b/docs/docs/how-to/commit-blueprint.md @@ -100,7 +100,7 @@ cardano-cli query protocol-parameters \ ## Step 5 Start the `hydra-node` as a _single_ party head instance. -Note: The value `6264cee4d5eab3fb58ab67f3899ecbcc0d7e72732a2d9c1c5d638115db6ca711` comes from the `hydra-node` release [0.16.0](https://github.com/input-output-hk/hydra/releases/tag/0.16.0). +Note: The value `6264cee4d5eab3fb58ab67f3899ecbcc0d7e72732a2d9c1c5d638115db6ca711` comes from the `hydra-node` release [0.16.0](https://github.com/cardano-scaling/hydra/releases/tag/0.16.0). ```shell hydra-node \ diff --git a/docs/docs/how-to/operating-hydra.md b/docs/docs/how-to/operating-hydra.md index 0bbc59462fd..53e165b02b7 100644 --- a/docs/docs/how-to/operating-hydra.md +++ b/docs/docs/how-to/operating-hydra.md @@ -12,7 +12,7 @@ This page guides Hydra users on troubleshooting issues when running their instan ## Example setup -We offer sample node configurations that will help you get started with hosting a Hydra node on virtual machines in the cloud. These configurations are available in the [`sample-node-config/` directory](https://github.com/input-output-hk/hydra/tree/master/sample-node-config/). +We offer sample node configurations that will help you get started with hosting a Hydra node on virtual machines in the cloud. These configurations are available in the [`sample-node-config/` directory](https://github.com/cardano-scaling/hydra/tree/master/sample-node-config/). ### Google Cloud with Terraform @@ -62,7 +62,7 @@ hydra_head_tx_confirmation_time_ms_count 0 * Ensure the `hydra-node` is connected to a `cardano-node` operating on the correct network. Verify the `--network` command-line argument and the `cardano-node` configuration. * Remember, the `hydra-node` cannot start if it cannot connect to the `cardano-node`, which might require time as the `cardano-node` must revalidate its database and potentially reconstruct its ledger state upon startup. Its connections are not open until it is fully prepared. If running as a service or a container, ensure that the orchestrator restarts the process when it crashes. -* Check that the _Scripts_ transaction identifier is valid. This identifier is provided on the [release](https://github.com/input-output-hk/hydra/releases/tag/0.10.0) page for the three major networks (`preview`, `pre-production`, `mainnet`). +* Check that the _Scripts_ transaction identifier is valid. This identifier is provided on the [release](https://github.com/cardano-scaling/hydra/releases/tag/0.10.0) page for the three major networks (`preview`, `pre-production`, `mainnet`). * Verify that the `hydra-node`'s _Cardano signing key_ is consistent with the _Verification key_ from the `Init` transaction. Ensure the `--cardano-signing-key` parameter points to the correct key, and that peers have the accurate `--cardano-verification-key` for your node. * Confirm that peers' _Cardano verification keys_ are accurate. This mirrors the above issue; check parameters on all peers. diff --git a/docs/docs/index.md b/docs/docs/index.md index 1a7543a9ef3..3bf475954aa 100644 --- a/docs/docs/index.md +++ b/docs/docs/index.md @@ -35,4 +35,4 @@ see also sections 7, 8 and 9 of the [Apache 2.0 License][license]. Now, without further ado, you can learn more about the protocol by visiting the [protocol overview page](./protocol-overview) or directly dive into [getting started using a local devnet](./getting-started). [known-issues]: ./known-issues.md -[license]: https://github.com/input-output-hk/hydra/blob/master/LICENSE +[license]: https://github.com/cardano-scaling/hydra/blob/master/LICENSE diff --git a/docs/docs/installation.md b/docs/docs/installation.md index 73aa7e07e08..67aa12f368c 100644 --- a/docs/docs/installation.md +++ b/docs/docs/installation.md @@ -11,13 +11,13 @@ Selecting the right installation method for the `hydra-node` depends on your req The quickest way to install and run a `hydra-node` is by using Docker images: ```shell -docker pull ghcr.io/input-output-hk/hydra-node -docker run --rm ghcr.io/input-output-hk/hydra-node --help +docker pull ghcr.io/cardano-scaling/hydra-node +docker run --rm ghcr.io/cardano-scaling/hydra-node --help ``` ### Prebuilt binaries -We provide statically linked binaries of `hydra-node` and `hydra-tui` for x86_64 Linux and ARM64 MacOS platforms. These binaries are available as attachments in our [github releases](https://github.com/input-output-hk/hydra/releases). +We provide statically linked binaries of `hydra-node` and `hydra-tui` for x86_64 Linux and ARM64 MacOS platforms. These binaries are available as attachments in our [github releases](https://github.com/cardano-scaling/hydra/releases). ### Build from source diff --git a/docs/docs/known-issues.md b/docs/docs/known-issues.md index 67826c4a249..54dfceb4eb9 100644 --- a/docs/docs/known-issues.md +++ b/docs/docs/known-issues.md @@ -16,10 +16,10 @@ Currently, participants may be denied access to their funds by other protocol pa See these resources for additional information about reducing the risk of locking up funds in a Hydra head: -* [Directly open heads](https://github.com/input-output-hk/hydra/issues/1329) -* [Always abortable head](https://github.com/input-output-hk/hydra/issues/699) -* [Limit size/complexity of UTXOs in the head](https://github.com/input-output-hk/hydra/issues/698) -* [Only sign closable snapshots](https://github.com/input-output-hk/hydra/issues/370) +* [Directly open heads](https://github.com/cardano-scaling/hydra/issues/1329) +* [Always abortable head](https://github.com/cardano-scaling/hydra/issues/699) +* [Limit size/complexity of UTXOs in the head](https://github.com/cardano-scaling/hydra/issues/698) +* [Only sign closable snapshots](https://github.com/cardano-scaling/hydra/issues/370) ### Training wheels diff --git a/docs/docs/tutorial/index.md b/docs/docs/tutorial/index.md index 1964d19fa25..0aaacfc57a8 100644 --- a/docs/docs/tutorial/index.md +++ b/docs/docs/tutorial/index.md @@ -33,7 +33,7 @@ After ensuring the tools above are available, begin by downloading pre-built bin ```shell mkdir -p bin version=0.17.0 -curl -L -O https://github.com/input-output-hk/hydra/releases/download/${version}/hydra-x86_64-linux-${version}.zip +curl -L -O https://github.com/cardano-scaling/hydra/releases/download/${version}/hydra-x86_64-linux-${version}.zip unzip -d bin hydra-x86_64-linux-${version}.zip curl -L -o - https://github.com/IntersectMBO/cardano-node/releases/download/8.11.0/cardano-node-8.11.0-linux.tar.gz \ | tar xz ./bin/cardano-node ./bin/cardano-cli @@ -48,7 +48,7 @@ chmod +x bin/* ```shell mkdir -p bin version=0.17.0 -curl -L -O https://github.com/input-output-hk/hydra/releases/download/${version}/hydra-aarch64-darwin-${version}.zip +curl -L -O https://github.com/cardano-scaling/hydra/releases/download/${version}/hydra-aarch64-darwin-${version}.zip unzip -d bin hydra-aarch64-darwin-${version}.zip curl -L -o - https://github.com/IntersectMBO/cardano-node/releases/download/8.11.0/cardano-node-8.11.0-macos.tar.gz \ | tar xz --wildcards ./bin/cardano-node ./bin/cardano-cli './bin/*.dylib' @@ -347,7 +347,7 @@ In summary, the Hydra head participants exchanged and agreed on: ## Step 3. Start the Hydra node -Scripts are pre-published for all [released](https://github.com/input-output-hk/hydra/releases) HYDRA_VERSIONs of the `hydra-node` and common Cardano networks. Consult the [user manual](../configuration#reference-scripts) for guidance on publishing your own scripts. +Scripts are pre-published for all [released](https://github.com/cardano-scaling/hydra/releases) HYDRA_VERSIONs of the `hydra-node` and common Cardano networks. Consult the [user manual](../configuration#reference-scripts) for guidance on publishing your own scripts. Start the `hydra-node` using these parameters: @@ -362,7 +362,7 @@ hydra-node \ --persistence-dir persistence-alice \ --cardano-signing-key credentials/alice-node.sk \ --hydra-signing-key credentials/alice-hydra.sk \ - --hydra-scripts-tx-id $(curl https://raw.githubusercontent.com/input-output-hk/hydra/master/networks.json | jq -r ".preprod.\"${version}\"") \ + --hydra-scripts-tx-id $(curl https://raw.githubusercontent.com/cardano-scaling/hydra/master/networks.json | jq -r ".preprod.\"${version}\"") \ --ledger-protocol-parameters protocol-parameters.json \ --testnet-magic 1 \ --node-socket node.socket \ @@ -385,7 +385,7 @@ hydra-node \ --persistence-dir persistence-bob \ --cardano-signing-key credentials/bob-node.sk \ --hydra-signing-key credentials/bob-hydra.sk \ - --hydra-scripts-tx-id $(curl https://raw.githubusercontent.com/input-output-hk/hydra/master/networks.json | jq -r ".preprod.\"${version}\"") \ + --hydra-scripts-tx-id $(curl https://raw.githubusercontent.com/cardano-scaling/hydra/master/networks.json | jq -r ".preprod.\"${version}\"") \ --ledger-protocol-parameters protocol-parameters.json \ --testnet-magic 1 \ --node-socket node.socket \ @@ -596,7 +596,7 @@ The `hydra-node` will then submit a protocol transaction with the last known sna :::caution Known bug You might need to submit the `Close` command multiple times if the head is not getting closed within approximately 30 seconds. -See [#1039](https://github.com/input-output-hk/hydra/issues/1039) for details. +See [#1039](https://github.com/cardano-scaling/hydra/issues/1039) for details. ::: The message will include a `contestationDeadline`, set using the configurable `--contestation-period`. Until this deadline, the closing snapshot can be contested with a more recent, multi-signed snapshot. Your `hydra-node` would contest automatically for you if the closed snapshot is not the last known one. diff --git a/docs/docusaurus.config.js b/docs/docusaurus.config.js index 8dd5ca2955e..c4cc982fecf 100644 --- a/docs/docusaurus.config.js +++ b/docs/docusaurus.config.js @@ -10,7 +10,7 @@ const customFields = { apiSpecUrl: "api.yaml", }; -const editUrl = "https://github.com/input-output-hk/hydra/tree/master/docs"; +const editUrl = "https://github.com/cardano-scaling/hydra/tree/master/docs"; /** @type {import('@docusaurus/types').Config} */ const config = { @@ -165,7 +165,7 @@ const config = { position: "right", }, { - href: "https://github.com/input-output-hk/hydra", + href: "https://github.com/cardano-scaling/hydra", label: "GitHub", position: "right", }, @@ -179,7 +179,7 @@ const config = { items: [ { label: "Coding Standards", - to: "https://github.com/input-output-hk/hydra/wiki/Coding-Standards", + to: "https://github.com/cardano-scaling/hydra/wiki/Coding-Standards", }, { label: "Architectural Decision Records", @@ -187,7 +187,7 @@ const config = { }, { label: "Testing Strategy", - to: "https://github.com/input-output-hk/hydra/wiki/Testing-Strategy", + to: "https://github.com/cardano-scaling/hydra/wiki/Testing-Strategy", }, ], }, @@ -200,7 +200,7 @@ const config = { }, { label: "Github Discussions", - href: "https://github.com/input-output-hk/hydra/discussions", + href: "https://github.com/cardano-scaling/hydra/discussions", }, { label: "Stack Exchange", @@ -221,7 +221,7 @@ const config = { }, { label: "Logbook", - to: "https://github.com/input-output-hk/hydra/wiki/Logbook", + to: "https://github.com/cardano-scaling/hydra/wiki/Logbook", }, ], }, @@ -238,7 +238,7 @@ const config = { }, { label: "Contributors", - to: "https://github.com/input-output-hk/hydra/graphs/contributors", + to: "https://github.com/cardano-scaling/hydra/graphs/contributors", }, ], }, diff --git a/docs/sidebars.js b/docs/sidebars.js index 3ad8d17d427..1e7005e8e6a 100644 --- a/docs/sidebars.js +++ b/docs/sidebars.js @@ -40,7 +40,7 @@ module.exports = { }, { type: "link", - href: "https://github.com/input-output-hk/hydra/releases", + href: "https://github.com/cardano-scaling/hydra/releases", label: "Release notes", }, { diff --git a/docs/src/components/DocumentMetadata/index.tsx b/docs/src/components/DocumentMetadata/index.tsx index c8d6b5ddb68..6f6ef1b998f 100644 --- a/docs/src/components/DocumentMetadata/index.tsx +++ b/docs/src/components/DocumentMetadata/index.tsx @@ -20,7 +20,7 @@ interface TranslatedMetadata { const style = { marginBottom: '1em' } const renderMetadata = ({ lastUpdatedAt, commitHash }: Metadata) => { - let link = `https://github.com/input-output-hk/hydra/commit/${commitHash}` + let link = `https://github.com/cardano-scaling/hydra/commit/${commitHash}` return (
Last updated:  @@ -36,7 +36,7 @@ const renderTranslatedMetadata = ({ translationUpdatedAt, commitHash, }: TranslatedMetadata) => { - let link = `https://github.com/input-output-hk/hydra/commit/${commitHash}` + let link = `https://github.com/cardano-scaling/hydra/commit/${commitHash}` const diffMs = moment(translationUpdatedAt).diff(sourceUpdatedAt) const outdated = diffMs < 0 const maybeRenderWarning = outdated && diff --git a/docs/standalone/audit-guidelines.md b/docs/standalone/audit-guidelines.md index 337f106172a..c0708edbe7f 100644 --- a/docs/standalone/audit-guidelines.md +++ b/docs/standalone/audit-guidelines.md @@ -12,7 +12,7 @@ Shall you decide to share your findings with us, please consider the following, ## Reporting a Vulnerability -If you discover a security vulnerability in Hydra, we ask that you report it to us confidentially. See [`SECURITY.md`](https://github.com/input-output-hk/hydra/blob/master/SECURITY.md) on how to report a security vulnerability. +If you discover a security vulnerability in Hydra, we ask that you report it to us confidentially. See [`SECURITY.md`](https://github.com/cardano-scaling/hydra/blob/master/SECURITY.md) on how to report a security vulnerability. ## Context and assumptions @@ -123,8 +123,8 @@ The [Hydra Head specification](/docs/dev/specification) captures these deviation With Hydra Head Protocol Implementation we refer to the software component that is used to operate a node in the Hydra Head protocol. The `hydra-node` allows its users to open a head, lock funds in it, connect to peers, process transactions as a layer 2, close a head and unlock the corresponding funds. It is comprised by the Hydra plutus scripts, Hydra head chain layer, layer 2 code, network communication between peers, and an API for clients to connect and use the node. -- Source code repository: [input-output-hk/hydra](https://github.com/input-output-hk/hydra) -- Version ready to be audited: Any [release](https://github.com/input-output-hk/hydra/releases) after version 0.10.0 +- Source code repository: [cardano-scaling/hydra](https://github.com/cardano-scaling/hydra) +- Version ready to be audited: Any [release](https://github.com/cardano-scaling/hydra/releases) after version 0.10.0 The following parts are described below: - Hydra plutus scripts (on-chain code) @@ -132,12 +132,12 @@ The following parts are described below: #### Artifact 2.1: Hydra plutus scripts (on-chain code) -Hydra plutus scripts source code can be found in the [hydra-plutus module](https://github.com/input-output-hk/hydra/tree/master/hydra-plutus). +Hydra plutus scripts source code can be found in the [hydra-plutus module](https://github.com/cardano-scaling/hydra/tree/master/hydra-plutus). -Hydra plutus mutation based testing can be found in the [hydra-node module](https://github.com/input-output-hk/hydra/tree/master/hydra-node) in test/Hydra/Chain/Direct/Contract/. +Hydra plutus mutation based testing can be found in the [hydra-node module](https://github.com/cardano-scaling/hydra/tree/master/hydra-node) in test/Hydra/Chain/Direct/Contract/. #### Artifact 2.2: Hydra node chain layer code (off-chain code) -Hydra node chain layer code can be found in the [hydra-node module](https://github.com/input-output-hk/hydra/tree/master/hydra-node/src/Hydra/Chain) in src/Hydra/Chain/Direct/ +Hydra node chain layer code can be found in the [hydra-node module](https://github.com/cardano-scaling/hydra/tree/master/hydra-node/src/Hydra/Chain) in src/Hydra/Chain/Direct/ -Hydra node chain layer tests can be found in the [hydra-node module](https://github.com/input-output-hk/hydra/tree/master/hydra-node/test/Hydra/Chain) in test/Hydra/Chain/Direct/ +Hydra node chain layer tests can be found in the [hydra-node module](https://github.com/cardano-scaling/hydra/tree/master/hydra-node/test/Hydra/Chain) in test/Hydra/Chain/Direct/ diff --git a/docs/standalone/contribute.md b/docs/standalone/contribute.md index 8ebd4e18c95..30ac282881e 100644 --- a/docs/standalone/contribute.md +++ b/docs/standalone/contribute.md @@ -16,8 +16,8 @@ We are exploring use cases and how to empower them with Hydra ourselves and with ### *Comment* on the roadmap -Our development roadmap is public [on Github](https://github.com/orgs/input-output-hk/projects/21/views/7). If you have questions or an item is of special interest to your team, leave a comment or start a new [discussion](https://github.com/input-output-hk/hydra/discussions). +Our development roadmap is public [on Github](https://github.com/orgs/input-output-hk/projects/21/views/7). If you have questions or an item is of special interest to your team, leave a comment or start a new [discussion](https://github.com/cardano-scaling/hydra/discussions). :::info -Our [Contribution Guidelines](https://github.com/input-output-hk/hydra/blob/master/CONTRIBUTING.md) on the repository hold more details on how to contribute. +Our [Contribution Guidelines](https://github.com/cardano-scaling/hydra/blob/master/CONTRIBUTING.md) on the repository hold more details on how to contribute. ::: diff --git a/hydra-cardano-api/hydra-cardano-api.cabal b/hydra-cardano-api/hydra-cardano-api.cabal index f46274b5aa4..c1eda2c875c 100644 --- a/hydra-cardano-api/hydra-cardano-api.cabal +++ b/hydra-cardano-api/hydra-cardano-api.cabal @@ -11,7 +11,7 @@ license-files: source-repository head type: git - location: https://github.com/input-output-hk/hydra + location: https://github.com/cardano-scaling/hydra common project-config default-language: GHC2021 diff --git a/hydra-chain-observer/hydra-chain-observer.cabal b/hydra-chain-observer/hydra-chain-observer.cabal index 200f11d2e79..541e88aab36 100644 --- a/hydra-chain-observer/hydra-chain-observer.cabal +++ b/hydra-chain-observer/hydra-chain-observer.cabal @@ -11,7 +11,7 @@ license-files: source-repository head type: git - location: https://github.com/input-output-hk/hydra + location: https://github.com/cardano-scaling/hydra common project-config default-language: GHC2021 diff --git a/hydra-cluster/README.md b/hydra-cluster/README.md index 09cfb2e88e3..b5433128703 100644 --- a/hydra-cluster/README.md +++ b/hydra-cluster/README.md @@ -50,7 +50,7 @@ To run the smoke test against the official cardano testnet using a local `state-testnet` directory (to re-use the synchronized chain db): Note: To get the transaction id for `--hydra-scripts-tx-id` parameter you can -consult our [release page](https://github.com/input-output-hk/hydra/releases) +consult our [release page](https://github.com/cardano-scaling/hydra/releases) where you can find pre-published Hydra scripts for different networks. ```sh diff --git a/hydra-cluster/hydra-cluster.cabal b/hydra-cluster/hydra-cluster.cabal index f1dbdf02ad4..9b3d18fb2d0 100644 --- a/hydra-cluster/hydra-cluster.cabal +++ b/hydra-cluster/hydra-cluster.cabal @@ -41,7 +41,7 @@ data-files: source-repository head type: git - location: https://github.com/input-output-hk/hydra + location: https://github.com/cardano-scaling/hydra common project-config default-language: GHC2021 diff --git a/hydra-explorer/hydra-explorer.cabal b/hydra-explorer/hydra-explorer.cabal index 2a3abb64b2d..36269a22d1e 100644 --- a/hydra-explorer/hydra-explorer.cabal +++ b/hydra-explorer/hydra-explorer.cabal @@ -11,7 +11,7 @@ license-files: source-repository head type: git - location: https://github.com/input-output-hk/hydra/hydra-explorer/ + location: https://github.com/cardano-scaling/hydra/hydra-explorer/ common project-config default-language: GHC2021 diff --git a/hydra-node/hydra-node.cabal b/hydra-node/hydra-node.cabal index ffb44a8cd51..df2089b8c15 100644 --- a/hydra-node/hydra-node.cabal +++ b/hydra-node/hydra-node.cabal @@ -15,7 +15,7 @@ data-files: source-repository head type: git - location: https://github.com/input-output-hk/hydra + location: https://github.com/cardano-scaling/hydra common project-config default-language: GHC2021 diff --git a/hydra-node/json-schemas/api.yaml b/hydra-node/json-schemas/api.yaml index 5d7d76e8284..0096086735c 100644 --- a/hydra-node/json-schemas/api.yaml +++ b/hydra-node/json-schemas/api.yaml @@ -18,7 +18,7 @@ info: license: name: Apache 2.0 - url: https://raw.githubusercontent.com/input-output-hk/hydra/master/LICENSE + url: https://raw.githubusercontent.com/cardano-scaling/hydra/master/LICENSE defaultContentType: application/json diff --git a/hydra-node/json-schemas/logs.yaml b/hydra-node/json-schemas/logs.yaml index 659ad43778b..b82e9506988 100644 --- a/hydra-node/json-schemas/logs.yaml +++ b/hydra-node/json-schemas/logs.yaml @@ -1,5 +1,5 @@ --- -"$id": https://raw.githubusercontent.com/input-output-hk/hydra/master/hydra-node/json-schemas/ +"$id": https://raw.githubusercontent.com/cardano-scaling/hydra/master/hydra-node/json-schemas/ "$schema": http://json-schema.org/draft/2020-12/schema "$comment": A description of the log items produced by a Hydra node title: Hydra Log API diff --git a/hydra-node/src/Hydra/Ledger/Cardano/Builder.hs b/hydra-node/src/Hydra/Ledger/Cardano/Builder.hs index 1a35217022f..9bbecdec571 100644 --- a/hydra-node/src/Hydra/Ledger/Cardano/Builder.hs +++ b/hydra-node/src/Hydra/Ledger/Cardano/Builder.hs @@ -47,7 +47,7 @@ instance Exception InvalidTransactionException -- scripts and no protocol parameters (needed to compute the script integrity -- hash). This is also added by our wallet at the moment and this ugly -- work-around will be removed eventually (related item --- [215](https://github.com/input-output-hk/hydra/issues/215). +-- [215](https://github.com/cardano-scaling/hydra/issues/215). -- -- So we currently bypass this by having default but seemingly innofensive -- values for collaterals and protocol params in the 'empty' value diff --git a/hydra-node/src/Hydra/Logging.hs b/hydra-node/src/Hydra/Logging.hs index 2e1a26c98cf..987d94b3f6b 100644 --- a/hydra-node/src/Hydra/Logging.hs +++ b/hydra-node/src/Hydra/Logging.hs @@ -3,7 +3,7 @@ -- | Adapter module to the actual logging framework. -- All Hydra node components implements /Structured logging/ via [contra-tracer](https://hackage.haskell.org/package/contra-tracer) -- generic logging framework. All logs are output in [JSON](https://www.json.org/json-en.html) in a format which is --- documented in a [JSON-Schema](https://github.com/input-output-hk/hydra/blob/master/hydra-node/json-schemas/logs.yaml). +-- documented in a [JSON-Schema](https://github.com/cardano-scaling/hydra/blob/master/hydra-node/json-schemas/logs.yaml). module Hydra.Logging ( -- * Tracer Tracer (..), diff --git a/hydra-plutus-extras/hydra-plutus-extras.cabal b/hydra-plutus-extras/hydra-plutus-extras.cabal index ce81a28dd88..8a338975809 100644 --- a/hydra-plutus-extras/hydra-plutus-extras.cabal +++ b/hydra-plutus-extras/hydra-plutus-extras.cabal @@ -13,7 +13,7 @@ license-files: source-repository head type: git - location: https://github.com/input-output-hk/hydra + location: https://github.com/cardano-scaling/hydra common project-config default-language: GHC2021 diff --git a/hydra-plutus/hydra-plutus.cabal b/hydra-plutus/hydra-plutus.cabal index 4ee6373498e..654da0c2b8d 100644 --- a/hydra-plutus/hydra-plutus.cabal +++ b/hydra-plutus/hydra-plutus.cabal @@ -11,7 +11,7 @@ license-files: source-repository head type: git - location: https://github.com/input-output-hk/hydra + location: https://github.com/cardano-scaling/hydra common project-config default-language: GHC2021 diff --git a/hydra-prelude/hydra-prelude.cabal b/hydra-prelude/hydra-prelude.cabal index a14c5394e87..58748922d7d 100644 --- a/hydra-prelude/hydra-prelude.cabal +++ b/hydra-prelude/hydra-prelude.cabal @@ -11,7 +11,7 @@ license-files: source-repository head type: git - location: https://github.com/input-output-hk/hydra + location: https://github.com/cardano-scaling/hydra library hs-source-dirs: src diff --git a/hydra-test-utils/hydra-test-utils.cabal b/hydra-test-utils/hydra-test-utils.cabal index e954caa759c..1eb9360cb98 100644 --- a/hydra-test-utils/hydra-test-utils.cabal +++ b/hydra-test-utils/hydra-test-utils.cabal @@ -11,7 +11,7 @@ license-files: source-repository head type: git - location: https://github.com/input-output-hk/hydra + location: https://github.com/cardano-scaling/hydra common package-config default-language: GHC2021 diff --git a/hydra-test-utils/src/Test/Hydra/Prelude.hs b/hydra-test-utils/src/Test/Hydra/Prelude.hs index 8984946e03a..28901d76bc0 100644 --- a/hydra-test-utils/src/Test/Hydra/Prelude.hs +++ b/hydra-test-utils/src/Test/Hydra/Prelude.hs @@ -48,7 +48,7 @@ import Test.QuickCheck.Monadic (PropertyM (MkPropertyM)) createSystemTempDirectory :: String -> IO FilePath createSystemTempDirectory template = do tmpDir <- case os of - "darwin" -> pure "/tmp" -- https://github.com/input-output-hk/hydra/issues/158. + "darwin" -> pure "/tmp" -- https://github.com/cardano-scaling/hydra/issues/158. _ -> getCanonicalTemporaryDirectory createTempDirectory tmpDir template diff --git a/hydra-tui/hydra-tui.cabal b/hydra-tui/hydra-tui.cabal index 72a7d6d9285..e2022d887e4 100644 --- a/hydra-tui/hydra-tui.cabal +++ b/hydra-tui/hydra-tui.cabal @@ -12,7 +12,7 @@ license-files: source-repository head type: git - location: https://github.com/input-output-hk/hydra + location: https://github.com/cardano-scaling/hydra common project-config default-language: GHC2021 diff --git a/plutus-cbor/plutus-cbor.cabal b/plutus-cbor/plutus-cbor.cabal index ac10dee4f4b..59d4645d7ae 100644 --- a/plutus-cbor/plutus-cbor.cabal +++ b/plutus-cbor/plutus-cbor.cabal @@ -11,7 +11,7 @@ license-files: source-repository head type: git - location: https://github.com/input-output-hk/hydra + location: https://github.com/cardano-scaling/hydra common project-config default-language: GHC2021 diff --git a/plutus-merkle-tree/plutus-merkle-tree.cabal b/plutus-merkle-tree/plutus-merkle-tree.cabal index d14b7a209de..1e21c5f42fe 100644 --- a/plutus-merkle-tree/plutus-merkle-tree.cabal +++ b/plutus-merkle-tree/plutus-merkle-tree.cabal @@ -11,7 +11,7 @@ license-files: source-repository head type: git - location: https://github.com/input-output-hk/hydra + location: https://github.com/cardano-scaling/hydra common project-config default-language: GHC2021 diff --git a/release.sh b/release.sh index 0befd965a4c..48e960b8c8c 100755 --- a/release.sh +++ b/release.sh @@ -188,7 +188,7 @@ update_demo_version() { local version="$1" ( cd demo - sed -i"" -e "s,\(ghcr.io/input-output-hk/hydra-[^:]*\):[^[:space:]]*,\1:$version," docker-compose.yaml seed-devnet.sh + sed -i"" -e "s,\(ghcr.io/cardano-scaling/hydra-[^:]*\):[^[:space:]]*,\1:$version," docker-compose.yaml seed-devnet.sh ) } @@ -196,7 +196,7 @@ update_explorer_version() { local version="$1" ( cd .github/workflows/explorer - sed -i"" -e "s,\(ghcr.io/input-output-hk/hydra-[^:]*\):[^[:space:]]*,\1:$version," docker-compose.yaml + sed -i"" -e "s,\(ghcr.io/cardano-scaling/hydra-[^:]*\):[^[:space:]]*,\1:$version," docker-compose.yaml ) } diff --git a/sample-node-config/aws/docker/docker-compose.yaml b/sample-node-config/aws/docker/docker-compose.yaml index d547ed15d22..1613a918235 100644 --- a/sample-node-config/aws/docker/docker-compose.yaml +++ b/sample-node-config/aws/docker/docker-compose.yaml @@ -83,7 +83,7 @@ services: ] hydra-tui: - image: ghcr.io/input-output-hk/hydra-tui:unstable + image: ghcr.io/cardano-scaling/hydra-tui:unstable profiles: - tui command: @@ -98,7 +98,7 @@ services: - ~/network:/network hydraw: - image: ghcr.io/input-output-hk/hydraw:latest + image: ghcr.io/cardano-scaling/hydraw:latest profiles: - hydraw environment: diff --git a/sample-node-config/aws/scripts/configure-testnet.sh b/sample-node-config/aws/scripts/configure-testnet.sh index 640a022f632..62995ea19b3 100755 --- a/sample-node-config/aws/scripts/configure-testnet.sh +++ b/sample-node-config/aws/scripts/configure-testnet.sh @@ -20,7 +20,7 @@ echo "Including hydra env variables" export NETWORK_MAGIC=$(jq .networkMagic repos/cardano-configurations/network/$NETWORK/genesis/shelley.json) echo "export NETWORK_MAGIC=$NETWORK_MAGIC" >> ~/.bash_env -# this is manually hardcoded from https://github.com/input-output-hk/hydra/releases/tag/0.10.0 +# this is manually hardcoded from https://github.com/cardano-scaling/hydra/releases/tag/0.10.0 # perhaps there would be a way to look those up in the Chain? export HYDRA_SCRIPTS_TX_ID=$(jq -r .$NETWORK.hydraScriptsTxId ~/scripts/configure.json) echo "export HYDRA_SCRIPTS_TX_ID=$HYDRA_SCRIPTS_TX_ID" >> ~/.bash_env diff --git a/sample-node-config/gcp/docker-compose.yaml b/sample-node-config/gcp/docker-compose.yaml index 3ea67e906ee..9c7767e1207 100644 --- a/sample-node-config/gcp/docker-compose.yaml +++ b/sample-node-config/gcp/docker-compose.yaml @@ -64,7 +64,7 @@ services: - ./devnet:/devnet hydraw: - image: ghcr.io/input-output-hk/hydraw:latest + image: ghcr.io/cardano-scaling/hydraw:latest profiles: - hydraw entrypoint: diff --git a/sample-node-config/gcp/scripts/configure-testnet.sh b/sample-node-config/gcp/scripts/configure-testnet.sh index 952a55b8289..6181e69de67 100644 --- a/sample-node-config/gcp/scripts/configure-testnet.sh +++ b/sample-node-config/gcp/scripts/configure-testnet.sh @@ -15,7 +15,7 @@ git clone https://github.com/input-output-hk/cardano-configurations export NETWORK_MAGIC=$(jq .networkMagic cardano-configurations/network/preview/genesis/shelley.json) -# this is manually hardcoded from https://github.com/input-output-hk/hydra/releases/tag/0.8.1 +# this is manually hardcoded from https://github.com/cardano-scaling/hydra/releases/tag/0.8.1 # perhaps there would be a way to look those up in the Chain? export HYDRA_SCRIPTS_TX_ID=bde2ca1f404200e78202ec37979174df9941e96fd35c05b3680d79465853a246 diff --git a/sample-node-config/nixos/README.md b/sample-node-config/nixos/README.md index 007991a52b6..43d81ddceac 100644 --- a/sample-node-config/nixos/README.md +++ b/sample-node-config/nixos/README.md @@ -59,7 +59,7 @@ For this, we do not need a service definition, but can simply use `docker` via S ssh -t example docker run --rm -it \ -v /data:/data \ --network host \ - ghcr.io/input-output-hk/hydra-tui \ + ghcr.io/cardano-scaling/hydra-tui \ --connect 0.0.0.0:4001 \ --node-socket /data/cardano-node/node.socket \ --testnet-magic 2 \ diff --git a/sample-node-config/nixos/hydraw.nix b/sample-node-config/nixos/hydraw.nix index 6be6612534b..043475e24f3 100644 --- a/sample-node-config/nixos/hydraw.nix +++ b/sample-node-config/nixos/hydraw.nix @@ -72,7 +72,7 @@ in # The hydraw application / bridge virtualisation.oci-containers.containers.hydraw = { - image = "ghcr.io/input-output-hk/hydraw:latest"; + image = "ghcr.io/cardano-scaling/hydraw:latest"; volumes = [ "/data/hydra-node/credentials:/credentials:ro" ]; diff --git a/spec/short.bib b/spec/short.bib index 495628aa818..e4e7a769920 100644 --- a/spec/short.bib +++ b/spec/short.bib @@ -69,7 +69,7 @@ @inproceedings{formal-model-of-bitcoin-transactions @misc{hydra-repo, title = {Hydra repository}, - note = {\url{https://github.com/input-output-hk/hydra}} + note = {\url{https://github.com/cardano-scaling/hydra}} } @article{hydrahead20, diff --git a/testnets/README.md b/testnets/README.md index e4982671daf..1da646679c5 100644 --- a/testnets/README.md +++ b/testnets/README.md @@ -23,7 +23,7 @@ curl -X POST -s "https://faucet.preview.world.dev.cardano.org/send-money/$(cat c Now we need to locate the Hydra scripts for the given testnet. For tagged & released versions we will publish them on the respective [release -page](https://github.com/input-output-hk/hydra/releases). +page](https://github.com/cardano-scaling/hydra/releases). You can also publish them yourselves by paying some some 50ADA and using this command and keep: