Skip to main content

Consensus network information

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). 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
Oasisgrpc.oasis.io:443testnet.grpc.oasis.io:443

Block Explorers

Name (Provider)Mainnet URLTestnet URL
Oasis Explorer (Oasis)https://explorer.oasis.io/mainnet/consensushttps://explorer.oasis.io/testnet/consensus
Oasis Scan (Bit Cat)https://www.oasisscan.comhttps://testnet.oasisscan.com

Indexers

Name (Provider)Mainnet URLTestnet URLDocumentation
Oasis Nexus (Oasis)https://nexus.oasis.io/v1https://testnet.nexus.oasis.io/v1API
Oasis Scan (Bit Cat)https://api.oasisscan.com/v2/mainnethttps://api.oasisscan.com/v2/testnetAPI

Rosetta Endpoints

ProviderMainnet URLTestnet URL
Oasishttps://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.