0.8.0
Pre-release-
BREAKING Hydra keys now use the text envelope format.
hydra-toolsexecutable now produces keys in the same format as cardano keys so this should make key handling simpler.- Take a look at the example on how to use
hydra-toolsto generate necessary hydra keys.
-
BREAKING hydra-node command line flag
--node-idis now mandatory.- Instead of
Hostwe are using thenode-idin the server messages like +PeerConnected/Disconnectedwhich are also used in - the TUI to distinguish between different connected peers.
- This also changes the way how
NodeIds are represented on the API.
- Instead of
-
BREAKING Keep track of
contestationDeadlineinstead ofremainingContestationPeriodand fixReadyToFanout. #483- Clients can now rely on
ReadyToFanout, such that sending aFanoutinput after seeing this output will never be "too early". - The
HeadIsClosedserver output now contains the deadline instead of the remaining time. - See
hydra-tuifor an example how to use thecontestationDeadlineandReadyToFanout. - See ADR20 for details and the rationale.
- Clients can now rely on
-
BREAKING Several changes to the API:
-
BREAKING Changed logs to improve legibility and trace on-chain posting errors. #472
- Strip chain layer logs to only contain
TxIdinstead of full transactions in the nominal cases. - Renamed log entry prefixes
Processing -> BeginandProcessed -> End. - Added
PostingFailedlog entry.
- Strip chain layer logs to only contain
-
BREAKING The
hydra-clusterexecutable (our smoke test) does require--publish-scriptsor--hydra-scripts-tx-idnow as it may be provided with pre-published hydra scripts. -
The
hydra-nodedoes persist L1 and L2 states on disk now: #187- New
--persistence-dircommand line argument to configure location. - Writes two JSON files
headstateandchainstateto the persistence directory. - While introspectable, modification of these files is not recommended.
- New
-
Fixed bugs in
hydra-node:- Crash after
3kblocks because of a failed time conversion. #523 - Internal wallet was losing memory of spent fuel UTxOs in presence of transaction failures. #525
- Node does not see some UTxOs sent to the internal wallet on startup. #526
- Prevent transactions from being resubmitted for application over and over. #485
- Crash after
-
Prevent misconfiguration of
hydra-nodeby 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-toolsexecutable, to help with generating Hydra keys and get hold of the marker datum hash. #474 -
Compute transaction costs as a "min fee" and report it in the tx-cost benchmark.
-
Update hydra-node-options section in docs.
-
Improved
hydra-tuiuser experience: -
Build & publish static Linux x86_64 executables on each release 👇 #546
Built artifacts
Hydra Scripts
Transaction IDs to be used as --hydra-scripts-tx-id when running hydra-node on the following networks:
-
preview:4081fab39728fa3c05c0edc4dc7c0e8c45129ca6b2b70bf8600c1203a79d2c6d
published & checked during smoke test run #32 (failing because noPlutusV2cost model was on the testnet at that time)