Oasis Network And Privana: Private DeFi Moves Up The Stack

This article is based on a Hypernest X Space conversation with Nino, product lead at Oasis Network for Privana. The conversation was hosted by Yann from Hypernest as part of Hypernest’s ongoing series on DeFi, privacy, RWA, and onchain financial infrastructure.

Privana is a user-facing private DeFi product built on the Oasis stack. In this recap, we look at how privacy infrastructure can move into application-level use cases across swaps, yield, automation, delegated execution, and intent protection.

The discussion also touched on DeFi security, selective disclosure, and the role privacy could play as onchain financial products become more sophisticated.

This article reflects the discussion from the Space and should not be interpreted as an official roadmap, product commitment, legal position, investment recommendation, or security guarantee. Product features, timelines, incentives, and availability may change.

Listen to the full X Space here

Private DeFi is no longer only a protocol-layer debate.

It is becoming an execution-layer and product distribution question.

For years, privacy in crypto was discussed mostly as infrastructure: encryption, trusted execution environments, zero-knowledge proofs, confidential compute, and private execution environments.

That layer still matters. But the next question is different:

What can users actually do with it?

More specifically, can privacy be embedded into the workflows that actually move liquidity: swaps, yield routing, delegated execution, TWAPs, vault automation, app-level permissions, and strategy execution?

That was the focus of our conversation with Nino. The discussion covered Oasis Network’s move from privacy infrastructure toward user-facing products, the launch of Privana, and the role privacy can play across swaps, yield, automation, DeFi UX, and intent protection.

Why Privacy Is Back In The DeFi Conversation

Privacy is becoming relevant again because DeFi is moving from simple transaction execution toward more complex financial workflows.

The issue is not only that wallet balances and transaction histories are public. Crypto-native users already understand that tradeoff.

The deeper issue is that intent is often public before, during, and after execution.

A swap route, order size, wallet history, rebalance, treasury movement, or automated strategy can become visible to the market before the user has completed the action. In a market structure shaped by public mempools, MEV, copy-trading, real-time wallet monitoring, and socialized wallet intelligence, that visibility creates execution costs.

For retail users, this can mean unwanted exposure of financial activity.

For traders and funds, it can mean strategy leakage.

For protocols and DAOs, it can mean public treasury movements that are easy to anticipate.

For institutions, it can mean the absence of basic transaction confidentiality that already exists in traditional finance.

This is why privacy is coming back into the DeFi conversation. It is not only a values-based discussion around user privacy. It is also a practical discussion about execution quality, strategy protection, and whether onchain finance can support more sophisticated flows without leaking intent by default.

Nino connected this shift to regulation and adoption. As stablecoins, DeFi products, and onchain financial applications move closer to mainstream financial behavior, the public-by-default model becomes harder to reconcile with how real financial systems operate.

As he explained during the conversation, sending money through a neobank is private by default. Sending money with stablecoins on a public ledger is usually not.

That difference matters.

Why Oasis Network Is Moving From Protocol Layer To Application Layer

Oasis Network has long focused on privacy infrastructure.

Privana represents a different phase: taking that infrastructure and turning it into a user-facing DeFi product.

Nino described this as Oasis moving up the stack.

The strategic move is not only about building a user-facing product. It is about showing how privacy infrastructure can become embedded in workflows users already understand: swaps, yield, automation, and portfolio movement.

Instead of privacy only existing as developer tooling, Privana explores how users can interact with DeFi through privacy-preserving workflows.

That matters because infrastructure only becomes visible to the market when it shows up inside real user behavior.

Privana is also a form of dogfooding. By building directly on top of the Oasis stack, the team can test what works, what needs to be improved, and how privacy infrastructure behaves when it is exposed to actual DeFi usage.

This shift is important for the privacy category.

Privacy infrastructure has often been technically strong, and the next phase is making it easier for users and developers to experience directly.

The next phase is not only about proving that privacy can exist onchain. It is about turning privacy into something users can access inside normal DeFi workflows.

What Privana Is Building On Oasis Network

Privana is a private, hardware-protected, non-custodial DeFi interface built on Oasis Sapphire.

In the stack described by Privana’s docs, Privana is the user-facing application, FlexVaults is the backend engine, and Oasis Sapphire is the confidential blockchain foundation.

The design is meant to let users swap tokens, earn yield on stablecoins, and automate trading strategies without exposing the full activity publicly onchain.

The important nuance is that privacy depends on execution path. Internal matching and vault inventory can provide stronger privacy, while external DEX routing may still be visible onchain from a pooled vault address rather than the user’s personal wallet.

Privana is being built around several key use cases:

private swaps
private earn/yield products
TWAP automation
order splitting
vault-based portfolio activity
connected app permissions
delegated execution

The product uses the Oasis stack, including Sapphire and trusted execution environments, to create privacy-preserving execution environments around DeFi activity.

At a high level, Privana allows users to interact with target chains and DeFi protocols without exposing all of their intent directly to public markets.

For swaps, that means user intent can be hidden while execution still routes through internal matching, vault inventory, or external liquidity depending on the execution path.

For earn and yield products, the goal is to allow users to deposit into vault-like structures where assets can be deployed according to programmable policies.

The point is not to rebuild every DeFi primitive from scratch.

The point is to add a privacy layer around existing DeFi infrastructure.

Nino explained that the Privana SDK can generate keys inside trusted execution environments for target chains. Access to those keys is governed by policies, and the private key itself is not exposed directly.

That architecture is designed to allow Privana to work across chains and connect with existing DeFi venues while keeping privacy as the product’s core design principle.

The non-custodial model is also different from a standard wallet model. Instead of the user manually signing every transaction from a seed phrase, vault keys live inside TEEs and are governed by programmable policies. Users can authorize, limit, and revoke delegations while the underlying key material remains protected inside the enclave.

The more interesting design point is delegated execution.

Privana is not only trying to hide a transaction from public view. It is building around a model where users can authorize actions through programmable policies, while keeping the underlying key material protected and the execution intent less exposed.

That design space becomes especially relevant as DeFi moves toward more automated interfaces: trading bots, vault managers, rule-based execution, AI-assisted trading, and connected applications that need permissions without full custody.

Why Intent Privacy Matters

One of the strongest parts of the conversation was the discussion around intent.

In DeFi, a user’s intent can become public before execution. That creates real market structure problems.

A large swap, a TWAP order, or an automated rebalance can leak intent before execution.

If that intent becomes visible too early, other actors can react to it.

That may lead to worse execution, adverse routing, copy-trading, MEV exposure, or information leakage.

In crypto-native terms, intent privacy is not a cosmetic privacy feature. It is part of execution quality. It can reduce information leakage around order size, route selection, timing, strategy logic, and vault behavior before execution reaches public markets.

Privana’s approach is to keep more of that intent hidden inside a trusted execution environment, while still allowing execution to happen through DeFi rails.

For sophisticated users, this is not just a privacy preference.

It is execution quality.

This matters especially as DeFi becomes more automated.

TWAPs, order splitting, automated rebalances, yield routing, AI-assisted trading, and Telegram bot-based execution can all leak strategy if the logic is visible too early.

In that context, privacy becomes part of how execution is protected.

It is not only about hiding the user. It is about protecting the structure of the action itself.

Privacy As A UX And Permissioning Layer

The conversation also touched on user experience, but the UX problem in private DeFi is deeper than cleaner screens.

The challenge is abstracting complex permissioning, cross-chain execution, gas flows, routing, vault actions, and privacy guarantees without forcing users to manage each layer manually.

Nino’s framing was simple: users should be able to trade like they normally do, but privately.

That is the right product direction.

Privacy should not feel like a separate workflow. It should become part of the default execution environment.

This is especially important as DeFi moves toward more delegated interfaces: trading bots, automated strategies, AI agents, vault managers, and connected apps.

In that world, users are not only signing individual transactions. They are granting permissions.

The product question becomes: how can those permissions be programmable, revocable, non-custodial, and private by default?

That is the design space Privana is entering.

The opportunity for products like Privana is to make the privacy layer feel native to the DeFi experience.

Selective Disclosure, Not Blind Privacy

The Space also moved beyond the simple privacy-versus-transparency debate.

Nino raised selective disclosure as a possible long-term direction for private DeFi.

This is the idea that user activity can remain private by default, while still allowing disclosure under specific legal, compliance, or risk conditions.

That framing matters.

If DeFi wants to connect with regulated financial systems, privacy cannot only mean permanent opacity. Institutions, regulators, and users will need systems where privacy, auditability, and accountability can coexist.

Selective disclosure may become one of the bridges between public blockchain infrastructure and real financial adoption.

The important point is that privacy and compliance do not have to be framed as opposites.

A more mature version of private DeFi may allow users to preserve privacy in normal conditions while creating defined paths for disclosure when legal requirements are met.

That is very different from the current public-chain default, where everyone can inspect everything all the time.

This should be understood as a design discussion from the Space, not a confirmed description of current Privana functionality.

Why Security And Trust Still Matter

The Space also touched on the current trust problem in DeFi.

As DeFi matures, users are becoming more thoughtful about how they evaluate new products, especially when funds are involved.

Nino’s view was that DeFi cannot rebuild trust only through more audits or larger TVL numbers.

The next phase may require stronger financial guarantees, risk limits, insurance-like structures, and clearer accountability around protocol risk, integration risk, oracle risk, execution risk, and smart contract risk.

That is especially relevant for new privacy products.

Privacy may reduce certain visibility-based risks and protect sensitive intent, but it does not replace broader security practices, risk controls, audits, limits, or careful rollout.

For privacy products, the trust model matters as much as the UX. Users need to understand what is hidden, what is still visible, who can execute what, what permissions can be revoked, and what happens if an integration fails.

Privana’s model is not trustless in the purest sense. It relies on assumptions around Intel SGX, Oasis Sapphire, attested FlexVaults code, and external protocols used for routing or yield. The important point is that the system attempts to make those assumptions explicit, bounded, and enforced through hardware-protected policy controls.

Nino also emphasized that Privana intends to scale progressively. The early rollout is expected to include limits and testing phases, creating a more controlled environment for early users.

That matters.

For a product dealing with privacy, execution, and funds, progressive rollout is part of building a thoughtful user experience.

The Roadmap For Privana

Privana has opened its waitlist.

According to Privana’s public roadmap, Phase 1 focuses on its Private Core. This includes private swaps across Ethereum, Base, and HyperEVM; best-route execution through LiFi aggregation; structural MEV protection; TWAP automation; automatic order splitting; an idle yield module; a vault dashboard; action history; and connected app permissions.

Privana’s roadmap also highlights core guarantees across every phase, including non-custodial design, mempool privacy, revocable delegations, fallback recovery, spot-only activity until a collateral engine exists, and vetted protocols for yield.

For a crypto-native audience, the important point is that Privana is not only positioning privacy as a shield around transactions.

The roadmap points toward private execution as a coordination layer: swaps, TWAPs, delegated actions, connected app permissions, and yield routing can all become part of a more private DeFi workflow.

At the time of the Space, Nino said the team was internally testing the earn feature and targeting June for the start of closed beta access.

The initial closed beta is expected to include limitations and incentives, creating a controlled environment for early users.

He also suggested that broader onboarding could come closer to autumn as the product continues to progress.

That staged rollout is important.

For a product dealing with privacy, execution, and funds, progressive scaling helps create a more thoughtful early user experience.

Nino also mentioned that the Oasis team is working on another product on top of the same SDK, with more details expected in the future.

What Oasis Network And Privana Mean For Private DeFi

The broader takeaway from the conversation is that privacy is becoming part of DeFi’s product architecture.

It is not only a philosophical position.

It affects execution quality, user experience, institutional adoption, strategy protection, automation, and the relationship between DeFi and regulation.

Privana is one example of this shift: privacy infrastructure moving into user-facing applications.

For DeFi to mature, more products will need to move beyond raw onchain visibility and offer financial experiences where privacy, control, accountability, and usability are built into the user journey.

That does not mean DeFi should abandon transparency.

It means the industry needs more precise tools.

Some information should be public. Some information should be private. Some information should be disclosed only under defined conditions.

That is a more realistic design space for financial applications.

For founders, investors, and ecosystem operators, the key question is whether privacy can become a default product primitive for DeFi rather than a niche feature.

Privana points toward that direction: privacy as infrastructure, but also privacy as execution quality, permissioning, UX, and distribution.

Build With Hypernest

At Hypernest, we partner with early-stage DeFi and Web3 founders working on the next generation of financial infrastructure.

Through our venture studio model, we help teams validate markets, sharpen product direction, build ecosystem visibility, and prepare for sustainable growth.

If you are building in DeFi, privacy, RWA, or Web3 infrastructure, apply to work with Hypernest.