Oasis

What is Oasis Network?

Oasis Network is a proof-of-stake layer-one blockchain whose core value proposition is “confidential compute”: it is designed to let applications process sensitive inputs and maintain selectively private state while still settling to a public blockchain, aiming to expand what can be built onchain beyond fully transparent DeFi-style state machines.

Its moat is not raw throughput but an architectural focus on confidentiality as a first-class primitive, most visibly through its confidential EVM, Sapphire, and its cross-chain extension, the Oasis Privacy Layer (OPL), which is positioned as a way for existing EVM dApps to outsource only the “privacy-requiring” portion of logic to Oasis while keeping users and assets on their origin chain.

In market structure terms, Oasis tends to screen as a niche L1 whose differentiation is privacy-preserving computation rather than generalized liquidity depth.

As of May 2026, ROSE sat around the low-#300s by market-cap ranking on large price aggregators (for example CoinMarketCap listed it at #295 at the time of review), and on DeFi-native telemetry its onchain economic footprint appears modest relative to mainstream L1s; for instance, DeFiLlama’s Oasis Sapphire chain page showed sub-$1m TVL in the period observed, implying that most investor attention is likely driven more by thematic “privacy/AI compute” optionality than by present-day fee generation.

That said, Oasis’s product surface area is broader than a single chain metric suggests: OPL explicitly targets cross-chain privacy use cases where activity may originate and remain economically anchored on other networks, with Oasis serving as a confidential execution venue rather than the primary liquidity hub.

Who Founded Oasis Network and When?

Oasis is closely associated with Oasis Labs and founder Dawn Song, an academic security researcher who became the public face of the project prior to mainnet. The network’s mainnet launch occurred on November 18, 2020, which Oasis framed as a decentralized launch with 70+ validators in its announcement post, “Oasis Mainnet: Ushering in a New Era of Privacy and Scalability”.

The timing matters contextually: it came after the 2017–2018 cycle’s collapse and during the early phase of DeFi’s 2020 expansion, when alternative L1 narratives were competing to differentiate on scaling and application specialization.

Over time, the project’s narrative has drifted from a relatively broad “privacy + scalability for Web3” positioning toward a more specific thesis: Oasis as a confidentiality and verifiable-compute layer that can plug into the EVM ecosystem.

That evolution is visible in its emphasis on Sapphire as a confidential EVM runtime (rather than a bespoke smart contract environment) and, later, in the push toward cross-chain privacy via OPL and toward verifiable offchain execution via Runtime Offchain Logic (ROFL).

The implicit pivot is away from competing head-on with general-purpose L1s on liquidity and composability, and toward being infrastructure for specialized workloads—particularly those where transparent execution is a non-starter (private auctions, selective disclosure identity, proprietary models/data, or enterprise-style workflows).

How Does the Oasis Network Work?

Oasis uses proof-of-stake consensus, with ROSE staked and delegated to validators who participate in block production and finality at the consensus layer; public token references and the project’s own documentation consistently describe ROSE’s role in staking and network security (see CoinMarketCap’s overview and Oasis docs on governance and upgrades such as Network Governance).

Architecturally, Oasis separates consensus from execution via a layered design where multiple runtimes (historically called ParaTimes) can execute in parallel while anchoring results to the base consensus layer, an approach intended to reduce execution-layer contention and to allow heterogeneous runtime environments (EVM and non-EVM) under one security umbrella.

Where Oasis becomes technically idiosyncratic is its confidentiality model and its willingness to make trusted hardware part of the threat model. Sapphire’s confidentiality relies on trusted execution environments (TEEs) for encrypted state/transaction processing with remote attestation rather than on purely cryptographic privacy systems like zkSNARK-only designs; third-party developer infrastructure summaries such as thirdweb’s Sapphire overview and Oasis’s own materials describe Sapphire as an EVM that executes Solidity contracts inside secure enclaves, keeping state and calldata encrypted while remaining EVM-compatible.

ROFL extends the same “attested execution” philosophy offchain by allowing non-deterministic, network-interactive, or heavy compute to run offchain while producing verifiable outputs that can be consumed onchain; Oasis’s official announcement of ROFL mainnet launch and the design discussion in ADR 0024 make clear that ROFL is meant to preserve an onchain verification path while relaxing the determinism and resource constraints of smart contracts.

The security trade-off is straightforward: TEEs can shrink the engineering friction versus ZK-heavy approaches but introduce a dependency on hardware vendors, attestation chains, and enclave compromise risk; Oasis attempts to mitigate this with attestation flows and committee-based operation, but the residual risk profile is qualitatively different from purely cryptographic privacy systems.

What Are the Tokenomics of ROSE?

ROSE is a capped-supply asset with a stated maximum of 10 billion tokens, widely repeated across aggregator listings such as CoinMarketCap and in Oasis’s own educational materials (e.g., “A Beginner’s Guide to Oasis”).

A capped maximum supply does not automatically mean the asset is “deflationary” in practice; what matters is the emissions path and the pace of unlocks/distributions versus burn and fee capture.

Oasis’s documentation describes a large portion of supply earmarked for staking rewards over time (for example, its docs discuss staking rewards allocations and targeted staking reward ranges in Token Metrics and Distribution), implying that—until distribution matures—the system behaves inflationarily from the perspective of circulating supply.

As of May 2026, most but not all supply appeared to be circulating on major trackers (CoinMarketCap showed roughly mid-to-high 70% of max supply circulating at the time of review), which reduces “unknown future dilution” versus early-stage networks but does not eliminate emissions-related sell pressure where staking rewards are routinely realized.

ROSE’s utility case is conventional for a PoS L1 but with added demand surfaces tied to confidential compute. It is used for staking/delegation to secure the network and earn rewards, for transaction fees/gas (including Sapphire execution), and for governance processes (as reflected in general token summaries like CoinMarketCap and Oasis’s own educational posts such as the beginner’s guide).

Value accrual, therefore, is primarily indirect: usage-driven fee demand and staking-driven demand for collateral to capture emissions and governance influence.

For Oasis specifically, a realistic analyst stance is that near-term “cash flow” style value capture is likely limited by the relatively small DeFi footprint observable on chain dashboards like DeFiLlama, so the investment debate tends to hinge on whether confidential EVM execution (Sapphire), cross-chain privacy middleware (OPL), and verifiable offchain compute (ROFL) translate into durable developer adoption and fee markets rather than one-off integrations.

Who Is Using Oasis Network?

A clean way to separate speculation from usage is to compare exchange liquidity (which can exist without product-market fit) with measurable onchain economic activity.

As of early-to-mid 2026, publicly visible DeFi TVL on Oasis Sapphire tracked by DeFiLlama remained small, and 24h DEX volume frequently appeared negligible in the same dashboard view, suggesting that sustained DeFi liquidity is not yet the network’s dominant “proof of use.”

This does not falsify the privacy thesis, but it does mean analysts should be cautious about extrapolating token liquidity into application traction.

Where Oasis does show concrete “usage intent” is in developer-facing infrastructure for confidential EVM applications and cross-chain privacy composition. Oasis maintains active documentation for OPL integration across multiple bridge frameworks, including Hyperlane, Router Protocol, and Celer IM, and it publishes canonical contract/address references for bridged assets and tooling in its developer docs (see Contract Addresses and Deployments, last updated Feb 2026).

That kind of documentation footprint is not adoption by itself, but it is typically a prerequisite for serious third-party integration.

On the partnership front, Oasis’s own materials and community posts frequently reference collaborations, but an institutional-grade read treats these as heterogeneous: some are co-marketing, some are grants, and some are actual product integrations.

The most defensible “institutional” signal, therefore, is not partner logos but whether OPL and ROFL integrations are deployed, maintained, and measurably used in production—something that, as of 2026, appears earlier-stage than the largest privacy or general-purpose execution ecosystems.

What Are the Risks and Challenges for Oasis Network?

Regulatory exposure for ROSE is best framed as the generic U.S. risk envelope for smart-contract platform tokens rather than as a protocol-specific enforcement story.

As of the last 12 months reviewed, there was no prominent, widely reported U.S. regulator lawsuit or ETF process directly centered on ROSE in mainstream coverage surfaced in this research pass; that absence should not be misread as regulatory clarity, only as a lack of a visible, token-specific headline event.

The more structural regulatory risk is classification uncertainty (whether secondary market activity could be argued to involve securities), plus privacy-adjacent scrutiny if confidential computation becomes associated—fairly or not—with illicit finance; Oasis’s “selective privacy” framing via OPL partially anticipates this by emphasizing configurable privacy rather than blanket anonymity, but the policy environment remains fluid.

Technically and operationally, the most material centralization vectors are validator concentration (a general PoS concern) and TEE dependency (a more Oasis-specific concern).

If a confidential EVM’s security assumptions rest on TEEs and attestation, systemic vulnerabilities in enclave technology, supply chain issues, or vendor policy shifts can become protocol-level risks. ROFL extends this surface area by bringing offchain networking and heavier computation into an attested framework (see the design rationale in ADR 0024), which can expand the bug and attack surface even as it expands capability.

From a market-structure standpoint, Oasis competes not only with “privacy L1s,” but also with general-purpose L2s and middleware that can bolt privacy onto existing liquidity centers. In practice, the competitors that matter are those that can deliver comparable developer ergonomics, security assurances, and composability without requiring developers to move users or liquidity, which is exactly the wedge OPL is trying to claim; the strategic risk is that the EVM ecosystem standardizes around alternative privacy primitives (e.g., ZK-based private state segments, encrypted mempools, or application-specific rollups) faster than Oasis can win mindshare.

What Is the Future Outlook for Oasis Network?

The most verifiable near-term roadmap items are those Oasis has published directly and those reflected in its maintained documentation.

Oasis’s official blog laid out priorities in “2025: The Oasis Roadmap”, emphasizing continued Sapphire/OPL ecosystem expansion, ROFL adoption, and developer/UX improvements, including efforts around bridging and onboarding. In addition, ROFL’s shift from concept to production is a concrete recent milestone: Oasis announced ROFL mainnet as officially live on July 2, 2025, and subsequent documentation work suggests ongoing productization rather than a one-off release.

OPL documentation was updated as recently as May 7, 2026 in the official docs (OPL docs), indicating active maintenance.

The structural hurdle is not whether Oasis can ship features—it demonstrably does—but whether those features produce sustained demand for confidential execution that is economically legible in fees, sticky integrations, and a durable developer base.

For institutional evaluators, the key forward indicators are whether OPL becomes a repeated pattern for existing EVM dApps (not just demos), whether ROFL becomes a credible alternative to centralized offchain automation for “AI agent” and cross-chain verification workflows, and whether the network’s TEE-based security model earns enough trust to be used for high-value state.

The roadmap’s feasibility is therefore less about raw engineering and more about catalyzing a privacy-compute category that developers will adopt even when it increases architectural complexity, because the application economics or user safety benefits are sufficiently large.