Midnight Don Activate Ledger 9: New Era for Private DeFi

Di mainnet upgrade go allow smart contracts to dey interact inside one single transaction and e add cryptographic standards for wallets, custody providers, and cross-chain applications.

By SongMarketCap

Updated:

Midnight News - Midnight Don Activate Ledger 9: New Era for Private DeFi

Midnight don finish hard fork wey upgrade im mainnet from Ledger 8 go Ledger 9. Di release introduce direct calls between smart contracts, expand compatibility with existing blockchain infrastructure, and include security and performance improvements.

According to Midnight, existing token balances and deployed smart contracts migrate automatically. Mainnet cNIGHT holders no need do anything to continue dey generate DUST, di resource wey dem dey use cover transaction costs.

Di network deploy Ledger 9 direct to mainnet, skip im usual Preprod deployment and observation period. Midnight describe am as controlled release path wey dem dey use when security fixes need extra protection for di network.

Smart Contracts Fit Work Together Now

Ledger 9 allow one smart contract to call function for another one inside di same transaction. Dis capability, wey dem dey call composability, give developers way to connect reusable components when dem dey build applications.

Midnight give example wey involve three DeFi steps: approve token, swap am, and deposit am into liquidity pool. With connected contracts, developers fit combine all those operations into one single user action.

Contracts fit also identify which other contract call dem and use dat information to authorize specific operations. Example be say vault fit allow approved lending contract to withdraw funds while e go restrict access from other contracts.

Di release introduce public events and logs wey contracts fit publish when action happen. Wallets, explorers, and other applications fit monitor those events and show di information wey come out to users.

Midnight present these capabilities as foundation for more advanced private financial applications. Separate Private Composability milestone still dey for im roadmap for first quarter of 2027. Developers still need consider wetin their contracts dey disclose: Midnight documentation note say cross-contract call dey expose address of di called contract.

New Standards Go Expand Wallet and Custody Compatibility

Ledger 9 add native support for ECDSA, digital signature method wey Bitcoin and Ethereum dey use, and Keccak-256, cryptographic hash function wey dem dey use for Ethereum ecosystem.

Di ledger now dey accept both Schnorr and ECDSA signatures for transaction authorization. According to Midnight, direct ECDSA support go make am easier for custody providers to connect their existing systems to di network.

Di release also implement BIP-44, standard wey allow wallets derive multiple addresses from single seed. Midnight expect say dis addition go help wallet providers and institutional custodians integrate di network into existing infrastructure.

For di Compact programming language, di new cryptographic capabilities give developers tools to build connections with other blockchains. Midnight identify private stablecoin transfers and cross-chain financial applications as potential uses. Each bridge, custody service, or token integration still need im own implementation.

[NEWSBREAK]

Wetín Change for Developers and Token Holders

Previously deployed contracts carry over without modification and no need recompile or redeploy because of di migration. Application developers go need update to Midnight.js 5, while contracts wey never deploy yet must compile with Compact toolchain wey target Ledger 9.

Di release also update infrastructure wey dem dey use generate and verify zero-knowledge proofs. Im support for ZKIR v3, intermediate format for cryptographic programs, enable newer signature formats. Ledger 9.1.0.0 release notes identify specific circuit types wey their verification keys need regenerate.

Mainnet cNIGHT DUST registrations dey replay automatically. For di Preview and Preprod test networks, builders must register their test NIGHT, or tNIGHT, again to continue dey generate DUST.

Midnight engineering team still dey complete documentation for some of di new capabilities. More technical details, including operation code references and transaction format specifications, dey planned for release within di coming weeks.