Oasis Network (ROSE)

Overview

Oasis Network is a layer-1 blockchain built for privacy and scale. Its design splits the chain into two parts: a consensus layer that secures the network and a ParaTime layer where applications run. This separation lets many runtimes (called ParaTimes) process transactions in parallel, so heavy workloads in one area don’t slow everything else down. The network’s native token, ROSE, is used to pay fees, stake for security, and participate in governance. A standout feature is Sapphire, a confidential EVM that lets developers write normal Solidity smart contracts while keeping contract state and inputs encrypted. This makes Oasis attractive for apps that need confidentiality, like private DeFi, sensitive data analytics, or secure voting. (docs.oasis.io)

History & Team

Oasis grew out of Oasis Labs, a company founded in 2018 by Dawn Song, a professor at the University of California, Berkeley and a MacArthur Fellow known for her work in security and privacy. Early technical leaders helping build the stack included Raymond Cheng, Noah Johnson, and Bobby Jaros. Oasis Labs raised over $45 million in 2018 from a group of well-known investors including Andreessen Horowitz (a16z), Accel, Binance, Pantera, Polychain, Electric Capital, and others. That funding helped develop the core research and engineering that later became the Oasis Network. (people.eecs.berkeley.edu)

As the network matured, the Oasis Protocol Foundation guided network development and governance. The team’s academic background in cryptography and systems security influenced two pillars that still define Oasis today: a modular architecture that scales by running multiple runtimes in parallel, and privacy technologies that protect data while it is being processed. (docs.oasis.io)

Technology & How It Works

Modular architecture: consensus + ParaTimes

Oasis separates consensus from computation. The consensus layer is a proof‑of‑stake blockchain using a Byzantine Fault Tolerant engine (CometBFT/Tendermint lineage) for fast, final settlement. The ParaTime layer hosts many parallel runtimes. Each runtime executes transactions in its own environment and posts succinct commitments back to consensus. If results diverge, a “discrepancy detection” process kicks in to resolve the issue and keep the system honest without complex sharding. This design behaves like native rollups at the base layer. (docs.oasis.io)

Confidential computing with TEEs

Confidential ParaTimes on Oasis can run inside Trusted Execution Environments (TEEs) such as Intel SGX. TEEs keep data encrypted in memory during execution so node operators cannot inspect inputs or internal state. Oasis adds remote attestation—cryptographic proof that code is running inside genuine secure hardware—so contracts and users can verify the environment before sharing secrets. Attestation details (e.g., SGX DCAP) are built into node software and verified on-chain. (docs.oasis.io)

ParaTimes available today

• Sapphire: the confidential EVM. Developers deploy standard Solidity contracts, but contract state, calldata, and randomness can be kept confidential. Mainnet launched in 2022. (docs.oasis.io)
• Emerald: an EVM-compatible, transparent runtime optimized for low fees, ~6‑second finality, and high throughput—useful for typical DeFi/NFT work. (docs.oasis.io)
• Cipher: a confidential runtime for WASM smart contracts, written primarily in Rust, with flexible choices over what data to keep public vs. private. (docs.oasis.io)

Cross‑chain privacy: Oasis Privacy Layer (OPL)

OPL lets apps on other EVM chains call confidential logic on Sapphire through message bridges, then receive results back on their home chain. This pattern can power features like secret ballots for DAOs or private order flow in DeFi, while users keep assets on their preferred network. Gas relayers can even cover ROSE gas behind the scenes for smoother UX. (docs.oasis.io)

Off‑chain logic for secure services (ROFL)

Runtime Offchain Logic (ROFL) is a framework for trusted off‑chain tasks—like oracles, game servers, or AI inference—that can attest results back to Sapphire. ROFL apps run in TEEs and talk to confidential contracts when needed. (docs.oasis.io)

Tokenomics & Utility

ROSE is a capped‑supply token with a fixed maximum of 10 billion. At mainnet launch, about 1.5 billion were in circulation, with a portion reserved to be released over time. Roughly 2.3 billion ROSE are dedicated to on‑chain staking rewards paid to validators and delegators for securing the network. The token is used for transaction fees, staking, delegation, and governance. (docs.oasis.io)

The network aims for broad participation through proof‑of‑stake:

• Validator set size targets around 120 entities. Stake weight determines who is elected to propose blocks. The minimum stake thresholds to register an entity and validator are modest (on the order of 100 ROSE each), and the unbonding period is ~14 days. Slashing applies to double‑signing. (docs.oasis.io)
• Community governance combines off‑chain discussion with on‑chain votes; node operators vote proportionally to stake. The governance process has supported upgrades, such as adjusting the staking reward schedule. In March 2024, Proposal #4 extended the ~2.5% reward rate until the common pool is exhausted, with the docs updated to reflect the change. (docs.oasis.io)

At a high level, the distribution has included allocations to early backers, core contributors, the Oasis Foundation endowment, community/ecosystem programs, strategic partners/reserves, and a long‑term pool for staking rewards. The Foundation has also published a delegation policy to support reliable validators. (docs.oasis.io)

Ecosystem & Use Cases

Private and scalable DeFi

Oasis supports two styles of DeFi development. On Emerald, builders get a low‑fee EVM for familiar apps like DEXs and lending. YuzuSwap, one of the earliest Emerald projects, highlighted the network’s speed and low costs. On Sapphire, builders gain privacy by default. illumineX, a confidential, MEV‑resistant DEX, launched with grants and a dedicated liquidity program to grow cross‑chain pools. These efforts reflect a broader push to seed core DeFi primitives on Sapphire. (docs.oasis.io)

Data tokenization and responsible data use

Because confidential computing is native, Oasis is often described as a platform for a “responsible data economy.” Apps can tokenize access to sensitive datasets (for example, health or financial data), analyze them privately inside TEEs, and reward data owners according to usage policies without exposing raw data. This model aims to align developers, enterprises, and individuals while meeting privacy goals. (oasis.net)

Governance and voting

With OPL and Sapphire, DAOs can run secret‑ballot votes where only the final tally is public. Oasis provides examples like voTEE and other confidential‑voting demos to help teams adopt this pattern. (docs.oasis.io)

Cross‑chain privacy services

Existing dApps on Ethereum, BNB Chain, or other EVM networks can add selective confidentiality by sending messages to Sapphire via OPL, then syncing results back. This enables private credit scoring, sealed‑bid auctions, protected order flow, or private on‑chain identity checks. (docs.oasis.io)

Oracles, AI, and gaming backends

ROFL makes it easier to run off‑chain logic in TEEs with attestations to on‑chain contracts. That helps with privacy‑preserving AI inference, fair game servers, or specialized data feeds that must prove correctness and integrity. (docs.oasis.io)

Advantages & Challenges

Advantages

• Built‑in privacy: Confidential EVM (Sapphire) keeps contract state and inputs encrypted, shielding them even from node operators while preserving verifiability. (docs.oasis.io)
• Parallel scale: Multiple ParaTimes execute in parallel, so workloads don’t compete for the same blockspace. The consensus layer finalizes results quickly with BFT finality. (docs.oasis.io)
• Native rollup‑style design: Oasis effectively treats ParaTimes as rollups, using discrepancy detection to validate results—a simpler alternative to complex sharding. (oasis.net)
• EVM compatibility plus more: Developers can choose EVM (Emerald/Sapphire) or WASM (Cipher) and tailor confidentiality to each use case. (docs.oasis.io)
• Cross‑chain privacy: OPL lets existing apps add confidentiality without migrating assets or users. (docs.oasis.io)

Challenges

• TEE trust model: Confidential runtimes rely on secure hardware and timely firmware/microcode updates. Operators must track SGX/TDX guidance to keep attestation valid. This dependency can be operationally demanding. (docs.oasis.io)
• Learning curve: The split between consensus and ParaTimes, plus deposits/withdrawals between layers, adds UX and developer complexity compared to single‑state chains. (docs.oasis.io)
• Ecosystem maturity: While DeFi and tools are growing, Oasis still competes with larger EVM ecosystems for developer mindshare and liquidity; foundation grants and security programs are working to accelerate growth. (oasis.net)

Where to Buy & Wallets

Oasis Network can be purchased on Binance and Binance.US. ROSE is available on KuCoin and MEXC, with additional regional listings such as Gate brands. Always check the supported deposit network for each exchange; many centralized platforms use the Oasis consensus layer for deposits/withdrawals. (support.binance.us)

ROSE Wallet is the official non‑custodial wallet for Oasis. It is offered as a web app and a browser extension, supports staking and ParaTime deposits/withdrawals, and integrates with Transak for card/bank purchases in supported regions. The ROSE App (rose.oasis.io) simplifies moving tokens between exchanges and Sapphire. MetaMask works for Sapphire and Emerald (EVM accounts), while Ledger hardware wallets integrate with the ROSE Wallet and CLI for added key security. For bridging wrapped ROSE (wROSE) from BNB Chain to Sapphire, Celer cBridge is supported. (oasis.net)

Regulatory & Compliance

Oasis is a general‑purpose smart‑contract network. ROSE primarily serves as a utility token for paying fees, staking, delegation, and governance. How a token is treated in law varies by jurisdiction and depends on facts and circumstances; Oasis documents describe ROSE’s functions but do not assign a legal classification. At a technical level, the network’s confidentiality features can help builders design applications that align with privacy obligations (for example, processing sensitive data inside TEEs, providing audit logs, and using selective disclosure), but meeting any specific regulation—like GDPR or U.S. state privacy laws—depends on how each app handles data and consent. (docs.oasis.io)

On faith‑based compliance, Oasis Network is often viewed more favorably by some Islamic finance reviewers because its rewards come from protocol emissions and transaction fees tied to securing and using the network, rather than interest‑based lending. Others may differ based on their interpretation of digital assets. The underlying facts—that ROSE’s incentives come from a fixed supply model with a defined staking reward pool and that the token is used for network fees and governance—are public and documented. Community members seeking formal guidance typically consult a qualified scholar in their jurisdiction. (docs.oasis.io)

Future Outlook

Several threads point to where Oasis is headed:

• Confidential EVM adoption: As more apps need privacy—private order flow, sealed‑bid auctions, or compliant data use—Sapphire offers a familiar Solidity environment with confidentiality by default. (docs.oasis.io)
• Cross‑chain growth via OPL: Expect more projects on other EVM chains to call into Sapphire for privacy tasks while keeping users and liquidity on their home networks. Gas relayers and better tooling should keep improving UX. (docs.oasis.io)
• DeFi on Sapphire: Grants and liquidity programs are seeding DEXs and other primitives. As these building blocks mature, the ecosystem can diversify beyond swaps into lending, structured products, and identity‑aware finance that preserve user privacy. (oasis.net)
• Trusted off‑chain services: ROFL and TEEs enable oracles and AI agents that can attest to correct execution, opening new designs for data‑driven apps. (docs.oasis.io)
• Ongoing protocol evolution: Governance has already adjusted staking economics; similar proposals can refine incentives, validator sets, and runtime features as usage patterns change. (forum.oasis.io)

Summary

Oasis Network blends a modular, rollup‑like architecture with built‑in privacy. The split between a BFT proof‑of‑stake consensus layer and a parallel ParaTime compute layer lets the network scale while giving developers choice: EVM with or without confidentiality, or confidential WASM. ROSE fuels the system through fees, staking, and governance, with a fixed total supply and a defined rewards pool. With Sapphire’s confidential EVM, OPL’s cross‑chain privacy, and a growing toolkit for secure off‑chain logic, Oasis targets use cases that need both performance and data protection—private DeFi, secure voting, AI with sensitive datasets, and more. While the TEE‑based trust model and ecosystem maturity present challenges, the network’s design and active development make Oasis a noteworthy platform for privacy‑first applications in Web3. (docs.oasis.io)