Midnight Fixes Validator-Rotation Risk in BABE Migration Code

Midnight developers merged a new safeguard into the midnight-node repository on October 26, refining how the blockchain will transition from Aura to BABE consensus.

Submitted by developer Klapeyron through pull request #2326, the change addresses a scenario in which the network could switch consensus mechanisms at the same moment its validator committee rotates.

The fix introduces an automatic delay when these events overlap, preventing the first BABE epoch from starting with an inconsistent validator configuration.

Midnight Addresses a Critical Timing Risk in Consensus Migration

Midnight currently uses Aura, where authorized validators produce blocks according to a predetermined schedule. BABE introduces a different selection mechanism based on cryptographic randomness, making future block production less predictable.

Switching between these systems requires precise coordination between the consensus engine and the network’s validator committee.

A potential conflict arises when the scheduled transition occurs in the same block as a committee rotation.

Under that scenario, BABE could initialize its first epoch using one set of validators while the runtime simultaneously recognizes another committee as active.

The resulting mismatch could leave the authorities responsible for producing blocks inconsistent with those recorded by the network.

The October 26 correction addresses this specific timing risk before the new consensus mechanism is deployed.

New Runtime Safeguard Automatically Delays the Transition

The update introduces an additional check within Midnight’s consensus engine using ShouldEndSession, the mechanism that determines whether the current validator session should conclude.

If a committee rotation is due in the same block as the planned consensus switch, the transition is postponed until a later epoch.

The process remains scheduled, but BABE does not initialize against a committee that is being replaced.

Developers added unit and integration tests covering both outcomes: delaying the switch when a rotation is required and completing it when no conflict exists.

The latest correction follows related changes introduced on October 15 and 16, which refined the initialization of BABE’s first epoch and the verification of competing blockchain branches during migration.

Together, these updates address specific edge cases in the transition procedure without changing runtime storage structures or existing runtime APIs.

The changes remain part of development work rather than evidence of a completed network migration.

[NEWSBREAK]

Cardano Stake Pool Operators Await the Mainnet Transition

Midnight’s official roadmap schedules a staged transition to BABE during the fourth quarter of 2026, followed by the beginning of mainnet migration in the first quarter of 2027.

That period also includes plans to open block production to Cardano stake pool operators and introduce NIGHT staking and delegation.

Before the consensus transition can proceed, validators must generate new BABE keys, update the authorized candidate list, and ensure network nodes run compatible software.

A governance-controlled scheduleFlip operation will then schedule the consensus change at an epoch boundary.

The newly merged safeguard adds a precise condition to that process: if validator rotation conflicts with the scheduled switch, the network defers the transition rather than initializing BABE with an inconsistent authority set.

The next operational milestones are coordinated node upgrades, validator key registration, and authorization of the consensus switch. No public mainnet activation date has been announced.