Sig Network announced on Oct 28 a partnership with the Midnight Foundation (@midnightfdn) that will allow applications on Ethereum to use the privacy features of @MidnightNtwrk without leaving the Ethereum network, according to the Midnight announcement. The integration is currently live on Midnight's stagenet test network. Per the same announcement, Sig Network is the signing network behind Midnight's Nightmode privacy design.

How the Setup Works

According to the Midnight announcement, Sig Network assigns an Ethereum account to each Midnight contract. A threshold of signers — described by Sig Network as independent — produces the signatures, and the network signs only what the Midnight contract requests. No single signer can act alone.

The announcement lays out the flow in three steps: first, the Midnight contract validates the request, burns the user's shielded claim and queues one Ethereum transaction. Next, the signers produce a standard Ethereum signature. Finally, Ethereum executes the transaction and the outcome is attested back to Midnight.

Assets Remain on Ethereum

Assets stay on Ethereum throughout, meaning the design requires no bridges or wrapped tokens. That is a notable distinction because wrapped assets ordinarily depend on a custodian or bridge contract holding the underlying tokens, an arrangement that has been a recurring source of security incidents across the industry. Because the account is an ordinary Ethereum account, it can trade on Uniswap or lend on Aave like any other. The announcement states that the contracts can include compliance controls and selective disclosure, allowing authorised institutions to access information when needed.

Midnight is a privacy-focused partner chain to Cardano developed by Input Output. CoinDesk, which covered the go-live of Midnight's NIGHT token, reported that it is built around zero-knowledge proofs, with a dual-state design that separates public and private data while enabling controlled disclosure to auditors, institutions or counterparties.

What Stays Private and What Does Not

According to the Midnight announcement, user balances and identities remain shielded on Midnight, while transaction amounts and timing on the Ethereum side stay public. The stagenet deployment covers Ethereum deposits, Uniswap swaps, Aave supply and withdrawals to any Ethereum address.

The announcement lists use cases including private trading against Uniswap prices, shielded yield on Aave, private positions on prediction and perpetuals venues through a pool, and shielded deposits and withdrawals. For developers, it says they can import a Signet module into Midnight's Compact language to queue Ethereum transactions, and an example repository includes an ERC-20 vault supporting deposit, withdrawal, swap and supply functions.

A TokenPost report from Oct 20 on Midnight's Nightmode design, which uses Sig Network's signing system, also described a working demonstration on stagenet covering Ethereum deposits, Uniswap swaps, Aave supply and withdrawals.

Limits Flagged Before the Announcement

CryptoSlate published an analysis on Oct 22, 2026, ahead of the partnership announcement. It reported that withdrawals from Sig Network's experimental Ethereum vault depend on its signing network, even though the underlying assets remain on Ethereum. It noted that Sig Network's full-stack demo runs on Midnight stagenet and Ethereum's Sepolia testnet — both public testnets — with a simulated signing responder, and therefore does not establish that a production group of independent signers is operating.

CryptoSlate also said that evaluating a live deployment requires knowing how many signers must cooperate, who operates them, how those arrangements can change and what recovery is possible when ordinary service is unavailable — the same diligence questions customarily applied to any design that routes withdrawals through a signing network.

On timing, CryptoSlate reported that mainnet support is tied to Midnight's ledger v9 upgrade on Sig Network's roadmap. At the code version it reviewed, the vault's published address registry contains a stagenet address and a blank mainnet entry, which the file defines as not yet deployed or published. As things stand, a published mainnet address and a confirmed production signer set are the concrete markers to watch as the integration moves from stagenet toward mainnet.

Sources

• Midnight: Sig Network partners with Midnight Foundation to bring privacy to applications on Ethereum
• TokenPost: Midnight Details Nightmode Design for Private Cross-Chain DeFi
• CryptoSlate: A Midnight privacy-vault demo needs outside signers to release Ethereum tokens
• CoinDesk: Cardano ecosystem gets a privacy boost as Midnight's NIGHT goes live