Sapphire ParaTime
Sapphire is our official confidential ParaTime providing a smart contract development environment with Ethereum Virtual Machine (EVM) compatibility.
As the official confidential EVM-compatible ParaTime on the Oasis Network, Sapphire allows for:
- Confidential state, end-to-end encryption, confidential randomness
- EVM compatibility
- Easy integration with EVM-based dApps, such as DeFi, NFT, Metaverse and crypto gaming
- Scalability: increased throughput of transactions
- Low-cost: 99%+ lower fees than Ethereum
- 6 second finality (1 block)
- Cross-chain bridge to enable cross-chain interoperability (upcoming)
If you are not bound to EVM and you wish to develop dApps with more fine-grained confidentiality, check out the Cipher ParaTime.
Chain Information
Mainnet
- Network name:
sapphire
- Long network name:
Oasis Sapphire
- Chain ID:
- Hex:
0x5afe
- Decimal:
23294
- Hex:
Testnet
- Network name:
sapphire-testnet
- Long network name:
Oasis Sapphire Testnet
- Chain ID:
- Hex:
0x5aff
- Decimal:
23295
- Hex:
RPC Endpoints
The RPC endpoint is a point of trust. Beside traffic rate limiting, it can also perform censorship or even a man-in-the-middle attack. If you have security considerations, we strongly recommend that you set up your own ParaTime client node and the Web3-compatible gateway.
You can connect to one of the public Web3 gateways below (in alphabetic order):
Provider | Mainnet RPC URLs | Testnet RPC URLs | Supports Confidential Queries |
---|---|---|---|
1RPC | https://1rpc.io/oasis/sapphire | N/A | Yes |
Oasis Protocol Foundation | https://sapphire.oasis.io wss://sapphire.oasis.io/ws | https://testnet.sapphire.oasis.io wss://testnet.sapphire.oasis.io/ws | Yes |
Public RPCs may have rate limits or traffic restrictions. For professional, dedicated RPC endpoints, consider the following providers (in alphabetic order):
Provider | Instructions | Pricing | Supports Confidential Queries |
---|---|---|---|
1RPC | docs.1rpc.io | Pricing | Yes |
Chainstack | docs.chainstack.com | Pricing | Yes |
Block Explorers
Provider | Mainnet URL | Testnet URL | EIP-3091 compatible |
---|---|---|---|
Oasis Protocol Foundation | https://explorer.oasis.io/mainnet/sapphire | https://explorer.oasis.io/testnet/sapphire | Yes |
If you are running your own Sapphire endpoint or a block explorer, and you wish to be added to the public list above, open an issue at github.com/oasisprotocol/docs.
See also
🗃️ Manage your Tokens
7 items
📄️ ParaTime Node
These instructions are for setting up a ParaTime node which participates in one or more ParaTime compute committees. If you want to run a ParaTime client node instead, see the instructions for running a ParaTime client node. If you want to run a validator node instead, see the instructions for running a validator node. Similarly, if you want to run a non-validator node instead, see the instructions for running a non-validator node.
📄️ ParaTime Client Node
These instructions are for setting up a ParaTime client node which only observes ParaTime activity and can submit transactions. If you want to run a ParaTime node instead, see the instructions for running a ParaTime node. Similarly, if you want to run a validator or a non-validator node instead, see the instructions for running a validator node or instructions for running a non-validator node.
📄️ Web3 Gateway
Web3 gateway for Emerald and Sapphire ParaTimes
🗃️ Emerald
2 items
🗃️ Cipher
4 items