Zama Expands Confidential Morpho Vaults and Launches Private Swaps on Ethereum

Advertisement

Encrypted Finance Takes a Concrete Step on Ethereum Mainnet

On July 23, Zama pushed its Confidential RFQ swap protocol live on Ethereum mainnet in private beta – a move that shifts the conversation around onchain privacy from theoretical infrastructure to a functioning product. The protocol connects to a Morpho vault denominated in confidential USDC, or cUSDC, that had already accumulated more than $40 million in deposits by September 2026. That figure, confirmed by Morpho, arrived with a notable qualifier: individual user positions remain hidden onchain.

The two products – the confidential vault and the RFQ swap venue – are now explicitly linked. Users can hold cUSDC, earn yield through the Steakhouse-curated Morpho deployment, and swap against other confidential token pairs, all without broadcasting wallet balances, transaction amounts, or trade direction to the public ledger. The full picture only emerged gradually, with the vault launching weeks before the swap protocol, but the architecture was clearly designed to connect them.

Abstract visualization of encrypted data flowing through a digital network
Via cryptodaily.co.uk

How the Confidential Vault Was Built Before the Swaps Arrived

The vault component came first. On June 17, Zama announced the Steakhouse Confidential USDC Prime vault, framing it as the first DeFi yield product built for cUSDC. Deposits opened on June 23, with Steakhouse Financial handling curation and Morpho providing the deployment infrastructure. The launch positioned the product as a privacy layer over an existing strategy rather than a new credit structure built from scratch.

That distinction shapes how the vault actually works. The Steakhouse Confidential USDC Prime vault mirrors Steakhouse Prime USDC on Morpho directly – same collateral, same markets, same risk parameters, same credit strategy. What Zama added was a fully homomorphic encryption layer that encrypts deposit sizes, positions, and timing. The effect is that a cUSDC holder can participate in the same underlying lending strategy as any regular USDC depositor, without exposing their activity on Ethereum. The privacy wrapper does not change what the capital does; it changes what others can see about it.

Morpho has confirmed that deposits are batched every 24 hours before being supplied to the vault. This batching mechanism is not incidental – it limits the granularity of timing-based inference attacks, where an observer might try to deduce position sizes by watching when exactly capital enters a protocol. The $40 million aggregate figure that Morpho reported by September 2026 demonstrates that institutional or at least sizable capital has been willing to engage with the product despite its private-beta constraints.

The csteakUSDC token produced by the vault then becomes material to the swap side of the system. Zama includes a csteakUSDC/cUSDC trading pair in its Confidential RFQ venue, which means the output of the confidential lending strategy is directly exchangeable within the same encrypted ecosystem. That link between the vault token and the swap venue is not cosmetic – it extends the utility of confidential capital beyond passive yield accumulation into active, encrypted exchange functionality.

Advertisement
Close-up of financial market data displayed on a trading screen
Photo by Alex Luna / Pexels

What the RFQ Protocol Actually Does With Order Flow

Zama’s Confidential RFQ operates as an onchain request-for-quote system, but with a structural difference from conventional onchain swaps: trade size and direction stay encrypted. The protocol also encrypts a trader’s price limit, which is typically visible in standard onchain order mechanisms and can be used by sophisticated participants to front-run or extract value from pending trades. Currently supported pairs include cUSDT/cUSDC, cZAMA/cUSDC, and csteakUSDC/cUSDC.

Market makers fill orders through a blind auction format. Whitelisted participants compete to provide quotes without seeing the publicly visible order details that would normally define how market makers position themselves in a conventional venue. The whitelist requirement keeps participation controlled during the private-beta period, which limits volume but also limits the attack surface for a protocol handling encrypted financial data. Whether the whitelisted maker set expands – and under what conditions – has not been specified.

Zama has also tied the swap protocol directly to its token mechanics. All swap fees collected by the Confidential RFQ venue are allocated to buying back and burning ZAMA. That arrangement makes the swap product more than a trading interface – it channels fee revenue into supply reduction for the protocol’s native token, giving the venue an explicit role in ZAMA’s broader economic design. The burn mechanism is documented in Zama’s community forum and was part of the July 23 launch disclosure.

The Infrastructure Underneath and What Remains Unresolved

The encryption underpinning both products is Zama’s fully homomorphic encryption, or FHE, technology. FHE allows computations to be performed on encrypted data without decrypting it first – a property that makes it theoretically well-suited for financial applications where verification and execution must happen onchain while concealing inputs. The practical challenge with FHE has historically been computational cost and latency, and Zama has not published detailed benchmarks on how those trade-offs manifest in the live swap product under real market conditions.

Server infrastructure representing blockchain protocol deployment
Photo by Christina Morillo / Pexels

What Zama has demonstrated is that a coherent product stack is operational: a confidential lending vault with $40 million in deposits, an encrypted swap venue with blind auction market making, and a fee structure tied to token mechanics. The private-beta format means that access remains gated and volume data is limited, but the architecture connecting cUSDC deposits to the Steakhouse strategy and then to the RFQ venue is functioning on Ethereum mainnet. The question sitting directly in front of the protocol now is whether the blind auction mechanism, with its whitelisted maker set, can generate competitive quotes – and whether spreads in a market where makers cannot see order details will be tight enough to attract meaningful flow once the beta restrictions lift.

Advertisement

Comments are closed, but trackbacks and pingbacks are open.