Crypto privacy has spent years being easier to demonstrate than to use. The cryptography could be impressive, but the practical question was harder: once your assets are private, what can you actually do with them?
A new cluster of products around Zama and Morpho is beginning to offer a more concrete answer.
In June 2026, Zama introduced confidential USDC access to a Morpho vault curated by Steakhouse Financial. Instead of exposing an individual depositor’s balance and position on Ethereum, the product uses Zama’s confidentiality infrastructure to keep that information encrypted while capital is ultimately deployed into an existing DeFi credit strategy.
Three months later, the experiment has expanded. On September 15, Zama opened confidential access to 16 Morpho vaults spanning five asset classes and five curators, alongside a confidential swap system for moving between encrypted assets.
The important development is not simply that Fully Homomorphic Encryption, or FHE, works on a blockchain. The more interesting shift is that privacy is beginning to attach itself to recognizable financial products.
- ⚡ Why This Is Interesting
- The Product Is the Important Part
- One Vault Has Become a Small Private-DeFi Surface
- The Real Problem Is Metadata
- Confidential Swaps Make the Experiment More Interesting
- Signal to Watch — Can users stay private between actions?
- Even Incentives Create a Privacy Leak
- Signal to Watch — Privacy becomes an integration problem
- Why Build on Existing DeFi Instead of a Private Chain?
- Privacy Is Not the Same as Anonymity
- Risk / Overhype Check
- What Would Actually Prove the Thesis?
- Signal to Watch — Distribution beats cryptography
- Who Should Pay Attention?
- 🔭 Where to Look Next
- The Bigger Shift
- Key Takeaway
⚡ Why This Is Interesting
Private DeFi has traditionally implied moving into a separate privacy system and accepting its smaller liquidity pool, different applications and additional infrastructure.
Zama is testing almost the inverse model: keep Ethereum, keep existing DeFi venues and strategies, and insert confidentiality between the user and the public financial position.
If that model proves durable, privacy may become less of a destination and more of a feature that financial applications can selectively add.
The Product Is the Important Part
Zama’s underlying technology is FHE, which allows computation over encrypted information without first exposing the underlying data. That cryptographic mechanism is important, but explaining FHE from first principles is not the interesting discovery here.
What matters now is where it is being attached.
The first Zama–Morpho product launched for deposits on June 23. Users could convert USDC into confidential USDC, or cUSDC, and access a Steakhouse-curated strategy on Morpho while keeping their individual balance confidential.
Morpho describes the structure as using the same collateral, markets and risk parameters as the corresponding public Steakhouse Prime USDC strategy. Deposits from confidential users are batched into the underlying vault rather than publishing each user’s position individually.
Fact Morpho reported more than $10 million in Confidential USDC deposits during the first four days after launch.
By September, Zama said the first confidential vault had surpassed $40 million in shielded TVL within seven weeks. That figure is a project-reported metric and should not be confused with independent evidence of sustained product-market fit. But the progression was sufficient for the experiment to move beyond a single vault.
One Vault Has Become a Small Private-DeFi Surface
On September 15, 2026, Zama expanded confidential access to 16 Morpho vaults across USDC, USDT, WBTC, AUSD and TGBP.
The curator set also widened. Strategies are now associated with Steakhouse Financial, Armitage by Wintermute, Flowdesk, RockawayX and Bitwise. According to reporting from The Block, 12 of the products provide confidential access to existing Morpho vaults, while four are confidential-only products.
That distinction matters.
Privacy is no longer being demonstrated only through a special-purpose sandbox. Some of these products are attempting to put a confidentiality interface in front of financial infrastructure that already exists.
| Layer | What is changing | What to watch |
|---|---|---|
| Assets | Confidential versions of USDC, USDT, WBTC, AUSD and TGBP | Whether confidential assets develop utility beyond holding and transfers |
| Yield | 16 confidential Morpho vaults | Whether deposits persist beyond launch incentives |
| Curation | Five different strategy curators | Whether privacy becomes available across genuinely different risk profiles |
| Trading | Confidential swaps between encrypted assets | Whether users can remain private while moving between positions |
| Distribution | Additional wallet and platform integrations are planned | Whether confidentiality becomes accessible without a specialist interface |
| Incentives | Encrypted rewards through a Merkl integration | Whether privacy survives the full product lifecycle rather than only deposits |
The Real Problem Is Metadata
Public DeFi has an unusual property compared with conventional finance: financial activity is inspectable by default.
That transparency is useful. It allows independent verification of reserves, positions, smart-contract activity and protocol health. It is one of the reasons open financial infrastructure is possible in the first place.
But the same transparency can become commercially awkward when the participant is a treasury, fund, market maker or institution deploying meaningful size.
A visible wallet can reveal position size, allocation changes, entry and exit timing and relationships between addresses. Even when the identity behind an address is not formally disclosed, enough contextual information can make activity strategically useful to competitors or trading systems.
The emerging private-DeFi thesis is therefore not necessarily that blockchains should become opaque. It is that verification and universal financial surveillance do not have to be the same thing.
That is a much more practical proposition than privacy as an ideological endpoint.
Confidential Swaps Make the Experiment More Interesting
Private deposits solve only part of the problem. A user who shields a position and then exposes every trade made around it has not gained much.
Zama’s Confidential Swap product attempts to extend privacy to execution.
The system uses an RFQ-style market in which information including trade size, direction and price limits can remain encrypted through much of the process. According to Zama’s current product documentation, the system is designed so market makers cannot inspect the full order before competing to fill it.
That makes private DeFi more interesting as a product category because it starts connecting actions together.
A confidential asset that can only be held is mostly a privacy primitive. An asset that can be held, deployed into credit markets, moved between strategies and exchanged without repeatedly returning to a transparent state begins to resemble a usable financial environment.
Signal to Watch — Can users stay private between actions?
The important metric is not the number of confidential tokens. Watch whether a user can move through an increasingly complete financial workflow without privacy disappearing at each application boundary.
Even Incentives Create a Privacy Leak
A surprisingly useful example arrived on September 17.
Zama announced an integration with Merkl for confidential DeFi incentives. The problem it addresses is subtle: hiding a deposit does little good if a subsequent public reward claim reveals enough information to infer the size of the underlying position.
Under the integration, rewards can be calculated from encrypted balances and distributed as confidential tokens.
This may sound like a niche implementation detail. It actually illustrates one of the hardest problems in usable privacy systems.
Privacy is compositional. Protecting one transaction is insufficient if another part of the workflow leaks the same information indirectly.
For private DeFi to become a real product category, wallets, incentives, swaps, lending positions, redemption flows and analytics all need to be considered as possible disclosure points.
Signal to Watch — Privacy becomes an integration problem
If confidential finance grows, the interesting developer work may shift from proving that encrypted computation is possible to ensuring that privacy survives interactions between otherwise independent applications.
Why Build on Existing DeFi Instead of a Private Chain?
This is where the Zama approach becomes strategically interesting.
A separate privacy blockchain can optimize deeply for confidentiality. But it must also create liquidity, applications, integrations, distribution and user demand inside its own ecosystem.
Zama describes its protocol differently: as a confidentiality layer that can be deployed on existing L1s and L2s rather than a standalone blockchain.
That potentially changes the cold-start equation.
Instead of asking users to leave established markets to obtain privacy, the product can attempt to bring privacy to venues users already recognize.
Interpretation If this architecture works, existing DeFi liquidity may become part of the distribution strategy for privacy technology. Privacy protocols would no longer need to win the liquidity competition before they can offer useful financial applications.
But there is an important qualifier: attaching privacy to existing infrastructure does not automatically make the entire underlying system private. The boundaries between encrypted and public components matter enormously.
Privacy Is Not the Same as Anonymity
There is another reason the word confidential matters here.
The products emerging around Zama are not necessarily trying to make every participant and every action unknowable to everyone.
For example, Zama’s current swap design uses known, whitelisted professional market makers. The goal is closer to controlling which financial information becomes public than eliminating every form of identity or compliance control.
This distinction could prove important for institutional adoption.
A treasury may not require complete anonymity. It may need its position size hidden from competitors while retaining internal controls, reporting and the ability to satisfy legal obligations.
That creates a design space between today’s radically transparent DeFi and completely opaque financial systems.
Risk / Overhype Check
$40 million in one early vault does not prove that private DeFi has found product-market fit. The number was reported by the projects involved, the products are young, and incentives or novelty can affect early deposits.
There are also harder questions than attracting capital: encrypted computation introduces additional technical complexity; privacy can make monitoring and analytics more difficult; application boundaries can leak information; and compliance requirements may differ sharply between jurisdictions and products.
Most importantly, confidentiality has to provide enough practical value to compensate for any additional friction. If users encounter slower workflows, limited integrations or complicated asset conversions, public DeFi may remain preferable for many activities.
What Would Actually Prove the Thesis?
TVL alone will not answer the question.
A better signal would be repeated use of confidential positions by participants who specifically require information protection — and who continue using those products after initial campaigns or incentives disappear.
Another signal would be integration depth.
Zama says additional access through products including Utila, Zerion Wallet and Yield.xyz is expected following the September launch. If confidential positions eventually appear inside normal wallet, custody and treasury workflows, privacy starts becoming infrastructure rather than a destination users must deliberately seek out.
The third signal is composability.
Can confidential collateral be borrowed against? Can private vault positions move through different protocols? Can confidential assets be used for payments, tokenized securities or treasury operations without repeatedly revealing their balances?
The more applications that preserve confidentiality between one another, the stronger the case that this is becoming a distinct financial layer.
Signal to Watch — Distribution beats cryptography
For the next phase, watch wallets, custodians and financial platforms more closely than cryptographic benchmarks. Privacy becomes a product when users encounter it inside tools they already use.
Who Should Pay Attention?
DeFi builders should watch whether confidentiality becomes another configurable property of financial applications, alongside collateral types, oracle design and risk parameters.
Wallet teams should watch the UX problem. The winning privacy experience may be the one where users do not have to think about cryptographic infrastructure at all.
Institutional crypto teams should watch whether confidential products solve a genuine operational objection to public blockchains: exposing portfolio information to the entire market.
Privacy researchers should watch what breaks when cryptography encounters real financial workflows. Product deployment exposes problems that isolated benchmarks rarely reveal.
Onchain analysts should pay attention for the opposite reason. If financial confidentiality expands, some assumptions about universal observability will need to change. The industry may have to develop ways to measure protocol health without expecting every individual position to remain publicly inspectable.
🔭 Where to Look Next
- The original cUSDC vault: watch whether deposits remain durable as the product matures rather than focusing on its initial growth curve.
- The 16-vault expansion: compare demand across stablecoins, WBTC and other asset types to see where confidentiality actually matters to users.
- Confidential Swap: follow the transition from an interesting execution mechanism toward sustained trading activity and broader asset support.
- Merkl incentives: watch whether encrypted rewards demonstrate a broader pattern of privacy-preserving composability.
- Wallet and custody integrations: these may be more important for adoption than another cryptographic performance milestone.
- Disclosure boundaries: inspect exactly which information remains encrypted and what can still be inferred from deposits, batches, withdrawals and interactions with public protocols.
- Competing approaches: watch whether confidentiality layers attached to existing chains gain more traction than isolated privacy-first ecosystems.
The Bigger Shift
The most interesting thing happening in private DeFi is not that cryptography has suddenly solved privacy.
It hasn’t.
The shift is more modest and potentially more consequential: confidentiality technology is being forced to behave like a product.
That means dealing with yield strategies, liquidity, market makers, incentives, wallets, custody, user experience and all the awkward disclosure points that appear when encrypted assets interact with real financial infrastructure.
Zama’s expansion from one confidential USDC vault to a broader set of Morpho strategies and swaps is still an early experiment. There is not enough evidence yet to conclude that private DeFi will become a major category.
But there is now enough product surface to make the experiment worth watching.
Key Takeaway
The emerging private-DeFi thesis is not “move finance onto a private blockchain.” It is “bring selective confidentiality to the financial venues that already have liquidity.”
If that model works, privacy could evolve from a separate crypto ecosystem into an application layer: something users turn on when their balances, strategies or transaction intentions should not be visible to the entire market.
The evidence to watch next is not another cryptographic benchmark. It is whether people repeatedly use confidential lending, trading and treasury products when public alternatives are sitting beside them.
