Understanding Custom RPC in Web3 Wallets
RPC (Remote Procedure Call) is a protocol that enables your OKX Wallet to communicate with specific blockchain networks. By adding a custom RPC, you can manually connect to various networks—such as testnets or custom EVM-compatible chains—that aren't preloaded in the wallet. This feature is particularly valuable for developers and users exploring emerging or niche blockchains.
Why Use Custom RPCs?
- Access testnets for development and testing
- Connect to EVM-compatible chains not natively supported
- Join private or enterprise blockchains
- Explore new or experimental networks
👉 Learn how to optimize your Web3 experience with OKX Wallet
Step-by-Step Guide to Adding Custom RPC
For Mobile App Users
- Open the OKX Web3 Wallet app
- Tap the network dropdown at the top of your wallet interface
- Select "Customize" or "Add Network"
- Enter the required network details (see specifications below)
- Confirm by tapping "Save"
For Browser Extension Users
- Log in to your OKX Wallet extension
- Click the network selector (typically displays "Ethereum" or "BNB Chain")
- Choose "Add Network"
Provide these essential parameters:
- Network Name: A descriptive label (e.g., "Arbitrum Testnet")
- RPC Endpoint: A valid HTTPS URL (obtained from the chain's documentation)
- Chain ID: Unique network identifier (e.g., 42161 for Arbitrum One)
- Currency Symbol (optional): Native token abbreviation (e.g., ETH)
- Block Explorer URL (optional): For transaction tracking
- Click "Save" to activate your custom connection
Key Specifications for Custom RPCs
| Parameter | Example Value | Notes |
|---|---|---|
| Network Name | Polygon Mumbai | User-defined label |
| RPC URL | https://rpc-mumbai.maticvigil.com | Must use HTTPS |
| Chain ID | 80001 | Cross-reference official docs |
| Currency Symbol | MATIC | Optional but recommended |
| Block Explorer | https://mumbai.polygonscan.com | Helps track transactions |
Security Best Practices
- Verify RPC URLs from official documentation to prevent phishing
- Double-check Chain IDs—incorrect values may cause failed transactions
- Custom networks can be edited or removed anytime via wallet settings
- When testing new chains, start with small transactions to verify functionality
👉 Explore advanced Web3 wallet features with OKX
FAQs About Custom RPC Configuration
Why isn't my custom RPC connection working?
Common issues include:
- Invalid HTTPS URL (must use secure protocol)
- Incorrect Chain ID (verify with the network's documentation)
- Temporary RPC endpoint downtime
Can I add multiple custom RPCs?
Yes, OKX Wallet supports unlimited custom networks, each requiring unique Chain IDs.
Is there a risk to using custom RPCs?
Only if endpoints are from unverified sources. Always use:
- Official documentation
- Community-recommended providers
- Enterprise-grade RPC services like Infura or Alchemy
Troubleshooting Tips
If you encounter issues:
- Cross-check parameters with the network's official documentation
- Try alternative RPC endpoints from trusted providers
Contact OKX Support with:
- Screenshots of error messages
- Exact steps taken before the error occurred
- Network details you attempted to add
For more Web3 wallet guides, visit our educational resources.