Paper identity: The Oasis Blockchain Platform, a 2020 technical report by Oasis Protocol Project. This page summarizes the paper’s proposed architecture and distinguishes it from later network deployments.
What the Paper Proposes
The report describes a blockchain platform that separates consensus from application execution. Its aim is to let different applications use execution environments with different performance and confidentiality requirements while sharing a consensus layer. It is an architectural proposal; the authors explicitly do not present it as a description of one particular deployed blockchain network.
Consensus and ParaTimes
The consensus layer orders and finalizes transactions for the network. ParaTimes are separate execution environments that run application logic and can make different choices about virtual machines, validation, and privacy. The separation is intended to let applications evolve without making every execution choice part of one shared runtime.
These layers also have distinct responsibilities for assets and execution. A paper summary should not imply that every ParaTime has the same rules, confidentiality properties, or compatibility. Those properties depend on the specific runtime and its implementation.
Confidential Computing and Its Limits
The report discusses using trusted execution environments (TEEs) such as Intel SGX for confidential computation. A TEE can protect data while code runs inside a hardware-isolated enclave, but this is a hardware-assisted security model. It depends on the processor, firmware, attestation, software implementation, and the threat assumptions of the application. It is not equivalent to a zero-knowledge proof and does not make every transaction or network activity private.
Applications that use confidential execution still need to assess what data enters and leaves an enclave, what observers can learn from public transactions, and how hardware or implementation weaknesses would affect their users.
Later Oasis Network Implementations
The current Oasis documentation describes specific ParaTimes that were developed after the 2020 report. It identifies Sapphire and Cipher as confidential ParaTimes and Emerald as a non-confidential, EVM-compatible ParaTime. These are current implementation details; they should not be attributed to the 2020 report as though the paper described those deployed networks in their present form.
Oasis also separates its consensus layer from ParaTime execution when describing token movement and network operation. Readers should consult the current documentation for present-day runtime and asset behavior, since deployments can change after a paper is published.
What the Paper Does Not Establish
- It is not a current specification for every Oasis deployment.
- It does not claim that all ParaTimes are confidential.
- A TEE does not by itself hide public ledger activity or remove hardware trust assumptions.
Related Terms
See Also
- Ethereum MEV Explained: Transaction Ordering, Block Builders, and User Risks
- What Do Zero-Knowledge Proofs Actually Guarantee in Blockchain?
- Why Can an Audited Smart Contract Still Be Exploited?
Sources
- The Oasis Blockchain Platform (2020 technical report) — Primary source for the proposed architecture, authorship, date, and the paper’s scope.
- Oasis Papers — Official index identifying the 2020 document as The Oasis Blockchain Platform by Oasis Protocol Project.
- Consensus Layer and Other ParaTimes — Current documentation for Emerald, Sapphire, and Cipher runtime classifications.
- Manage your Tokens — Current guide to the relationship between consensus-layer assets and ParaTime execution.