Skip to main content

Create dApp

Oasis architectural design including ParaTime and consensus layers

The Oasis architecture is designed to have a simple, robust consensus layer on top which connects handful of ParaTimes executing smart contracts. DApp developers may choose among those ParaTimes depending on whether they require confidentiality and/or EVM-compatibility.

Learn more by exploring the ParaTimes below!

EVM-compatibleOasis Wasm
Confidential

🗃️ Sapphire

12 items

🗃️ Cipher

4 items

Non-Confidential

🗃️ Emerald

2 items

In addition to building fully native dApps running on one of the Oasis ParaTimes, you can also add privacy to your existing dApps running on other, non-confidential chains, and only use Oasis as a privacy service.

The Oasis team prepared a rich cross-chain toolkit called the Oasis Privacy Layer. It consists of solidity precompiles integrating bridges and wrapping the OpenZeppelin ERC2771 contract on top of Sapphire, demonstrates best practices for writing confidential smart contracts and working examples for you to explore and extend.

🗃️ Oasis Privacy Layer

6 items

Consensus Layer RPC Endpoints

danger

The RPC endpoint is a point of trust. Beside rate limiting, it can also perform censorship or even man-in-the-middle attack. If you have security considerations, we strongly recommend that you run your own client node,

Most dApp developers will build dApps on the ParaTime layer (the compute layer) depicted above. For Sapphire and Emerald which are EVM-compatible chains, those dApps connect directly to an EVM-compatible Web3 endpoint. However, if you are building a dApp for Cipher or the one that needs to perform consensus operations such as the consensus-layer token transfers, governance transactions, cross-chain ParaTime deposits and withdrawals and similar, you will need to connect to the one of the endpoints speaking Oasis gRPC.

Public gRPC endpoints (in alphabetic order):

ProviderMainnet URLTestnet URL
Oasis Protocol Foundationgrpc.oasis.io:443testnet.grpc.oasis.io:443

Consensus Layer Block Explorers

Name (Provider)Mainnet URLTestnet URL
Oasis Scan (Bit Cat)https://www.oasisscan.comhttps://testnet.oasisscan.com
Oasis Explorer (Oasis Protocol Foundation)Coming soonComing soon

Consensus Layer Indexers

Name (Provider)Mainnet URLTestnet URLDocumentation
Oasis Scan (Bit Cat)https://api.oasisscan.com/mainnet/v2https://api.oasisscan.com/testnet/v2Mainnet API, Testnet API
Oasis Nexus (Oasis Protocol Foundation)https://nexus.oasis.io/v1https://testnet.nexus.oasis.io/v1API

Rosetta Endpoints

ProviderMainnet URLTestnet URL
Oasis Protocol Foundationhttps://rosetta.oasis.io/api/mainnet/v1https://rosetta.oasis.io/api/testnet/v1
note

If you are running your own Oasis client node endpoint, a block explorer, an indexer, or the Rosetta gateway and wish to be added to these docs, open an issue at github.com/oasisprotocol/docs.

See also