Skip to main content

Network Information

This page consolidates every parameter you need to connect to XPHERE from a wallet, dApp, indexer, or backend service.

Mainnet​

FieldValue
Network NameXphere Mainnet
Chain ID (decimal)20250217
Chain ID (hex)0x134fe69
Native Token SymbolXP
Token NameXphere
Decimals18
Block Time~1 second
ConsensusOptimized PBFT (Main Chain) + xpHash PoW (Proof Chain)
HTTPS RPChttps://rpc.x-phere.com (recommended)
https://en-hkg.x-phere.com
https://en-bkk.x-phere.com
https://rpc.ankr.com/xphere_mainnet (Ankr)
WebSocket RPCwss://rpc.x-phere.com/ws (recommended)
wss://en-hkg.x-phere.com/ws
wss://en-bkk.x-phere.com/ws
Block Explorerhttps://xpscan.io (XPScan)
https://xp.tamsa.io (Tamsa Explorer)
xpHash Fork Block1,740,000

Testnet​

FieldValue
Network NameXphere Testnet
Chain ID (decimal)1998991
Chain ID (hex)0x1e808f
Native Token SymbolXPT
Token NameXphere Testnet
Decimals18
HTTPS RPChttps://testnet.x-phere.com
https://rpc.ankr.com/xphere_testnet (Ankr)
WebSocket RPCwss://testnet.x-phere.com/ws/ (note the trailing slash)
Block Explorerhttps://xpt.tamsa.io (Tamsa Testnet Explorer)
Faucethttps://faucet.x-phere.com — 10 XPT per address per 24 h
xpHash Fork Block327,400
The two networks use different native symbols

Mainnet is XP; Testnet is XPT. A wallet configured with XP against Chain ID 1998991 will display the wrong symbol and mislead you about which network you are signing on. Both entries are registered under these symbols in the public chain registry that backs chainlist.org.

Testnet WebSocket path

wss://testnet.x-phere.com/ws answers 301 Moved Permanently to /ws/. Clients that do not follow redirects during the WebSocket handshake must use the trailing-slash form. Mainnet upgrades at /ws directly.

Which Mainnet endpoint to use​

Point production traffic at rpc.x-phere.com. It fronts several Foundation endpoint nodes across regions. Health checks run continuously, and requests move to a healthy node when one stops answering — no client change, no DNS edit on your side.

en-hkg and en-bkk remain available and address single nodes directly. Use them when you need to pin traffic to one region, or to compare two nodes against each other while debugging. Because they are single origins, an outage there is visible to your application; rpc.x-phere.com absorbs it.

All three answer the same JSON-RPC methods over both HTTPS and WebSocket, and are rate limited per client IP. If you run an indexer or any workload that needs sustained high request volume, contact the Foundation rather than spreading load across the hostnames — the limit applies to the underlying nodes either way.

Explorer routing​

NetworkExplorer to useNotes
Mainnetxpscan.io, xp.tamsa.ioEither serves Mainnet blocks, transactions, and addresses
Testnetxpt.tamsa.ioThe only published XPHERE Testnet explorer

XPScan publishes Mainnet data — its own footer states Chain ID: 20250217 — and no XPScan testnet instance is published (https://xpscan.io/testnet returns 404, and testnet.xpscan.io does not resolve). Send Testnet readers to xpt.tamsa.io.

Verifying These Values Yourself​

Every number in the tables above is readable from the live RPC:

# Mainnet → 0x134fe69 (20250217)
curl -s -X POST https://rpc.x-phere.com \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

# Testnet → 0x1e808f (1998991)
curl -s -X POST https://testnet.x-phere.com \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

Always cross-check eth_chainId on the endpoint you are about to use before signing transactions in production.

Connecting from Common Tools​

MetaMask​

See the step-by-step guide: Wallet Setup.

wallet_addEthereumChain​

// Mainnet
await window.ethereum.request({
  method: "wallet_addEthereumChain",
  params: [{
    chainId: "0x134fe69", // 20250217
    chainName: "Xphere Mainnet",
    nativeCurrency: { name: "Xphere", symbol: "XP", decimals: 18 },
    rpcUrls: ["https://rpc.x-phere.com"],
    blockExplorerUrls: ["https://xpscan.io", "https://xp.tamsa.io"],
  }],
});

// Testnet
await window.ethereum.request({
  method: "wallet_addEthereumChain",
  params: [{
    chainId: "0x1e808f", // 1998991
    chainName: "Xphere Testnet",
    nativeCurrency: { name: "Xphere Testnet", symbol: "XPT", decimals: 18 },
    rpcUrls: ["https://testnet.x-phere.com"],
    blockExplorerUrls: ["https://xpt.tamsa.io"],
  }],
});

viem / ethers.js / web3.js​

// viem
import { defineChain } from "viem";

export const xphere = defineChain({
  id: 20250217,
  name: "Xphere Mainnet",
  nativeCurrency: { name: "Xphere", symbol: "XP", decimals: 18 },
  rpcUrls: {
    default: { http: ["https://rpc.x-phere.com"] },
  },
  blockExplorers: {
    default: { name: "Tamsa Explorer", url: "https://xp.tamsa.io" },
  },
});

export const xphereTestnet = defineChain({
  id: 1998991,
  name: "Xphere Testnet",
  testnet: true,
  nativeCurrency: { name: "Xphere Testnet", symbol: "XPT", decimals: 18 },
  rpcUrls: {
    default: { http: ["https://testnet.x-phere.com"] },
  },
  blockExplorers: {
    default: { name: "Tamsa Testnet Explorer", url: "https://xpt.tamsa.io" },
  },
});
// ethers v6
import { JsonRpcProvider, Network } from "ethers";

const mainnet = new JsonRpcProvider(
  "https://rpc.x-phere.com",
  new Network("xphere", 20250217)
);

const testnet = new JsonRpcProvider(
  "https://testnet.x-phere.com",
  new Network("xphere-testnet", 1998991)
);

curl (sanity check)​

# Mainnet
curl -X POST https://rpc.x-phere.com \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

# Testnet
curl -X POST https://testnet.x-phere.com \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

Rate Limits & Reliability​

Public endpoints provided by the XPHERE Foundation are best-effort and may apply per-IP rate limits without prior notice. For production workloads, run your own Endpoint Node or use a dedicated RPC provider.

See Also​