• 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 processor
• 24GB of RAM when running with the InMemory backend, 8GB when running with the OnDisk backend (pending confirmation)
• 300GB of free storage (350GB recommended for future growth)

• Linux 64-bit (Ubuntu 20.04 LTS, 22.04 LTS, 24.04 LTS, 26.04 LTS; Mint 20, 21, 21.1, 21.2, 21.3, 22, 22.1, 22.2; Debian 11, 12, 13)
• Windows 64-bit (10, 11)
• MacOS 10.15, 11 (Big Sur), 12 (Monterey), 13 (Ventura), 14 (Sonoma), 15 (Sequoia), 26 (Tahoe)

• GHC 9.6
• Cabal 3.8/3.12

• Pre-release configuration files
• Docker Images: cardano-node, cardano-tracer, cardano-submit-api

• 🟢 - signed / agreed / supported
• 🟥 - not agreed / unsupported

• The protocol version the node advertises in block headers is bumped from 11.1 to 11.3. (#6767)
• Network configurations: the maximum randomised ledger snapshot delay (Storage.LedgerDB.Snapshots.MaxDelay) is capped at one hour (3600s). On mainnet and preprod it was 6 hours (21600s); on preview and sanchonet it was 4320s. MinDelay and Interval are unchanged. (#6767, iohk-nix#624)
• Updated to ouroboros-consensus 5.4, cardano-api 11.12 and cardano-cli 11.7. See the Consensus section for the memory improvements. (#6767)

No changes.

• Updated to cardano-api 11.12 and cardano-cli 11.7. (#6767)

• New status command that reports the state of a testnet created with cardano-testnet, in human-readable form or as JSON with --json. The JSON output has a schema, checked in CI. (#6741)
• Starting a testnet can no longer hang forever while waiting for a node to start. (#6750)
• The --output-dir help now gives the real default (./testnet) and says the directory must not already contain a testnet. (#6752)
• Updated to cardano-api 11.12 and cardano-cli 11.7. (#6767)

Updated to cardano-cli 11.7.0.0:

• New dijkstra stake-pool bls-registration-certificate offline: takes an existing pool registration certificate and writes a new one with only the BLS key and its proof of possession replaced. Use it to register a pool's BLS key for the first time or rotate it, without re-entering pool parameters. Accepts certificates from the Conway era and from earlier cardano-cli versions.
• New debug certificate view prints a certificate file as JSON or YAML. debug certificate view and debug transaction view read standard input when the file path is -.
• debug transaction view uses new keys for certificates (breaking for scripts that read them): pool registrations show pool id, vrf key hash, reward account (bech32) and margin (a fraction); DRep keys are spelled DRep, with credential key DRep credential; committee certificates show every credential and anchor.
• transaction view prints sub-transaction data.
• governance action create-protocol-parameters-update has options for the new Dijkstra parameters: minimum pool margin, maximum pledge leverage, the Peras parameters, and reference-input costs. --no-max-pledge-leverage and --no-peras-bootstrap-round propose unsetting them.
• Dijkstra sub-transactions: new witness and assemble commands create key witnesses separately and combine them with an unsigned sub-transaction, rejecting witnesses whose signatures do not match.
• Dijkstra transaction build, build-raw and build-estimate:
  • support native and Plutus V4 script guards (inline or reference);
  • support CIP-159 account balance intervals (--account-balance-interval, --starting-account-balance-interval).

Updated to cardano-api 11.12.0.0:

• Fixed calcMinFeeRecursive failing with FeeCalculationDidNotConverge when the change output sits near a CBOR integer width boundary (such as 2^32 lovelace). The fee it returns can be up to 4 * txFeePerByte above the minimum (176 lovelace on mainnet).
• Fixed reading JSON simple scripts, including guards, in the Dijkstra era, which used to crash.
• IntroducedInDijkstraPParams covers minimum pool margin, maximum pledge leverage, the Peras parameters and reference-input costs.
• Requires ouroboros-consensus 5.4, cardano-ledger-core 1.23 and cardano-ledger-alonzo 1.18.

No changes.

No changes.

Updated from ouroboros-consensus 5.2.0.0 to 5.4.0.0:

• The ChainDB no longer keeps its startup arguments reachable for its whole lifetime. Until now, the Peras voting view (never used while Peras is disabled) kept the genesis ledger state and its tables alive, costing several hundred MiB of live data on networks with a large genesis UTxO or delegation set.
• Writing a ledger snapshot no longer temporarily grows live memory by about the snapshot's size. The snapshot request queue used to keep the request, and with it the serialised snapshot, reachable until the write finished.
• Until the node has first caught up, ledger snapshots are written as soon as they are requested. The randomised snapshot delay (MinDelay/MaxDelay) applies only once the node has been caught up, even if it later falls behind again. While syncing, a delayed snapshot kept an outdated ledger state alive for the whole delay.
• TraceForgingMempoolSnapshot is emitted after the forging thread has computed the mempool snapshot, not before, so its duration is no longer counted as block forging time.

Updated to cardano-ledger-core 1.23, cardano-ledger-alonzo 1.18 and cardano-ledger-dijkstra 0.5. These contain library API changes only (Plutus cost model handling in PlutusWithContext, new Inject AlonzoContextError constraints), with no change in ledger rules or behaviour. The other ledger packages were rebuilt with updated bounds only.

No changes.

Updated to trace-dispatcher 2.13.3:

• An IO error while writing traces to stdout, such as an encoding failure or a closed pipe, no longer crashes the node. The error is reported on stderr, and stdout tracing resumes once the condition clears. (hermod-tracing#22)
• Lower per-message tracing overhead: configured tracers build their per-namespace tracers once per configuration instead of once per message, and namespace lookups no longer allocate.

Package changelogs