Midnight Node 2.1.0 RC2 Fixes Bridge Costs and Node Bootstrap

Midnight release Node 2.1.0 RC2 on September 17, remove two technical blockers wey bin dey stop the 2.1 line from move go final release.

The update no introduce new protocol behavior, but e change how dem dey verify the runtime, how dem dey measure bridge workloads and how new nodes dey connect to Preview and Devnet.

Midnight Publishes a Verifiable Runtime

Midnight Node 2.1.0 RC2 na the first candidate for the 2.1 line wey include deterministic runtime WASM file and one srtool digest wey show how dem take produce am.

The runtime WASM get the logic wey Midnight nodes dey execute. Deterministic build go allow operators and governance participants to confirm say the published artifact match the source code.

RC1 no include separate WASM artifact. Because of that, governance no get independent reproducible file wey dem fit reference when dem wan authorize upgrade through set_code action.

RC2 now provide the runtime file, cryptographic hashes and build provenance wey dem need for verification. Coordinated governance action still dey required to activate the runtime, but the necessary technical artifact don dey available.

The release get five additional commits compared with RC1. E no change the protocol specification or introduce new user-facing functionality, so e keep the scope focused on final release preparation.

Midnight Corrects Cardano Bridge Costs

New benchmark testing show say functions inside pallet_c2m_bridge and pallet_partner_chains_bridge bin get weight wey be about half of their true execution cost for reference validator hardware.

The earlier weights dem generate am for developer workstation instead of Midnight designated benchmarking machine. After dem repeat the tests for the reference hardware, the measured weights for bridge operations increase by between 1.92 and 2.51 times.

The update no make the operations more computationally expensive. E just give the runtime more accurate measure of resources wey dem don already dey consume.

One function wey the thing affect, handle_transfers, dey execute as mandatory part of a block. If mandatory call underpriced, e fit push block processing pass the intended resource limit because the operation no fit wait when the remaining capacity don finish.

The corrected components include the Cardano-to-Midnight bridge and Cardano observation infrastructure wey relate to cNIGHT. These systems dey connect Cardano-based NIGHT activity with the Midnight chain. More accurate resource pricing go align bridge capacity with the measured cost of processing NIGHT-related operations for validator hardware.

Genesis Fix Restores New Node Bootstrap

RC2 still replace the packaged chain specifications and genesis artifacts for Preview and Devnet.

Node wey dem launch from empty disk with earlier files fit calculate incorrect genesis hash. Existing bootnodes go see am as another chain and reject the connection, leave the affected node for block zero without peers.

The defect no affect nodes wey don already connect and synchronize because their valid genesis data dey store locally. Operators wey get affected new installations must remove the existing base path and bootstrap again using the files wey come with RC2.

Nodes wey don already synchronize no need reset, resynchronization or reindexing. No supported direct upgrade path dey from RC1 or the earlier beta because those versions be development candidates, no be deployment baselines. The supported path still be coordinated hard fork from the 1.0.300 runtime.

Midnight 2.0 no reach final release, so 2.1.0 be the planned first complete version of the new major line after Node 1.0.1. RC2 no be final mainnet release, but governance now get verifiable runtime artifact, bridge calls dey use measured execution costs and new Preview and Devnet nodes fit bootstrap with the genesis data wey the active networks dey use.