**Smart Privacy** Enhanced decentralized applications (dApps) require advanced privacy features. Oasis concentrates on providing Smart Privacy to Web3 and AI through a flexible, fully customizable confidentiality framework, replacing the traditional, complex, and inefficient tools currently in use. With innovations like the Sapphire runtime and the Oasis Privacy Layer (OPL) for Ethereum Virtual Machine (EVM)-based chains, Oasis offers cutting-edge confidentiality to any Web3 developer, even those not working directly on the Oasis Network. For applications on an alternate host chain, OPL integrates Sapphire’s privacy capabilities across any level of Web3. By offering a wide spectrum of confidentiality options with limitless customizability, Oasis is redefining how developers approach privacy integration and reshaping the available tools for prioritizing privacy in Web3 and AI. **Layered Architecture** The architecture of the Oasis Network was established with a strategic decision to separate the network's consensus layer from the compute layer. Oasis delivers privacy-preserving computation via runtime environments within the compute layer. A proof-of-stake (PoS) mechanism secures the consensus layer, which serves as a core network hub to achieve agreement on transaction ordering, validity, and global state. The compute layer acts as the platform for executing smart contracts, comprising multiple parallel runtimes (ParaTimes) crafted for specific computational requirements. This layered architecture supports dynamic and cost-effective deployment of dApps operating on Oasis or utilizing its technology while being hosted on another network. Each ParaTime seamlessly integrates into the Oasis consensus layer. Moreover, each Oasis runtime can independently evolve while maintaining security ensured by the consensus layer. This structure allows users and developers comprehensive control over their dApps' execution and confidentiality, as well as the associated data. **Efficient Confidentiality** Oasis stands out from other privacy networks and technologies by simultaneously optimizing for efficiency and confidentiality. Different dApps handle varying amounts and types of user data, but every data load can be processed on Oasis with consistent efficiency levels. Whether dealing with data-heavy smart contracts or simple transaction data, both can be executed efficiently with optional end-to-end encryption within the Oasis runtimes. By segregating the consensus and compute layers, Oasis permits its execution environments to function without interference from each other. Consensus is settled on a separate layer and accessed by applications on the compute layer only when required. While other networks provide extreme privacy through inefficient computation or extreme efficiency without strong privacy, Oasis architecture supports both.

The Oasis Network (ROSE) currently has a circulating supply of 6.5 billion tokens, with its total supply capped at 10 billion ROSE. Upon its genesis, the initial token distribution was structured as follows: * 23.5% – Staking rewards * 23% – Backers * 5% – Strategic partners and reserve * 18.5% – Community and ecosystem * 10% – Foundation endowment * 20% – Core contributors On the Oasis Network consensus layer, ROSE is employed for transaction fees, staking, delegation, and governance. Additionally, ROSE is utilized for transaction fees and compute costs in the Oasis compute layer.

Oasis is safeguarded by a proof-of-stake (PoS) mechanism within its consensus layer, supported by a decentralized array of validator nodes managed by a global network of independent users. Fraud proofs, based on discrepancy detection, protect the distinct compute and consensus layers within the network. For confidential runtimes such as Sapphire and Cipher, Oasis nodes are mandated to utilize a secure computing technology known as a Trusted Execution Environment (TEE). This acts as a secure enclave for smart contract execution, utilizing encrypted memory and remote attestation. Encrypted data is input along with the smart contract and validity proofs. Subsequently, the data is validated, decrypted, and processed by the smart contract. Contract data is then re-encrypted before being transmitted out of the TEE. This method not only mitigates developer and user friction but also ensures that data remains confidential and is never disclosed, even to node operators or application developers.

The Oasis Network is constructed and supported by a dynamic, decentralized community of engineers and developers. Significantly, a number of core contributors possess PhD degrees and have expertise in computer security and cryptography. Additionally, Oasis receives backing from a group of industry-leading supporters and external contributors who jointly manage a $235 million Ecosystem Fund aimed at promoting ecosystem development within Oasis. The Oasis Foundation also oversees an active grants program to assist builders and creators using the network.

The Oasis compute layer facilitates multiple parallel runtime environments, known as ParaTimes, enabling Web3 developers to create decentralized applications on any existing runtime or even develop their own. Unique ParaTimes can be crafted independently to fulfill the specific needs of any application, encompassing privacy parameters, staking requirements, programming languages, and more. Currently, there are three separate ParaTimes operational on Oasis: Sapphire, Emerald, and Cipher. Sapphire is the pioneering confidential EVM-compatible runtime. It offers developers the distinct ability to create EVM-based on-chain dApps with smart contracts that range from completely confidential to entirely public, and any level of confidentiality in between. Sapphire is an innovative developer environment that provides a familiar framework for EVM developers, enhanced by the advantages of Oasis Smart Privacy technology. Emerald is a runtime on Oasis that delivers full EVM compatibility and high-performance scalability. It was designed to address two primary challenges faced by every Web3 developer: gas fees and cross-chain interoperability. By utilizing the Emerald runtime, developers can ensure their users do not experience performance slowdowns or unexpected congestion. Cipher is a WebAssembly (WASM)-based privacy-enabled runtime built on Oasis. Utilizing Cipher and the Oasis Contract SDK, developers can employ Rust to create the next generation of confidential dApps. The power of Sapphire is not exclusively for native Oasis developers. Through the Oasis Privacy Layer framework, Oasis extends Sapphire’s privacy capabilities to the entire Web3 space. Crypto developers can effortlessly integrate Oasis privacy into their existing dApps on any EVM network without the need to migrate their applications and users from their native blockchain. For native builders and users of the Oasis Network, a comprehensive suite of tools supports a seamless experience for monitoring and transacting on the network. Oasis Wallet serves as the official non-custodial wallet for storing, sending, and receiving digital assets on the Oasis Network. With the successful implementation of Oasis Safe by ProtoFire on Sapphire and a collaboration with Transak, Oasis users benefit from industry-leading custody solutions and convenient on-ramps for the Oasis ecosystem. Oasis Explorer offers an intuitive platform for exploring on-chain activities from Oasis users and developers. By providing insightful data and analytics across all Oasis runtime environments, the Explorer allows users to assess the growth and progress of Oasis. Oasis Nexus acts as the official indexer tool for the Oasis Network and underpins explorers and wallets. Nexus continuously retrieves blockchain data from one or more Oasis nodes, parses the data, and stores it in a heavily indexed SQL database. This setup supplies a JSON-based web API for data access. For further details, please refer to Eulerpool for comprehensive information on Oasis.