Can a blockchain built around privacy still play nice with the signature method banks already use? As of November 6, 2026, Midnight Network’s answer is yes. Midnight, a privacy-focused chain that runs alongside Cardano, pushed the Midnight Ledger 9 upgrade straight to its live mainnet that day. It adds support for ECDSA signatures, the same scheme Bitcoin and Ethereum wallets use, along with a handful of other changes aimed mostly at developers and, eventually, big institutional custodians.
Here’s what Midnight’s own blog post confirms, what two independent crypto outlets add on top of it, and what still hasn’t been tested anywhere outside a press release.
What Changed in the Midnight Ledger 9 Upgrade
Midnight calls Ledger 9 a hard fork, its term for an upgrade that changes the rules validators follow. The network’s blog post and two independent outlets, TokenPost and Coinranking, agree on the core list of changes:
- ECDSA signatures. Midnight’s ledger previously accepted only Schnorr signatures. Ledger 9 adds ECDSA, the signing method used across Bitcoin, Ethereum, and most other major chains. Midnight’s blog says this lets “the largest institutional custody providers” connect using hardware and software they already run, without building anything Midnight-specific.
- BIP-44 wallet derivation. This is the standard that lets one seed phrase generate many wallet addresses. Supporting it means custodians and wallet makers can spin up Midnight addresses with tools they already have, instead of buying new hardware.
- Native Keccak-256 hashing. This is the hashing method Ethereum uses to fingerprint data. Midnight’s smart-contract language, Compact, can now compute it directly, which matters for any contract that needs to check Ethereum-style data without writing custom code for it.
- Contract-to-contract calls. One smart contract can now call another inside a single transaction. Coinranking’s writeup frames the practical upside as fewer separate approvals: an action that used to need three signatures (approve a token, swap it, deposit it) can collapse into one.
- Event logs. Contracts can now publish simple public notices, like “payment received,” that wallets and blockchain explorers can watch for, instead of requiring custom tracking code.
- A new proving system. Midnight’s zero-knowledge proofs, the math that lets the network verify a private transaction without seeing its contents, moved to a new version called ZKIR V3, needed to support the new signature types.
None of the three sources I could read gives a transaction-speed number, a fee figure, or an adoption count. If Midnight has published throughput data for Ledger 9, it wasn’t in the blog post I read.
Why Skip the Usual Safety Net?
Here’s the detail that would normally raise a flag at a bank’s IT department: Midnight’s own blog post says Ledger 9 “has been deployed directly to mainnet, bypassing the standard Preprod deployment and soak period.” Translated, that means skipping the usual stretch of time an upgrade spends running on a test network before it touches real money. Midnight’s blog says that shortcut is reserved for situations “when security fixes require a more controlled release path,” which suggests at least part of Ledger 9 patched something urgent rather than just adding features.
That’s a reasonable call for a true security fix. It’s also exactly the kind of shortcut that turns into a headline if something breaks. Base’s Denim upgrade ran into an unrelated bug with empty blocks within hours of launch earlier this month, a reminder that a clean-looking upgrade announcement and a chain that’s survived real, adversarial traffic are two different things. Ledger 9 hasn’t had that test yet, at least not one anybody’s published.
There’s also a practical cost for anyone building on Midnight. Deployed contracts and existing balances migrated automatically, but developers now need Midnight.js version 5 and have to recompile new contracts with an updated toolchain targeting Ledger 9. Builders on Midnight’s test networks have to manually re-register their test tokens to keep earning the network’s staking-reward currency. None of that touches ordinary holders on mainnet, whose registration carried over without any action needed.
The Custody Pitch, and the Bank That Still Hasn’t Launched
The real audience for Ledger 9 isn’t someone holding NIGHT, Midnight’s token, in a personal wallet. It’s regulated custodians, the companies banks and funds trust to hold crypto on their behalf. Midnight’s blog names BitGo specifically, saying ECDSA and BIP-44 support “lets regulated custodians like BitGo integrate Midnight into their existing hardware security systems.” That’s a claim about technical compatibility, not an announced partnership. Nothing in Midnight’s post, or in the independent coverage I found, says BitGo has actually signed on or built anything.
The closest real-world test case is Monument Bank, a UK lender that partnered with the Midnight Foundation in March to explore tokenizing retail deposits, up to £250 million worth, on Midnight’s network. Standard Chartered took a similar institutional custody route with Ripple’s RLUSD stablecoin earlier this year, so the pattern of a bank quietly piloting a token rail before saying anything about go-live isn’t new. But Monument’s founder told CoinDesk back in September that the rollout had already slipped, that the bank had identified but not named a Canadian custody provider, and that a November launch was merely anticipated, not locked in. As of this story, Monument hasn’t confirmed customers can use anything.
What We Don’t Know Yet
- No performance numbers. Nobody involved has published transaction speed, fees, or adoption figures tied specifically to Ledger 9.
- No named custodian deal. BitGo is cited only as an example of the kind of custodian the upgrade could attract, not a confirmed partner.
- Monument’s timeline keeps slipping. The one concrete institutional use case tied to Midnight, tokenized retail deposits at a UK bank, was delayed as of September and still isn’t live.
- The “why skip testing” question is unanswered. Midnight’s blog hints at an urgent security fix but doesn’t say what the fix addressed.
- Detailed technical docs are still coming. Midnight’s own post says exact opcode references and transaction-format specs will arrive “over the coming weeks,” after the upgrade already shipped.
Who Benefits and How
This is infrastructure, not a consumer product, so the benefit depends entirely on who’s asking.
- Developers building privacy-preserving apps on Midnight get cheaper, simpler multi-step transactions once they rebuild for Ledger 9, and a way to verify Ethereum-style data without writing custom code.
- Regulated custodians and the institutions that rely on them get a technical on-ramp, hardware and signature standards they already run, that didn’t exist on Midnight before November 6. Whether any of them actually use it is still an open question.
- Retail bank customers, like the UK account holders Monument Bank would eventually serve, are the farthest removed from today’s change. If tokenized deposits ever ship, the pitch is settlement that isn’t tied to banking hours. Right now that’s a plan with a slipped timeline, not something anyone can sign up for.
- Anyone just holding NIGHT or using a Midnight-based app today has nothing new to do. The migration happened automatically, and nothing about a typical user’s experience changed on November 6.
A privacy chain spent its first big mainnet upgrade making itself look more like the custody-friendly, compliance-ready infrastructure a bank’s lawyers would recognize. That’s a deliberate bet on who adopts privacy tech next, institutions before individuals. Whether that bet pays off depends on whether BitGo, Monument, or anyone else actually ships something on top of it in the next few months.
Sources
- Midnight Network: Ledger 9 Upgrade on Mainnet (Nov. 6, 2026)
- TokenPost: Midnight Completes Ledger 9 Upgrade for Private Cross-Chain Deposits (Nov. 10, 2026)
- Coinranking: Midnight Ledger 9 Hard Fork Brings Private Asset and Stablecoin Transfers (Nov. 7, 2026)
- Blockonomi: Midnight Upgrade Expands Options for Institutional Custodians (Nov. 11, 2026)
