Oasis

In 2018, UC Berkeley professor Dawn Song co-founded Oasis Labs. Berkeley’s account connects the company directly to her privacy-preserving computation research and names Raymond Cheng and Noah Johnson among the early team. The project began with a computer-security problem before it became a token network: infrastructure operators should not automatically see the data they process.

The proposed answer did not ask one blockchain virtual machine to serve every workload. Oasis separated proof-of-stake consensus from ParaTimes, replicated execution environments with their own rules and ledgers. That division let transparent and confidential computation share settlement without pretending they had identical trust requirements.

Oasis announced Mainnet Beta on October 1, 2020. It was a live network, but the later upgrade was the sharper economic boundary. On November 18 at 16:00 UTC, community node operators moved to chain oasis-1, enabled ROSE transfers and activated the reward schedule. The two dates describe successive states, not competing launch claims.

ROSE entered with a fixed 10 billion cap and about 1.5 billion circulating. The full approximate allocation put 23.5% into staking rewards, 23% with backers, 20% with core contributors, 18.5% into community and ecosystem programs, 10% in the Foundation endowment and 5% with strategic partners and reserve. Those buckets explain who could finance security and development, while the official page warns that allocations were approximate and subject to change.

Sapphire’s chronology has three distinct steps. Testnet opened on 21 July 2022; Sapphire 0.3.0 reached mainnet on 16 December. At the Oasis Rendezvous on 19 July 2023, the Foundation launched Oasis Privacy Layer as a bridge-and-relayer framework through which applications on other EVM chains could call Sapphire.

Sapphire offers encrypted state, calls and confidential randomness, but only inside that ParaTime and only when applications use the features correctly. Testnet data should be treated as public. A public RPC can censor or intercept requests; contracts cannot know whether calldata arrived encrypted; and timing, gas, storage size or access patterns can leak clues.

Inside Sapphire, trusted execution hardware isolates contract work from the host. Remote attestation lets participants check which runtime is in the enclave. Yet the platform paper leaves residual trust visible: the key manager has an enclave component and an external component, and the latter is trusted not to perform rollback or side-channel attacks. Hardware flaws, unsafe upgrades or unavailable key-manager nodes are operational assumptions, not details erased by encryption.

ROFL extended the pattern beyond contracts and officially reached mainnet on 2 July 2025. A registered bundle runs in a node-hosted enclave, obtains an attested identity and application-scoped secrets, and can send transactions that Sapphire recognizes. This proves which registered code environment handled a result. HTTPS can authenticate a remote server, but neither attestation nor TLS proves that a price feed, sensor, model output or human statement is true, fresh or available.

ROSE pays consensus gas and supports staking, delegation and rewards. Governance is more layered than the label suggests. Proposals and architecture decisions can begin in public issues and ADRs; unresolved design work can be decided by project committers. Network votes are conducted by eligible stake-backed entities or validators, not by every passive balance clicking a ballot.

Even an approved upgrade becomes real only when node operators install the software and the network reaches the required support. The Foundation also directs its own delegations under a published policy. ROSE therefore coordinates security and decisions, but control is distributed across delegated stake, validator votes, maintainers, Foundation resources and the operators who run each runtime.