Cardano Mainnet Configuration Defaults to Ouroboros Genesis

The official mainnet configuration now contains ConsensusMode: GenesisMode. This moves Genesis from an optional synchronization mode to the default setting for nodes deployed with the latest configuration package.

The update is not a hard fork or a ledger upgrade. It changes how nodes synchronize with the network, particularly when joining for the first time or reconnecting after an extended period offline.

GenesisMode Becomes the Mainnet Default

The Cardano Operations Book confirms that Ouroboros Genesis is now the default consensus mode in the distributed mainnet node configuration.

The current package is listed as compatible with cardano-node 11.1.2, while the configuration requires at least version 11.1.0. Operators using these files will run GenesisMode unless they manually select PraosMode.

Existing stake pools and relay nodes are not automatically switched. A node continues to follow the consensus mode defined in its local configuration until the operator updates or replaces that file.

Operators can also return to the previous synchronization process by selecting PraosMode and using the corresponding bootstrap peer configuration.

Genesis Reduces Reliance on Trusted Entry Points

Under PraosMode, a new node begins synchronization through a predefined set of bootstrap peers. Those peers provide the initial path into the network and help the node reach the current chain.

Ouroboros Genesis introduces a chain selection process built around Cardano’s honest majority of stake assumption. Instead of depending on a fixed list of trusted entry points to identify the correct chain, a node evaluates the available chain history using protocol rules and information connected to the distribution of ADA stake.

The mainnet package also includes a peer snapshot containing large ledger peers selected from network stake data. These peers help the node establish initial connections, while Genesis determines how competing chains are evaluated during synchronization.

For a new node, or one returning after a long absence, the practical result is a more resilient recovery process. The node can identify the valid chain without assuming that the first peers it contacts are necessarily following the correct branch.

Genesis does not remove every operational dependency. Nodes still require valid configuration files, sufficient network access, and the security assumption that an honest majority controls the active ADA stake.

Operators Must Review Version and Topology

Operators adopting Genesis must first verify that they are running a supported cardano-node version. The current configuration requires version 11.1.0 or later, while the distributed mainnet package is identified as compatible with version 11.1.2.

The local ConsensusMode value must then be checked. A node configured with GenesisMode will use the new synchronization process. A node that still contains PraosMode will continue using bootstrap peers regardless of the setting in the latest public configuration.

The associated topology also requires a valid peer snapshot reference. Changing the consensus mode without reviewing the topology can leave the node without the peer discovery path expected by Genesis.

Cardano’s documentation is not yet fully aligned. The Operations Book identifies Genesis as the mainnet default, while some developer guidance still describes Praos as the current default and Genesis as a future replacement. For deployments using the latest mainnet package, the distributed configuration file provides the operative setting.

There is no single activation epoch for the transition. Ouroboros Genesis becomes the operational default node by node as new deployments adopt the current package and existing operators update their local configuration.