Midnight Node 2.1.0 Beta Add Road wey go Hard Fork for Live Chain

Midnight don release Node 2.1.0-beta.1, major pre-release wey dey prepare the running network to upgrade go ledger 9. E join the feature set wey dem build during the unreleased 2.0.0 line with extra two months of maintenance and security patches, plus migration logic wey dem design to preserve DUST generation wey link to $NIGHT.

The beta dey available for Midnight public network environments. To publish am no mean say the new runtime don already active across Mainnet.

Midnight Node Add Upgrade Road for the Running Network

Midnight Node na the core software wey validators and RPC operators dey use to follow the network, process transactions and run the runtime behind Midnight applications.

Midnight na privacy-focused partner chain wey connect to Cardano. Developers fit use am build applications wey combine public blockchain state with private data and selective disclosure. The economic model separate $NIGHT, the public network asset, from DUST, the non-transferable resource wey users dey consume when dem execute transactions and smart contracts.

Version 2.1.0-beta.1 land on August 21 as feature-complete beta. Dem classify the release as major update compared with the latest final Node 1.0.1 version.

The main infrastructure change na the ability to hard fork from running 1.0.x chain. Earlier 2.0.0 builds bin dey design around fresh genesis environment, wey limit their use for already active network. Node 2.1.0 add the migration logic wey required to move the existing chain enter the new runtime without to discard im current state.

Ledger 9 Migration Preserve DUST Generation

To activate Node 2.1.0 go move Midnight from ledger 8 go ledger 9 through on-chain, multi-block migration. The runtime specification go change from 1_000_003 go 2_001_000, while the transaction version go move from 3 go 4.

The transition still affect the state wey dem dey use to generate DUST from NIGHT wey dem observe for Cardano. The ledger migration go initialize the new DUST structure without the existing generation records, so the node need to reconstruct dem from pre-fork data.

Node 2.1.0 go perform that reconstruction in batches after the runtime upgrade. Cardano observation go pause small during the process, wey dem estimate say e fit cover approximately 28 blocks for Mainnet scale, nine for Preview and one for Preprod.

After reconstruction, observation go resume without to skip the Cardano UTxOs wey arrive during the migration. The process go preserve the link between Cardano-based NIGHT positions and the DUST resource wey dem generate for Midnight activity.

Infrastructure wey connect to the node must still account for the transaction version change. Clients, software development kits and indexers need to refresh their runtime metadata after the upgrade block, while transactions wey dem don sign or queue before the transition must be rebuild.

Mainnet Activation Still Need Governance

Node 1.0.3 na the documented starting point for the hard fork, but that baseline release still bin dey pending when dem publish the 2.1.0 beta notes. To move direct from Node 1.0.2 or earlier version no dey part of the supported migration road.

Validators must first install the new binary and confirm say the network still dey import and finalize blocks under the existing runtime. Authorized technical signers fit then apply the governance set_code action wey go replace the active runtime.

The Cardano-to-Midnight bridge get additional governance dependency. Im Cardano observation provider go remain inactive until dem set the required MainChainScripts configuration and data checkpoint.

Node 2.1.0 provide the software and migration road for Midnight next runtime. Ledger 9 go become operational only after the 1.0.3 baseline dey available, upgraded validators dey run across the network and governance apply the new runtime on-chain.