Oasis Network (ROSE)

Overview

Oasis Network has a consensus layer secured by validators and a ParaTime layer containing separate compute runtimes. ParaTimes can use different execution and confidentiality models while committing results through the shared consensus system.

Sapphire is an EVM-compatible confidential ParaTime, while ROSE is the native asset for consensus fees, staking, delegation, and network operations. Consensus-layer accounts and ParaTime accounts or addresses are different contexts, and moving ROSE between them uses defined deposit or withdrawal workflows. Wallets and exchanges should verify whether a destination belongs to the consensus layer or a specific ParaTime. Integrators must confirm chain, address type, runtime, fee balance, and final execution. Confidentiality claims should be evaluated for the selected ParaTime and its hardware or committee assumptions. Payment support for Oasis Network (ROSE) needs explicit asset and network allowlists, receipt or execution checks, reorganization handling, and recovery procedures. Changes to governance, validators, sequencers, bridges, or client versions can alter risk without changing the public brand.

This prevents later renames, forks, or infrastructure changes from making previous settlement decisions impossible to reproduce. Historical records involving Oasis Network (ROSE) should retain chain identifiers, block hashes, transaction data, and the configuration version used at acceptance time. Oasis Network (ROSE) should be identified by its active mainnet, chain or network identifiers, native fee asset, address rules, and currently supported software. A project name, associated token, testnet, legacy deployment, and bridged representation are different objects and should not be used interchangeably. Operational takeaway: Oasis separates consensus and ParaTime execution, requiring precise handling of ROSE, address context, runtime, transfers, and confidentiality assumptions.