Midnight Fixes Validator-Rotation Risk in BABE Migration Code

Midnight developers don merge one new safeguard enter the midnight-node repository on October 26, wey refine how the blockchain go take move from Aura go BABE consensus.

Developer Klapeyron submit am through pull request #2326. The change tackle one scenario wey fit make the network switch consensus mechanism the same time wey e validator committee dey rotate.

The fix add automatic delay when these two events overlap, to stop the first BABE epoch from starting with validator configuration wey no dey consistent.

Midnight Addresses a Critical Timing Risk in Consensus Migration

Midnight dey use Aura currently, where authorized validators dey produce blocks according to schedule wey dem don set. BABE bring different selection mechanism based on cryptographic randomness, wey make future block production less predictable.

To switch between the two systems need correct coordination between the consensus engine and the network validator committee.

Conflict fit show when the scheduled transition happen inside the same block with committee rotation.

For that kind scenario, BABE fit initialize im first epoch with one set of validators while the runtime at the same time recognize another committee as active.

This mismatch fit make the authorities wey suppose produce blocks no align with wetin the network record.

The October 26 correction address this particular timing risk before dem deploy the new consensus mechanism.

New Runtime Safeguard Automatically Delays the Transition

The update add extra check inside Midnight consensus engine using ShouldEndSession, the mechanism wey dey decide whether the current validator session suppose end.

If committee rotation suppose happen for the same block with the planned consensus switch, the transition go postpone till later epoch.

The process still dey scheduled, but BABE no go initialize on top committee wey people dey replace.

Developers add unit and integration tests wey cover both outcomes: to delay the switch when rotation dey required and to complete am when no conflict dey.

The latest correction follow related changes wey dem introduce on October 15 and 16, wey refine how BABE first epoch go initialize and how dem go verify competing blockchain branches during migration.

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

The changes still be part of development work, e no be proof say network migration don complete.

[NEWSBREAK]

Cardano Stake Pool Operators Await the Mainnet Transition

Midnight official roadmap schedule staged transition to BABE during the fourth quarter of 2026, followed by beginning of mainnet migration for the first quarter of 2027.

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

Before the consensus transition fit proceed, validators must generate new BABE keys, update the authorized candidate list, and make sure network nodes dey run compatible software.

One governance-controlled scheduleFlip operation go then schedule the consensus change for epoch boundary.

The new safeguard wey dem merge add one precise condition to that process: if validator rotation conflict with the scheduled switch, the network go defer the transition instead of initializing BABE with authority set wey no dey consistent.

The next operational milestones na coordinated node upgrades, validator key registration, and authorization of the consensus switch. Dem never announce public mainnet activation date.