- The cardano-node repository integrates the ledger, consensus, networking, and node shell repositories, and provides logging as a feature to the other packages.
- The cardano-cli is a CLI utility used for running a node and supports various subcommands, including era-based commands, Byron-specific commands, and miscellaneous commands.
The Cardano-node repository is a top-level node that integrates the ledger, consensus, networking, and node shell repositories. It provides logging as a feature to the other packages. The node no longer incorporates wallet or explorer functionality. The wallet backend and explorer backend are separate components that run in separate external processes that communicate with the node via local IPC.
JUST IN: #Cardano Node 1.35.7 has been released and comes with the new Dynamic P2P functionality for Mainnet.
The new P2P mode is under continuous testing so SPOs are encouraged to run it on a single relay, and use (old) the non-P2P mode on other relays.https://t.co/3vHwSDQeNP
— Emmanuel 𓂀 🍕 𓅓🇬🇭🦄🟣⚡️ (@thepizzaknight_) April 4, 2023
To obtain the cardano-node, you can either build it from source or download the hydra binaries from the release notes. The latest supported networks can be found at the Cardano website. To run the node on Windows, you need to reference a few files and directories as arguments. The docker image with the latest version of cardano-node can be pulled from the Cardano website.
The cardano-cli is a CLI utility used for running a node. The general synopsis includes various options such as –topology, –database-path, –byron-delegation-certificate, –shelley-operational-certificate, –port, and –config. The –config flag points to a .yaml file responsible for configuring the logging and other important settings for the node.
Cardano-cli also supports various subcommands, including era-based commands, Byron-specific commands, and miscellaneous commands. The subcommands are subdivided into groups, and all subcommands have help available. For example, the byron key migrate-delegate-key-from subcommand migrates a delegate key from an older version.
The Byron genesis generation operations will create a directory that contains genesis.json, avvm-seed..seed, delegate-keys..key, delegation-cert..json, genesis-keys..key, and poor-keys.*.key. Key operations include signing key generation and verification key extraction, delegate key migration, and signing key queries.
Note that key operations do not support password-protected keys. Signing keys can be generated using the keygen subcommand, and extracting a verification key out of the signing key is performed by the to-verification subcommand. One can gather information about a signing key’s properties through the signing-key-public and signing-key-address subcommands.