Technologie & IA
Midnight moves to Ledger 9: applications need updated tools
Midnight’s mainnet changed versions on November 6. The upgrade expands contract capabilities and requires applications to migrate, while some NIGHT-related and privacy features remain outside this release.

Contracts remain, applications need updates
Midnight activated Ledger 9 on its mainnet on November 6, 2026, according to its announcement and technical documentation. The project says existing balances and deployed contracts migrate automatically. That continuity does not mean every application can keep its old tools: after the change, mainnet accepts only transactions in Ledger 9 format. The interfaces that build them therefore need to be updated.
The official compatibility matrix pairs mainnet with Midnight.js 5.0.0 and Wallet SDK 2.0.0, among other components. Developers must also align their compilation, proof, and indexing tools with the corresponding versions. This is more than a change in how a wallet displays information: an older application may still know a contract’s address while no longer being able to produce a compatible transaction. Preserving assets and maintaining software compatibility are distinct aspects of the migration.
Contract interactions with a defined scope
Ledger 9 allows one contract to call another within a single transaction. This capability makes it easier to combine several functions without asking the user to perform as many separate operations. However, the documentation specifies that this first phase concerns unshielded data. Events emitted by contracts, which applications can follow through the indexer, are also limited to public events at this stage. It would therefore overstate the release to describe it as broadly enabling fully confidential interactions.
The upgrade also introduces cryptographic primitives used in other ecosystems, including ECDSA signature verification and Keccak hashing. These building blocks may simplify some integrations with existing tools. Their presence does not mean that every bridge between networks is available: Midnight says activating the cNIGHT-to-mNIGHT protocol token bridge on mainnet still requires a separate governance action. Block production rewards are also outside Ledger 9’s scope.
Preserving older contracts during the transition
The Midnight.js 5 release notes distinguish existing contracts from new deployments. An older contract can retain its original compiled artifacts while being called through the new tools. Recompiling it without preparing its update changes its verifier keys, even when the source code remains identical. The new artifacts then no longer match the deployed contract. The documentation therefore calls for keeping the existing artifacts or following the designated maintenance process to upgrade the contract.
Finally, the test environments are not all at the same stage. Preview now runs Ledger 9, while Preprod remains on Ledger 8 in the matrix reviewed. Testing an application on Preprod is therefore insufficient to validate compatibility with the new mainnet version. For teams, the operational priority is to choose the right environment, align dependencies, and check actual contract calls. Protocol activation marks a milestone; fully adapting applications remains work to be done.
