How to Add a Custom Remote Procedure Call (RPC) to OKX Wallet

Remote Procedure Call (RPC) is a protocol that enables your OKX Wallet to communicate with a specific blockchain network. By adding a custom RPC, you can manually connect to unsupported networks (e.g., testnets or custom EVM-compatible chains) not preloaded in the wallet. This feature is especially valuable for developers or users exploring emerging or niche blockchains.

Why Use Custom RPCs?

Custom RPCs allow you to:

Access testnets for development and testing.
Connect to EVM-compatible chains outside OKX Wallet’s default list.
Interact with private networks for enterprise or local deployments.

👉 Learn more about blockchain networks

Step-by-Step Guide to Add a Custom RPC

Via Mobile App

Open the OKX Web3 Wallet app.
Tap the network dropdown menu at the top of the wallet interface.
Select Custom or Add Network.
Enter the following details:
- Network Name: A descriptive label (e.g., "My Testnet").
- New RPC URL: A valid HTTPS endpoint (e.g., https://rpc.testnet.chain).
- Chain ID: The unique network identifier (e.g., 137 for Polygon).
- Currency Symbol (optional): Native token symbol (e.g., ETH, BNB).
- Block Explorer URL (optional): For transaction tracking.
Click Confirm or Save.

Via Browser Extension

Log in to your OKX Wallet extension.
Click the network selector (e.g., Ethereum, BNB Chain).
Choose Add Network.
Fill in the same details as above.
Select Save or Add.

Your custom RPC network will now appear in the network list.

Best Practices

Verify RPC Sources: Only use endpoints from trusted providers.
Double-Check Chain IDs: Incorrect IDs may disrupt wallet functionality.
Edit/Remove Networks: Manage custom networks anytime via wallet settings.

👉 Troubleshoot RPC issues

FAQs

1. What happens if my RPC endpoint goes offline?

Your wallet won’t sync with the blockchain until the endpoint is restored. Always use reliable providers or fallback URLs.

2. Can I add multiple custom RPCs?

Yes! OKX Wallet supports multiple custom networks. Repeat the steps for each new RPC.

3. Are custom RPCs secure?

Security depends on the endpoint provider. Avoid public RPCs with rate limits or untrusted origins.

4. Why isn’t my custom network working?

Ensure:

The RPC URL is HTTPS (not HTTP).
The Chain ID matches the network’s official documentation.

Final Notes

For unresolved issues, consult the blockchain’s official documentation or contact OKX support.