What is the Oasis Sapphire mainnet RPC URL?

Oasis Sapphire's listed primary public RPC URL is https://sapphire.oasis.io.

What is Oasis Sapphire's chain ID?

Oasis Sapphire's listed chain ID is 23294.

What block explorer does Oasis Sapphire use?

Oasis Sapphire's listed block explorer is https://explorer.oasis.io/mainnet/sapphire.

What gas token does Oasis Sapphire use?

Oasis Sapphire's listed gas token is ROSE.

Chain profile

Oasis Sapphire chain ID 23294 and mainnet RPC URL

Source snapshotJuly 4, 2026

Source evidence snapshot July 4, 2026. Oasis documentation lists Sapphire mainnet with chain ID 23294, public Web3 gateway RPC URLs, ROSE gas token context, and Oasis Explorer.

Quick settings

Oasis Sapphire RPC status and chain ID answer

Oasis Sapphire mainnet uses chain ID 23294 / 0x5afe, RPC URL https://sapphire.oasis.io, explorer https://explorer.oasis.io/mainnet/sapphire, and ROSE as the gas token. Use the latest source check and linked docs to verify the fields before adding the network to a wallet, script, or app.

Chain ID: 23294 / 0x5afe
RPC URL: https://sapphire.oasis.io
Explorer: https://explorer.oasis.io/mainnet/sapphire
Gas token: ROSE
Source docs: Oasis docs
Latest check: Jul 20, 2026
Source snapshot: July 4, 2026
Config path: wallet_addEthereumChain JSON

Copy Oasis Sapphire config Open source docs Explorer directory Gas token directory

Good fit when you need:

the Oasis Sapphire chain ID, RPC URL, explorer, and gas token in one place;
source documentation links beside the copied setup fields;
manual wallet config fields without connecting a wallet or choosing an RPC provider.

Before you paste these fields:

compare the chain ID against the source link on this page;
open the explorer once and confirm it matches the network you expect;
use the public RPC for setup checks, then choose monitored infrastructure for production traffic.

Chain ID23294 / 0x5afe

RPC URLhttps://sapphire.oasis.io

Explorerhttps://explorer.oasis.io/mainnet/sapphire

Gas tokenROSE

VerificationVerified metadata

Source snapshotJuly 4, 2026

Evidence snapshotJul 20, 2026

Verification record

Automated source snapshots and recorded probe evidence are tracked separately. The source snapshot timestamp is not a manual review date. This is not a live uptime, latency, or production reliability monitor. If a recorded public RPC probe fails, verify the source links and current endpoint availability before changing production configuration.

Automated source snapshot: July 4, 2026
Verification status: Verified metadata
Source snapshot run: source-monitoring-2026-07-04
Source snapshot tool: source-monitoring-refresh
Source set: Oasis docs
Latest recorded chain ID probe: eth_chainId matched expected 0x5afe; observed 0x5afe on Jul 20, 2026

Methodology Report a correction

Oasis Sapphire wallet-add fields

Wallet directory sites often expose a connect button. Main.net keeps the same MetaMask and EIP-3085 setup fields as text so developers can compare them with official/source docs before calling wallet_addEthereumChain.

chainId: 0x5afe (23294)
chainName: Oasis Sapphire
nativeCurrency: ROSE; name ROSE, symbol ROSE, decimals 18
rpcUrls: https://sapphire.oasis.io
blockExplorerUrls: https://explorer.oasis.io/mainnet/sapphire

GlossaryChain IDHow wallet and RPC software identify a mainnet network.GlossaryRPC endpointWhat an RPC URL does and why public endpoints can be rate-limited.GlossaryMainnetThe production network context for these chain settings.Gas tokenROSE gas tokenOther mainnet rows that use ROSE for gas.Network categoryEVM mainnetsCompare Oasis Sapphire with related evm mainnets by chain ID, RPC URL, explorer, and source links.GuideChain ID listChain IDs, RPC URLs, explorers, and source links across Main.net.

Monitoring evidence

These checks are review signals only. They are not uptime, latency, privacy, or production reliability claims. A source fetch failure or eth_chainId failure can mean a source page or public RPC endpoint was unavailable, changed, or rate-limited during a check. Re-open source links and test current RPC availability before relying on a public endpoint.

Snapshot generated: Jul 20, 2026
Source checks: 2 sources checked
Source changes: 0 changes since the previous source hash snapshot
Source fetch failures: 0
eth_chainId probe: matched expected 0x5afe
Per-source check timing: Included in the monitoring snapshot, not represented as a manual review or page freshness date

View monitoring snapshots orsource change history.

Network endpoints

Primary public RPC: https://sapphire.oasis.io
Explorer: https://explorer.oasis.io/mainnet/sapphire
Official/source documentation: Oasis docs
Chain type: EVM ParaTime mainnet
Chain ID hex: 0x5afe
Source snapshot provenance: source-monitoring-2026-07-04 via source-monitoring-refresh

Oasis Sapphire common questions

What is the Oasis Sapphire mainnet RPC URL?: Oasis Sapphire's listed primary public RPC URL is https://sapphire.oasis.io.
What is Oasis Sapphire's chain ID?: Oasis Sapphire's listed chain ID is 23294.
What block explorer does Oasis Sapphire use?: Oasis Sapphire's listed block explorer is https://explorer.oasis.io/mainnet/sapphire.
What gas token does Oasis Sapphire use?: Oasis Sapphire's listed gas token is ROSE.

Copy-ready config

Neutral app configuration built from the verified fields above. Copy buttons only place text on your clipboard; they do not connect a wallet, request permissions, or rank RPC providers.

Chain ID decimal23294

Chain ID hex0x5afe

RPC URLhttps://sapphire.oasis.io

Explorer URLhttps://explorer.oasis.io/mainnet/sapphire

EIP-3085-shaped JSON

Rendered as text for manual review before use.

{
  "chainId": "0x5afe",
  "chainName": "Oasis Sapphire",
  "nativeCurrency": {
    "name": "ROSE",
    "symbol": "ROSE",
    "decimals": 18
  },
  "rpcUrls": [
    "https://sapphire.oasis.io"
  ],
  "blockExplorerUrls": [
    "https://explorer.oasis.io/mainnet/sapphire"
  ]
}

Developer snippets

Static examples generated from Main.net fields. These snippets are for manual configuration review and read-only RPC checks; they do not connect wallets, create signers, submit writes, or rank providers.

viem chain definition

Read-only snippet generated from Main.net fields. Review official sources before production use.

import { defineChain } from 'viem'

export const oasisSapphireMainnet = defineChain({
  id: 23294,
  name: "Oasis Sapphire",
  nativeCurrency: {
    name: "ROSE",
    symbol: "ROSE",
    decimals: 18,
  },
  rpcUrls: {
    default: { http: ["https://sapphire.oasis.io"] },
    public: { http: ["https://sapphire.oasis.io"] },
  },
  blockExplorers: {
    default: {
      name: "explorer.oasis.io",
      url: "https://explorer.oasis.io/mainnet/sapphire",
    },
  },
})

wagmi read-only config

Read-only transport example generated from Main.net fields. It does not include account adapters or transaction actions.

import { createConfig, http } from 'wagmi'
import { oasisSapphireMainnet } from './oasis-sapphire'

export const config = createConfig({
  chains: [oasisSapphireMainnet],
  transports: {
    [oasisSapphireMainnet.id]: http("https://sapphire.oasis.io"),
  },
})

ethers read-only provider

Read-only JsonRpcProvider example generated from Main.net fields. It does not create a signer.

import { JsonRpcProvider } from 'ethers'

export const provider = new JsonRpcProvider("https://sapphire.oasis.io", {
  chainId: 23294,
  name: "oasis-sapphire",
})

const network = await provider.getNetwork()
console.log(network.chainId)

bash

curl eth_chainId check

Minimal JSON-RPC identity check. This verifies the endpoint-reported chain ID only, not uptime or production suitability.

curl -s -X POST \
  -H 'content-type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}' \
  https://sapphire.oasis.io

# Expected chain ID: 23294 / 0x5afe

Developer signals

External dashboards a developer may inspect before choosing where to deploy. Main.net links to these references but does not collect the metric values, normalize methodologies, rank chains, or recommend deployments.

explorerOasis Sapphire explorerExplorer-hosted blocks, transactions, contracts, token transfers, and verification tools from the listed explorer.

Main.net links to external developer-signal dashboards but does not collect, normalize, rank, or republish their metric values in this version.
External metrics can use different methodologies and update schedules. Check the linked provider documentation before comparing chains.
These links are not recommendations, rankings, investment advice, or claims that a chain is suitable for a specific application.

Source links

Oasis Sapphire network information Oasis mainnet parameters

Safety note

Oasis documentation warns that public RPC endpoints are points of trust and may be rate-limited, censored, or man-in-the-middle targets. Run dedicated infrastructure for sensitive use.

Main.net is an independent reference site. It does not operate this chain, custody assets, execute transactions, or provide investment advice.

Report a correction

If this page has stale RPC, explorer, chain ID, or source information, open a public correction issue with a source link so it can be checked.

Report Oasis Sapphire data Send page feedback