0.8.0
Pre-release-
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 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 thenode-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.
- Instead of
-
BREAKING Keep track of
contestationDeadline
instead ofremainingContestationPeriod
and fixReadyToFanout
. #483- Clients can now rely on
ReadyToFanout
, such that sending aFanout
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 thecontestationDeadline
andReadyToFanout
. - 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
TxId
instead of full transactions in the nominal cases. - Renamed log entry prefixes
Processing -> Begin
andProcessed -> End
. - Added
PostingFailed
log entry.
- Strip chain layer logs to only contain
-
BREAKING The
hydra-cluster
executable (our smoke test) does require--publish-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- New
--persistence-dir
command line argument to configure location. - Writes two JSON files
headstate
andchainstate
to the persistence directory. - While introspectable, modification of these files is not recommended.
- New
-
Fixed bugs in
hydra-node
:- Crash after
3k
blocks 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-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 -
Compute transaction costs as a "min fee" and report it in the tx-cost benchmark.
-
Update hydra-node-options section in docs.
-
Improved
hydra-tui
user 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 noPlutusV2
cost model was on the testnet at that time)