Oasis price

ROSE

• Smart Privacy

Better dApps require smarter privacy. This is why Oasis focuses on delivering Smart Privacy to Web3 and AI in the form of a flexible, fully customizable confidentiality framework that replaces the rigid, complex and inefficient tools in the status quo. With technologies like the Sapphire runtime and its accompanying Oasis Privacy Layer (OPL) for EVM-based chains, Oasis brings cutting edge confidentiality to any Web3 developer, even ones that don’t build directly on the Oasis Network. For applications running on a separate host chain, OPL allows the powerful privacy features of Sapphire to be integrated on any layer of Web3. By creating a spectrum of confidentiality with unlimited customizability, Oasis is redefining how developers think about integrating privacy and reshaping the toolset available for prioritizing privacy in Web3 and AI.

• Layered Architecture

Architecting the Oasis Network started with a key decision to separate the network’s consensus layer from the compute layer. Oasis provides privacy-preserving computation via runtime environments on the compute layer. A proof-of-stake (PoS) mechanism secures the consensus layer, which acts as a hub for reaching network-wide agreement on transaction ordering, validity and global state. The compute layer, which functions as the execution platform for smart contracts, consists of multiple parallel runtimes (ParaTimes) that are built for specialized computation needs.

This layered approach allows for a dynamic and low-cost deployment of any dApps running on Oasis or using Oasis technology while running on another host network. Each ParaTime plugs into the Oasis consensus layer. Each Oasis runtime can also evolve independently of the others while maintaining security provided by the consensus layer, enabling users and developers to have complete control over the execution and confidentiality of their dApps and associated data.

• Efficient Confidentiality

Oasis differentiates itself from other privacy networks and technologies by optimizing for both efficiency and confidentiality simultaneously. Every dApp manages different amounts and types of user data, but every data load can be processed on Oasis with the same level of efficiency. From data-heavy smart contracts to simple transaction data, both can be executed efficiently with optional end-to-end encryption in one of the Oasis runtimes.

By operating separate consensus and compute layers, Oasis allows its execution environments to operate unencumbered by each other. Consensus is settled on a separate layer and accessed by applications running on the compute layer when necessary. While other networks offer extreme privacy only through inefficient computation or extreme efficiency without robust privacy, the Oasis architecture enables both.

The current supply of Oasis Network ROSE is 6.5 billion tokens, with a total supply of 10 billion ROSE. The initial token distribution upon genesis was as follows:

• 23.5% – Staking rewards
• 23% – Backers
• 5% – Strategic partners and reserve
• 18.5% – Community and ecosystem
• 10% – Foundation endowment
• 20% – Core contributors

ROSE is used for transaction fees, staking, delegation and governance on the Oasis Network consensus layer. ROSE is also used for transaction fees and compute costs in the Oasis compute layer.

The Oasis compute layer supports multiple parallel runtime, or ParaTime, environments which allows Web3 developers to build decentralized applications on any existing runtime or even launch their own. Unique ParaTimes can be developed in isolation to meet the specific requirements of any application, including privacy parameters, staking requirements, development language and more.

Three separate ParaTimes already run on Oasis: Sapphire, Emerald and Cipher.

Sapphire is the first confidential EVM-compatible runtime. Sapphire provides developers with the unique capability to build EVM-based on-chain dApps with smart contracts that are completely confidential, completely public, or anywhere in between on the spectrum of confidentiality. Sapphire is a groundbreaking developer environment that offers a familiar building environment for any EVM developers with the added benefits of Oasis Smart Privacy technology.

Emerald is a runtime built on Oasis that offers full EVM compatibility and high-performance scalability. Emerald was engineered to solve two key problems faced by every Web3 developer: gas fees and cross-chain interoperability. Using the Emerald runtime, developers can build with confidence that their users will not suffer performance lags or surprise congestion.

Cipher is a WebAssembly (WASM)-based privacy-enabled runtime built on Oasis. With Cipher and the Oasis Contract SDK, developers can use Rust to build the next generation of confidential dApps.

But accessing the power of Sapphire is not limited to native Oasis developers. With the Oasis Privacy Layer framework, Oasis brings the power of Sapphire privacy to all of Web3. Crypto developers can seamlessly add Oasis privacy to their existing dApp on any EVM network without having to migrate their application and users away from their native blockchain.

For native builders and users of the Oasis Network, there is a suite of tools that support a seamless experience monitoring and transacting on the network.

Oasis Wallet is the official non-custodial wallet for storing, sending and receiving digital assets on the Oasis Network. With the successful deployment of Oasis Safe by ProtoFire on Sapphire and a partnership with Transak, Oasis users also have access to an industry-leading custody options and easy on-ramps for the Oasis ecosystem.

Oasis Explorer provides an easy-to-use deep dive into on-chain activity from Oasis users and developers. By surfacing powerful data and analytics across all Oasis runtime environments, the Explorer queries data for users to analyze the growth and development of Oasis.

Oasis Nexus is the official indexer tool for the Oasis Network and the backend for explorers and wallets. Nexus continuously fetches blockchain data from one or more Oasis nodes, parses the data and stores it into a heavily indexed SQL database, which provides a JSON-based web API to access the data.