Skip to content

Network Overview

Use these endpoints and identifiers to point your DApp at D9 Mainnet, then store them in your Environment Configuration.

Item Value
Chain name D9 Mainnet
WalletConnect project ID d9-wallet-public
Wallet app link scheme d9wallet
Genesis hash 0xc3140da27f348abd94a638e9ca7ee7e9005caf5f2b451044c9487905ea5e0991
Service Endpoint
Chain RPC wss://rpc-hermes.d9network.com
wss://rpc-mercury.d9network.com
wss://rpc-stentor.d9network.com
WalletConnect Relay wss://relay.d9network.com
Indexer API https://indexer.d9network.com/v1
Block explorer https://explorer.d9network.com
Wallet service https://wallet.d9network.com
  • If one RPC endpoint is unreachable, switch to another. All three connect to the same mainnet cluster.
  • Public RPC endpoints expose safe methods only and enforce per-IP rate limits. Prefer WebSocket subscriptions over polling.
Identifier Value Purpose
Genesis hash 32-byte hash above Verifies the target chain and is required in every transaction signer payload
WalletConnect protocol chain ID d9net:000000000000000000000000000000d9 Routes wallet-protocol messages only; not an EVM chain ID or truncated genesis hash

Never use these two values interchangeably. A successful WalletConnect pairing does not confirm that your RPC endpoint serves D9 Mainnet—always complete RPC Verification.

To deploy and register a validator, see Deploy a Validator Node.