• An Intel or AMD x86 processor with two or more cores, at 1.6GHz or faster (2GHz or faster for a stake pool or relay)
• Or, for MacOS, an Apple Silicon (M1, M2 or M3) processor
• 24GB of RAM
• 150GB of free storage (250GB recommended for future growth)

• Linux 64-bit (Ubuntu 18.04 LTS, 20.04 LTS; Mint 19.3, 20; Debian 10.3)
• Windows 64-bit (8.1, 10, 11)
• MacOS 10.13, 10.14, 10.15, 11

• GHC 8.10.7/Cabal 3.8.1.0

• Docker image
• Configuration files

NONE

• Changing the selection now traces the entire SelectView (including the tiebreaker VRF)

NONE

• Introduces light peer sharing: incoming duplex connections become known to
  the outbound governor.
• Fixed issues with random peer selection for sharing.
• Addressed asynchronous demotion issues, preventing peers from remaining
  indefinitely in certain states (the bug).
• Fixed a bug where peers marked with DoNotAdvertisePeer were being shared.
• Clarified distinction between pools of peers for sharing and requesting.
• Updated types for PeerSharing, including removal of PeerSharingPrivate
  for symmetric handshakes, improving compatibility and fixing specific
  issues.
• Changed encoding for IPv6 addresses in the PeerSharing protocol.
• Introduced NodeToNodeVersion_13 - this version fixes the negotiated value
  of PeerSharing and deprecates PeerSharingPrivate. Older versions would
  wrongly echo the proposer's PeerSharing value so version 13 disables peer
  sharing with older versions to not lead into unwanted disconnections.
• Made ChainSync idle timeout configurable.
• Updated KeepAlive client for better round-trip time sampling.
• Introduced less aggressive churn for established and known peers.
• Added new PeerStatus PeerCooling to manage asynchronous demotions more accurately.
• Introduced big ledger peers to the outbound governor.
• Fixed a small memory leak in PeerMetrics.
• Made DNS resolution for peers more efficient and limited concurrency for
  faster and more stable connections.
• Improved memory footprint for peer metrics.

Introduction of Top-Level Command:

• cardano-cli 8.17.0.0 now features as a top-level command, exemplified by commands like cardano-cli conway, cardano-cli babbage, and cardano-cli alonzo.

This refactoring is crucial for the seamless integration of the Conway era, which introduces significant changes compared to Babbage and previous eras. This enhancement aims to improve user experience by tailoring the CLI to display only the commands and flags relevant to the current era. For example, Conway-specific commands are not displayed in Babbage, and Babbage options that would be nonsensical in Conway are appropriately excluded (i.e MIR certificates and update proposals by genesis keys)

Please be aware that commands are actively under development, and changes or refinements may still occur in upcoming releases.

Preservation of Legacy Commands:

• cardano-cli 8.17.0.0 retains all commands from cardano-cli 8.1.2 (the previous release suitable for mainnet). These commands are designated as "legacy commands," ensuring users transitioning from cardano-cli 8.1.2 can seamlessly continue their operations without disruption while they smoothly transition into the new commands structure.

Known Issues:

There are a few minor bugs related to Conway era integration where Conway subcommands are spilling over to previous eras and the legacy commands. For updates on these issues, please refer to cardano-cli repository.

• The legacy command "cardano-cli transaction build" currently displays options --vote-file and --proposal-file.
• The legacy command cardano-cli query presents the subcommand constitution-hash which is irrelevant for babbage era
• cardano-cli babbage stake-address registration-certificate and cardano-cli stake-address registration-certificate show the flag --key-reg-deposit-amt but it is really not needed on Babbage. This will be removed, however the its presence and the removal is purely cosmetic since the resulting certificate does conform to the Babbage cddl. In other words, using this flag does not have any impact. The deposit in Babbage era should be supplied on the current fashion: when balancing the transaction.
• The output of cardano-cli babbage query stake-address-info shows the voteDelegation field which does not have any meaning in Babbage and is Conway specific to display the DRep that we are delegating to.

• Major refactoring of API (see detailed changelogs for API below)
• Fix the inclusion of datum hashes in Alonzo era tx bodies
• New ToJSON instance for TxValidationErrorInCardanoMode
• Remove ByronTx data constructor from data Tx era
• Delete Cardano.Api.Eon.ByronEraOnly module
• Remove TxFeeImplicit and TxValidityNoUpperBound

• Remove support for Byron transactions
• Update cardano-cli-8.17.0.0 and cardano-api-8.36.1.1

NONE