Midnight Moves Closer to MetaMask and EVM Tooling Support

Midnight is moving closer to supporting MetaMask and existing Ethereum development tools without turning its privacy-focused network into an EVM blockchain.

Midnight Foundation CTO Sebastien Guillemot said on August 11 that an EVM emulation mode is nearing release and demonstrated MetaMask connected to a Midnight development environment. The work is advancing alongside account abstraction designed to let partners reuse existing wallet and EVM infrastructure instead of building a separate integration stack.

Midnight is a Cardano partner chain focused on programmable privacy and selective disclosure using zero-knowledge technology. It operates its own ledger while maintaining technical and economic connections with the Cardano ecosystem.

Midnight Is Building an EVM Compatibility Layer

Midnight is not an EVM blockchain. Instead, the team is building an emulation layer that allows existing EVM wallets and tools to communicate with Midnight through familiar interfaces while preserving its own privacy architecture.

Guillemot demonstrated the functionality using MetaMask, with the wallet connecting to a Midnight development environment, signing requests and interacting with NIGHT.

According to Guillemot, the EVM emulation mode works with multiple EVM tools and wallets. MetaMask is the concrete example demonstrated publicly so far, while Midnight documentation does not yet list tools such as Hardhat, Foundry or ethers.js as production-supported integrations.

The approach is designed to give developers and infrastructure providers a familiar integration path without replacing Midnight’s zero-knowledge execution model with the Ethereum Virtual Machine.

Account Abstraction Targets Integration Costs

EVM emulation is part of a broader account abstraction effort intended to reduce the infrastructure required to integrate Midnight.

Non-EVM integrations can require dedicated wallet connectors, SDK integrations, RPC infrastructure and separate onboarding flows. Reusing an existing EVM stack could remove part of that development work for wallets, applications and other partners.

Guillemot estimated that the approach could deliver an “easily a 100x cost reduction” for many partner integrations. No separate public cost breakdown has been released to quantify that estimate.

The same architecture targets user onboarding. Instead of requiring a dedicated Midnight wallet for every application, users could access the network through wallets they already use.

Midnight’s NIGHT and DUST architecture addresses another part of that experience. NIGHT generates DUST, a shielded and non-transferable network resource used for transaction fees. DUST is not purchased as a separate gas token, and applications can sponsor transaction capacity for their users.

Combined, EVM emulation, account abstraction and DUST are designed to reduce both the infrastructure partners need to build and the steps users need to complete before interacting with Midnight applications.

The Cardano Connection Goes Beyond NIGHT Distribution

Midnight is not a Cardano Layer 2, and its transactions do not execute or settle directly on Cardano mainnet. It is a separate partner chain with its own ledger, consensus and privacy infrastructure.

The networks nevertheless share several direct technical and economic connections. Cardano stake pool operators can participate in Midnight’s validator infrastructure, while the partner-chain architecture provides interoperability mechanisms between the networks.

NIGHT was initially minted as a Cardano Native Asset, and registered NIGHT UTXOs on Cardano are connected to DUST generation through Midnight’s observation infrastructure. The Cardano community was also directly involved in NIGHT’s initial distribution, with approximately half of the total supply allocated to ADA holders through the Glacier Drop.

The MetaMask implementation demonstrated by Guillemot remains a development-stage feature. Moving EVM emulation and account abstraction into production would change how Midnight can be integrated: partners could connect its privacy infrastructure to wallets and tooling already used across the EVM ecosystem instead of building a separate Web3 access layer for each integration.