CoinYQ

What is Oasis?

Oasis Network is a Layer 1 decentralized blockchain designed around scalability, privacy, and versatility. Its defining architecture separates a proof-of-stake consensus layer from a compute layer made of parallel ParaTimes, allowing different execution environments to share the network while processing workloads independently.

The network is oriented toward applications that need confidential data and verifiable execution. Oasis documentation describes confidential ParaTimes as secure-compute environments in which encrypted inputs are processed inside trusted execution environments (TEEs), preventing node operators or application developers from seeing the underlying data.

Its current developer stack includes Sapphire, an EVM-compatible confidential ParaTime, and ROFL (Runtime Off-Chain Logic), a framework for running applications in TEEs while anchoring management and verification through Sapphire. These components target private DeFi, trustless agents, confidential oracles, identity, gaming, DAOs, tokenized assets, and verified payments.

What problem does Oasis solve?

Public blockchains make execution and state broadly observable, which is useful for auditability but unsuitable for many financial, business, identity, and consumer applications. Running complex computation entirely on-chain can also be costly and slow; moving it off-chain improves practicality but ordinarily sacrifices verifiability.

Oasis addresses this trade-off by combining on-chain consensus and policy enforcement with confidential execution. TEEs keep data encrypted from infrastructure operators while attestations and cryptographic verification let users check what code ran, although the security model still depends on the enclave hardware, correct application logic, and careful handling of outputs.

How does Oasis work?

The consensus layer is a high-throughput proof-of-stake network run by decentralized validators. The ParaTime layer hosts replicated compute environments, each with its own execution rules and state. Because ParaTimes run in parallel, a demanding workload in one runtime need not slow simpler transactions in another; developers can create ParaTimes with different VM choices, committee models, hardware requirements, and permission settings.

Sapphire is the network's confidential EVM ParaTime. It supports end-to-end encrypted state, confidential randomness, EVM-based dApp integration, cross-chain bridges, and one-block (approximately six-second) finality according to the official docs. Developers can adapt Solidity/EVM applications while using Sapphire's privacy features rather than exposing all contract inputs and state publicly.

ROFL extends the model to off-chain applications. A ROFL app runs on Oasis nodes inside a TEE, packaged either as a container or executable, with SGX/TDX-based privacy and integrity, auditable updates, a built-in key-management service, and permissionless registration/management including billing. Sapphire smart contracts can verify ROFL transaction origin, allowing off-chain computation to return verifiable results without disclosing private inputs. ROSE is the native token used for fees, staking, delegation, governance voting, rewards, and dApp-specific purposes; tokens can move between the consensus ledger and ParaTimes via deposits and withdrawals.

Key facts

  • Native token: ROSE.
  • ROSE is used for proof-of-stake block proposal and validation, governance proposal voting, staking rewards, network gas fees, and dApp-specific use cases.
  • The official token-metrics page states a fixed total cap of 10 billion ROSE and approximately 1.5 billion circulating at mainnet launch; it also describes approximately 2.3 billion tokens reserved for staking rewards.
  • Oasis separates consensus from execution into a consensus layer and parallel ParaTimes.
  • Sapphire is an EVM-compatible confidential ParaTime with encrypted state, confidential randomness, cross-chain bridges, and documented one-block/approximately six-second finality.
  • ROFL apps run inside TEEs managed through the Sapphire blockchain and support Intel SGX/TDX, key management, auditable updates, and permissionless deployment/management.
  • The official Oasis explorer is available at explorer.oasis.io/mainnet, with Sapphire exploration under its Sapphire path.
  • The Oasis Protocol Foundation maintains public implementations including oasis-core, oasis-sdk, sapphire-paratime, wallet, explorer, and cli on GitHub.

Official links

Categories

Related coins

Compare

Frequently asked questions

What is the Oasis Network token?

ROSE is the native Oasis token. It pays gas, supports proof-of-stake validation and delegation, participates in governance, distributes staking rewards, and can serve dApp-specific purposes.

What is the difference between the consensus layer and a ParaTime?

The consensus layer provides shared proof-of-stake consensus and settlement, while a ParaTime is a replicated compute environment with its own execution logic and state. Deposits and withdrawals move ROSE between these ledgers; ordinary transfers occur within one layer or ParaTime.

What is Sapphire?

Sapphire is Oasis's confidential, EVM-compatible ParaTime. It lets EVM developers use encrypted state, confidential randomness, and confidential smart-contract execution, with documented one-block/approximately six-second finality.

What is ROFL?

ROFL (Runtime Off-Chain Logic) is a framework for applications running in Oasis-node TEEs. It provides privacy and integrity, auditable updates, key management, permissionless app deployment/management, and integration with Sapphire for verifying transaction origin.

Does Oasis privacy eliminate all trust assumptions?

No. The design reduces reliance on infrastructure operators through TEEs and attestations, but users still rely on the security of the hardware root of trust, the correctness of deployed code, and application designs that do not intentionally reveal sensitive information.

External trackers

Choose a tracking site for Oasis: