Create dApp
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-compatible | Oasis Wasm | |
|---|---|---|
| Confidential | 🗃️ Sapphire12 items | 🗃️ Cipher5 items |
| Non-Confidential | 🗃️ Emerald2 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
2 items
Consensus Layer RPC Endpoints
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):
| Provider | Mainnet URL | Testnet URL |
|---|---|---|
| Oasis Protocol Foundation | grpc.oasis.io:443 | testnet.grpc.oasis.io:443 |
Consensus Layer Block Explorers
| Name (Provider) | Mainnet URL | Testnet URL |
|---|---|---|
| Oasis Scan (Bit Cat) | https://www.oasisscan.com | https://testnet.oasisscan.com |
| Oasis Explorer (Oasis Protocol Foundation) | Coming soon | Coming soon |
Consensus Layer Indexers
| Name (Provider) | Mainnet URL | Testnet URL | Documentation |
|---|---|---|---|
| Oasis Scan (Bit Cat) | https://api.oasisscan.com/mainnet/v2 | https://api.oasisscan.com/testnet/v2 | Mainnet API, Testnet API |
| Oasis Nexus (Oasis Protocol Foundation) | https://nexus.oasis.io/v1 | https://testnet.nexus.oasis.io/v1 | API |
Rosetta Endpoints
| Provider | Mainnet URL | Testnet URL |
|---|---|---|
| Oasis Protocol Foundation | https://rosetta.oasis.io/api/mainnet/v1 | https://rosetta.oasis.io/api/testnet/v1 |
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.