Start here

Connect to the network

The public network settings for wallets, applications, and integrations.

Network name

Tuven

Chain ID

99359 / 0x1841f

Native currency

USDX · 18 decimals

RPC

https://rpc.tuven.io

Explorer

Tuven Explorer ↗

Use the network configuration below to add Tuven to an EVM wallet. The chain ID identifies Tuven independently of its RPC hostname. Applications should check the chain ID before every transaction.

Add Tuven programmatically

A wallet provider can add Tuven with wallet_addEthereumChain and switch to it with wallet_switchEthereumChain. Both operations require user confirmation in the wallet. Chain IDs in these requests are hexadecimal strings.

await window.ethereum.request({
  method: 'wallet_addEthereumChain',
  params: [{
    chainId: '0x1841f',
    chainName: 'Tuven',
    nativeCurrency: { name: 'USDX', symbol: 'USDX', decimals: 18 },
    rpcUrls: ['https://rpc.tuven.io'],
    blockExplorerUrls: ['https://explorer.tuven.io']
  }]
});
await window.ethereum.request({
  method: 'wallet_switchEthereumChain',
  params: [{ chainId: '0x1841f' }]
});

Check your connection

Call eth_chainId and compare the result to the configured chain ID. Then request the latest block number. A successful HTTP response does not guarantee a successful RPC call: always check for a JSON-RPC error object.

curl 'https://rpc.tuven.io' \
  -H 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'

Availability and finality

Tuven targets one-second blocks and uses Malachite BFT consensus. The target is a configuration parameter, not a latency guarantee. Network availability depends on the validator and RPC infrastructure. The explorer is an indexer and can lag behind the latest RPC state.