Release 0.7.0 · cardano-scaling/hydra

BREAKING Switch to BabbageEra and PlutusV2.
- hydra-cardano-api now uses Era = BabbageEra and constructs PlutusV2 scripts.
- hydra-plutus scripts now use the serialiseData builtin to CBOR encode data on-chain.
- hydra-node now expects BabbageEra blocks and produces BabbageEra transactions.
- hydra-cluster now spins up a stake pool instead of a BFT node (not possible in Praos anymore).
- As a consequence, the Hydra scripts in hydra-plutus have now different script hashes.
BREAKING Use reference inputs and reference scripts in abort transaction.
- 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 #423.
Use deadline when posting a fanoutTx instead of the current slot #441.
The user manual is now also available in Japanese thanks to @btbf! 🇯🇵
Fixed display of remaining contestation period in hydra-tui #437.

Transaction IDs to be used as --hydra-scripts-tx-id when running hydra-node on the following networks:

vasil-dev: 5d0aff357c3dc586fc6903bb5c7ef0b4d07eef2475c58fa200e85d65a752f532
✔️ published & checked during smoke test run #19
preview: bde2ca1f404200e78202ec37979174df9941e96fd35c05b3680d79465853a246
✔️ published & checked during smoke test run #20

Provide feedback