Hey Cardanians! Welcome aboard the Weekly Cardano Digest #151!

We've filtered through all the noise to distill crucial updates into a breezy, 5-minute read. No need for you to sift through endless info ,we've got you covered. Ready to delve into this week's top Cardano news? Let’s dive in.

Here are the topics of the week:

• 🌙 Midnight Ships Ledger 9 Directly to Mainnet

• 🏦 Midnight Takes Institutional Privacy to the SALT Conference

• 🧩 Lace 2.5 Lets Cardano Accounts Designate cNIGHT to Generate DUST

• Weekly Development Report

• & More!

🌙 Midnight Ships Ledger 9 Directly to Mainnet

Midnight completed its upgrade from Ledger 8 to Ledger 9 on mainnet on November 6, and the way it got there is as notable as what it contains. Previous Midnight upgrades went to Preprod first and sat through a soak period before touching mainnet. Ledger 9 bypassed both and was deployed directly to the live network — an approach the team says it reserves for cases where security fixes require a more controlled release path. Preprod remains on Ledger 8 for now, so builders targeting the test network are working against an older ledger until it catches up.

The contents are squarely aimed at interoperability. Ledger 9 adds native support for widely used cryptographic standards, including ECDSA and Keccak-256 — the primitives that Ethereum and most of the tooling built around it already assume. It expands wallet and custody compatibility, and it enables contracts to interact directly with one another. That last item is the one builders have been waiting on: contract-to-contract execution within a single transaction turns a collection of isolated private contracts into something composable, where existing functionality can be extended and reusable components combined instead of rewritten.

Put together, the release reads less like a privacy-chain upgrade and more like a compatibility layer. ECDSA and Keccak-256 lower the cost of connecting Midnight to the infrastructure institutions and custodians already run; broader custody support is the unglamorous prerequisite for anyone holding assets on behalf of someone else. The honest caveat is that a direct-to-mainnet deployment trades the usual safety margin for speed, and a version gap with Preprod is an awkward place for developers to sit. Both are defensible when the alternative is leaving a security fix in a public queue — but they are costs, not free wins.

👉 Learn more

🏦 Midnight Takes Institutional Privacy to the SALT Conference

At the SALT Conference, Midnight's argument moved from cryptography to banking rails. Input Output highlighted the panel on November 4, where the framing was deliberately unromantic: banks bringing financial services on-chain are still bound to protect customer data, and that obligation is what makes privacy infrastructure an adoption requirement rather than an ideological preference. A fully transparent ledger is not a feature a regulated institution can accept; it is a reason not to deploy.

The work with Monument Bank is the concrete case. In a clip published the following day, Monument Bank's Mintoo Bhandari described what he calls the "Uberization" of DeFi — an experience as simple as ordering a car, with the privacy and security machinery kept entirely out of sight. The user never chooses a proof system or reasons about shielded balances; they open a product that works. It is the same abstraction argument that made payments usable, applied to a stack whose complexity is currently its biggest barrier.

This is a different register from most Cardano ecosystem news — no release, no milestone, no number to cite. It is worth tracking anyway, because it is the clearest statement yet of who Midnight thinks its customer is. The pitch is not to crypto-native users who want privacy on principle; it is to institutions that need it to ship at all. That focus explains a lot about Ledger 9's priorities this same week, and it sets a fairly demanding bar: the measure of this strategy will be deployed products at named institutions, not conference panels about them.

👉 Learn more

🧩 Lace 2.5 Lets Cardano Accounts Designate cNIGHT to Generate DUST

Lace 2.5 shipped for the browser extension on October 30, and this week's Essential Cardano development report spells out what landed. The headline feature wires the two networks together inside a single wallet: users can now designate cNIGHT from their Cardano accounts to generate DUST, without juggling two applications or moving assets between them. For anyone following Midnight's rollout, this is the piece that makes the token mechanics usable rather than theoretical.

The rest of the release is maintenance of the kind that actually decides whether people keep a wallet installed. Lace 2.5 brings improvements to transactions, DApp signing and syncing, plus a per-account sync reset — a small but genuinely useful addition for the case where one account's local state goes bad and resyncing the entire wallet would be an absurd remedy. None of this makes headlines; all of it is the difference between a wallet that feels reliable and one that does not.

The release sits inside a dense week elsewhere in the report. The Leios prototype rc-2026w44 added adaptive endorsements, which shrink endorser blocks when votes are insufficient, while rc-2026w43 cut certifying-block forging time from as much as 0.9 seconds down to milliseconds. Hydra merged monitoring for snapshot progress, queues and persistence along with dashboards and example alerts. DevX published a Dijkstra readiness tracker and reassessed its tooling against the cardano-node 11.2.0 prerelease. Plutus finalized cost models for the keepPolicies and dropPolicies builtins and added 65 conformance cases for the new Value builtins. Steady, unglamorous progress on all fronts.

👉 Learn more

Interesting Stories

Essential Cardano’s weekly development report