How to Add a Custom RPC Network to OKX Wallet for Accessing New Blockchain Projects?

Understanding Custom RPC Network Integration

1. OKX Wallet supports manual addition of custom blockchain networks via standardized JSON-RPC endpoints, enabling direct interaction with emerging Layer 1 and Layer 2 ecosystems without relying on pre-approved listings.

2. Each custom network requires a unique chain ID, a stable HTTP or HTTPS RPC URL, a block explorer URL for transaction verification, and a native currency symbol with its decimal precision.

3. The wallet validates network parameters during input but does not perform real-time connectivity checks—users must confirm endpoint responsiveness before finalizing the configuration.

4. Once added, the network appears under the “Networks” tab and becomes selectable for sending transactions, deploying contracts, or interacting with dApps hosted on that chain.

5. Network metadata—including icon, name, and explorer link—is stored locally within the wallet’s secure storage and is never transmitted to external servers.

Step-by-Step Configuration Process

1. Open OKX Wallet and navigate to Settings → Networks → Add Network Manually.

2. Enter the chain ID as a decimal or hexadecimal integer matching the target blockchain’s specification—for example, 195 for XLayer or 324 for zkSync Era.

3. Input the full RPC URL including protocol (e.g., https://rpc.xlayer.tech), ensuring it permits CORS requests and returns valid JSON-RPC responses to eth_chainId and eth_blockNumber calls.

4. Specify the block explorer URL using a placeholder for transaction hashes, such as https://www.okx.com/explorer/xlayer/tx/{txHash}, where {txHash} will be dynamically replaced.

5. Set the native token symbol (e.g., OKT) and decimals (typically 18), then save the configuration to activate the network in the wallet interface.

Verification and Troubleshooting

1. After saving, switch to the newly added network and check the displayed balance—if zero but expected, confirm the account has been funded on-chain using an external block explorer.

2. Attempt a test transaction with minimal value; if it stalls or fails, inspect browser developer tools for failed RPC requests indicating timeout, CORS rejection, or invalid response format.

3. A common error “Invalid JSON-RPC response” signals mismatched content-type headers or non-200 HTTP status codes returned by the node provider.

4. If gas estimation fails, verify the RPC endpoint exposes eth_estimateGas and eth_gasPrice methods—some public nodes disable these for rate-limiting reasons.

5. Persistent “Network unreachable” messages suggest DNS resolution failure or TLS certificate misconfiguration on the RPC domain.

Security Considerations for Third-Party Endpoints

1. Never input RPC URLs from unverified social media posts or unofficial documentation—malicious endpoints can intercept signing requests or return forged balances.

2. Prefer providers offering TLS 1.3, certificate pinning, and documented uptime SLAs—examples include Blast API, Chainstack, and OKX’s own XLayer RPC infrastructure.

3. Avoid RPCs that require API keys embedded directly in the wallet configuration, as OKX Wallet does not support dynamic key injection and may expose credentials in plaintext logs.

4. Cross-check the chain ID against official project repositories—spoofed IDs like 137 (Polygon) or 1 (Ethereum Mainnet) are frequently reused in phishing attempts targeting new users.

5. Disable unused custom networks regularly to reduce attack surface; each active network increases the number of potential RPC injection vectors during dApp connections.

Frequently Asked Questions

Q: Can I add a network with a chain ID already used by another blockchain?A: Yes, but doing so risks transaction misrouting if both chains share identical IDs and the wallet cannot distinguish them by endpoint alone. Always verify chain ID uniqueness through official sources.

Q: Why does my custom network show “0x0” as the current block number after adding?A: This indicates the RPC endpoint returned null or empty data for eth_blockNumber. Confirm the node is fully synced and accepts unauthenticated JSON-RPC GET/POST requests.

Q: Is it possible to import a custom network configuration file (e.g., .json) into OKX Wallet?A: No. OKX Wallet does not support bulk import of network definitions. All entries must be added manually through the UI with individual field validation.

Q: Do custom networks support EIP-1559 fee markets?A: Support depends entirely on the underlying RPC provider. If the node implements eth_maxPriorityFeePerGas and related methods, OKX Wallet will display dynamic fee options; otherwise, legacy gas pricing applies.