Midnight has completed a hard fork that moves its mainnet from Ledger 8 to Ledger 9. The upgrade, published on the project’s blog on November 6, 2026, adds standard cryptographic signature support, contract-to-contract execution, and a set of performance and security improvements. According to the team, the goal is to give developers the infrastructure needed for cross-system connections, application composability, and more advanced privacy features.

A smooth transition for existing users

Balances and already-deployed smart contracts migrate automatically during the upgrade, and existing contracts carry over unchanged. However, builders must update their applications to Midnight.js 5, while contracts that have not yet been deployed need to be compiled with the updated Compact toolchain targeting Ledger 9. For mainnet holders of cNIGHT, DUST generation registration happens automatically with no action required.

The engineering team has chosen to accelerate feature deployments so developers can access new capabilities sooner. As a result, technical documentation for some of the newest features is still being finalized and will appear in the Midnight docs over the coming weeks.

Stablecoin privacy meets standard cryptography

Moving stablecoins between blockchain networks typically exposes a user’s financial history to the public. Midnight aims to let users bring stablecoins onto its network while keeping transaction data private, and doing so safely requires the same cryptographic standards used across the broader blockchain ecosystem. The Compact programming language now includes these native formulas, which means developers can build tools that let users move money from other chains onto Midnight privately.

The update adds native support for Keccak-256 and ECDSA. Keccak-256 is the hashing algorithm Ethereum uses to turn data into fixed-length cryptographic fingerprints, while ECDSA is the digital signature method used by networks such as Bitcoin and Ethereum to prove wallet ownership. Because Midnight processes these functions natively, assets from other chains can be deposited directly, with the network verifying transactions mathematically rather than relying on a centralized middleman.

At the ledger layer, both Schnorr and ECDSA signatures are now accepted to authorize transactions. Accepting ECDSA directly allows the largest institutional custody providers to connect to the network. The release also implements the BIP-44 address derivation standard, which works like a master key system in which a single seed phrase generates and manages thousands of secure addresses. Since custodians and wallet providers already use this standard industry-wide, enterprise partners can create Midnight wallets with their existing software, letting financial institutions mint, burn, and transfer assets without purchasing new security hardware.

Contracts that talk to each other

Decentralized applications rarely work in isolation, and more advanced operations require composability — the ability for different applications to plug into one another like interlocking building blocks. Ledger 9 introduces true composability through several features.

Cross-contract calls allow one contract to ask another to execute a function within the same transaction. This improves user experience considerably: instead of signing three separate transactions to approve a token, swap it, and deposit it into a liquidity pool, developers can combine the steps into a single user action. Contracts can also determine which contract called them and use that information to authorize specific actions — a secure vault, for example, could enforce a rule that only an approved lending contract may withdraw funds from it. Finally, smart contracts can now publish short public notices, such as “payment received.” When a transaction finalizes, the contract broadcasts the event, and wallets, explorers, and tracking programs listen for it and push organized data to front-end interfaces, refreshing balances in real time.

Without cross-contract calls, every team has to rebuild the same basic infrastructure inside its own contract, which is slower, harder to audit, and harder to upgrade. With this release, developers can create shared building blocks: a token standard, an identity check, or an escrow system can be written once, thoroughly audited, and reused across many applications. The team notes that this phase lays the groundwork for improvements to private DeFi, opening up applications that protect confidentiality while remaining regulatory compliant.

Infrastructure, documentation, and node operations

The release bundles numerous performance improvements with reliability upgrades and security maintenance patches, making Midnight safer to upgrade, easier to build on, and more secure. Most notably, all zero-knowledge proofs and their matching verification keys now use a new version called the Zero-Knowledge Intermediate Representation (ZKIR V3). This upgrades the compiler to support the new signature formats and serves as the underlying packaging that enables the network’s new cryptographic features. To support the accelerated rollout, the engineering team is finalizing technical documentation directly in the code repository, which will eventually detail exact opcode references and transaction format specifications.

What Ledger 9 unlocks

Taken together, native ECDSA signatures, enterprise custody support, and smart contract composability open several doors for the ecosystem:

  • Institutional custody and capital: Direct compatibility with ECDSA and BIP-44 derivation lets regulated custodians such as BitGo integrate Midnight into their existing hardware security systems, paving the way for institutional asset management.
  • Modular DeFi: By connecting modular contracts, builders can assemble sophisticated decentralized applications that streamline multi-step transactions into a single click.
  • A foundation for advanced private finance: By handling external cryptographic standards and multi-contract flows natively, Ledger 9 creates the structural runway for private cross-chain stablecoins and end-to-end shielded DeFi workflows.

Notes on the release process

Unlike previous upgrades, Ledger 9 was deployed directly to mainnet, bypassing the standard Preprod deployment and soak period. The team says this approach is used when security fixes require a more controlled release path to protect the network. While mainnet cNIGHT DUST registrations replay automatically, builders on Preview and Preprod will need to re-register their tNIGHT on those networks to resume DUST generation.