This version of the node fixes an issue with the peer sharing networking feature which prevents a node from sharing peers with others that it is connected to.

NOTE: As with 8.9.0, please refrain from updating all relays simultaneously; instead, we recommend spreading out the rollout over the upcoming weeks to minimize disruptions.

Known Issues​

Haskell Security Advisory Haskell Security Advisory is a repository of security advisories filed against packages published via Hackage. cabal-audit output:

Found advisories:

dependency "base" at version 4.14.3.0 is vulnerable for:
  HSEC-2023-0007 "readFloat: memory exhaustion with large exponent"
  published: 2024-04-08 23:04:08 +1000
  https://haskell.github.io/security-advisories/advisory/HSEC-2023-0007
  No fix version available
  toml, parser, dos

Technical Specification​

Minimum System Requirements​

• 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
• 200GB of free storage (250GB recommended for future growth)

Platforms​

• 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/Cabal supported versions​

• GHC 8.10.7/Cabal 3.8.1.0

~~

NOTE:​

Please refrain from updating all relays simultaneously; instead, we recommend spreading out the rollout over the upcoming weeks to minimize disruptions.

Cardano Node 8.9.0 is a release that introduces genesis lite a.k.a bootstrap peers. Please refer to here to read more about it. This version fixes a small bug on the dynamic block forging logic and also includes some overall improvements.

Benchmarking reports relevant to the 8.9.0 release can be found in this post on Cardano Updates.

Known Issues​

Technical Specification​

Minimum System Requirements​

• 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
• 200GB of free storage (250GB recommended for future growth)

Platforms​

• 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/Cabal supported versions​

• GHC 8.10.7/Cabal 3.8.1.0

~~

This Cardano node release is mainnet ready and updates the Plutus interpreter. All SPOs are encouraged to update, especially ones that are currently running Cardano node version 8.1.1.

Node 8.1.2 is a minor release of the Cardano node, which updates the Plutus interpreter.

Known Issues​

Please see list of 8.1.0 issues

Technical Specification​

Minimum System Requirements

• 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)
• 24GB of RAM
• 150GB of free storage (250GB recommended for future growth)

Platforms

• 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/Cabal supported versions

• GHC 8.10.7/Cabal 3.8.1.0

~~

Node 8.0.0 is a major release of the Cardano node that adds initial, experimental, support for the Conway ledger era (Protocol Version 9.0). It includes some additional CLI commands, bug fixes, and network configuration options. SPOs are recommended to deploy this version on all their nodes. This version of the Cardano node:

Introduces the Conway era (Voltaire) as a developmental hard fork. Note: the node does not have any Voltaire features yet, this just prepares the way by creating the transaction formats and providing the ability to hard fork into the era. Adds a governance action for SPO polls (cardano-cli governance poll) that the Cardano Foundation will use to conduct an SPO survey Introduces a fairness improvement into the mempool logic Adds query commands to inspect metrics and data in mempool Allows the network to be defined via CARDANO_NODE_NETWORK_ID instead of needing to be passed in every CLI query Adds more detailed output in the query tip CLI command Allows modification via configuration file of connection limits Provides versioned serialization formats for ledger Provides a ledger API Changes the tracking of deposits It also includes some bug fixes and performance improvements.

IMPORTANT: On mainnet, P2P networking is only intended to be ran on a single relay at this time. Please continue to run any other relays with P2P disabled using the legacy topology.

Please note that this version contains breaking changes

Needs newer libsodium-vrf revision dbb48cce5429cb6585c9034f002568964f1ce567

KES key and operational certificate renewal completed. Operators generate KES files on a regular basis and issue operational certificates with new KES files approximately every 90 days to operate the pool. Blocks cannot be generated after expiration.

KES key and operational certificate renewal completed. Operators generate KES files on a regular basis and issue operational certificates with new KES files approximately every 90 days to operate the pool. Blocks cannot be generated after expiration.

KES key and operational certificate renewal completed. Operators generate KES files on a regular basis and issue operational certificates with new KES files approximately every 90 days to operate the pool. Blocks cannot be generated after expiration.

KES key and operational certificate renewal completed. Operators generate KES files on a regular basis and issue operational certificates with new KES files approximately every 90 days to operate the pool. Blocks cannot be generated after expiration.

KES key and operational certificate renewal completed. Operators generate KES files on a regular basis and issue operational certificates with new KES files approximately every 90 days to operate the pool. Blocks cannot be generated after expiration.

KES key and operational certificate renewal completed. Operators generate KES files on a regular basis and issue operational certificates with new KES files approximately every 90 days to operate the pool. Blocks cannot be generated after expiration.

KES key and operational certificate renewal completed. Operators generate KES files on a regular basis and issue operational certificates with new KES files approximately every 90 days to operate the pool. Blocks cannot be generated after expiration.