Adding a custom Remote Procedure Call (RPC) endpoint to your OKX Wallet allows you to connect directly to blockchain networks that aren’t pre-configured in the wallet interface. This is especially useful for developers, early adopters, and users exploring new or niche EVM-compatible chains—such as testnets, private networks, or emerging Layer-1 and Layer-2 solutions.
An RPC acts as a communication bridge between your wallet and a specific blockchain network. It enables your wallet (the client) to send requests to a remote server (a blockchain node), execute actions like sending transactions or querying balances, and receive responses—all without managing complex connection details.
By manually adding a custom RPC, you gain flexibility and access beyond mainstream networks like Ethereum or BNB Chain. Whether you're testing smart contracts on a local development chain or interacting with a newly launched decentralized application (dApp), this feature empowers greater control over your Web3 experience.
👉 Discover how easy it is to connect to any EVM-compatible network with OKX Wallet.
Why Use a Custom RPC Endpoint?
The primary advantage of configuring a custom RPC lies in accessibility and customization. While OKX Wallet supports dozens of popular blockchains by default, countless others—especially testnets or project-specific chains—are not automatically included.
Here’s when a custom RPC becomes essential:
- You're developing or testing dApps on a local or test network (e.g., Hardhat, Ganache, or Goerli).
- You want to interact with a new EVM-compatible chain before it's widely supported.
- You're using a private or consortium blockchain for enterprise or research purposes.
- You prefer using your own node provider for enhanced privacy and reliability.
With manual RPC configuration, you're no longer limited to pre-approved networks. However, accuracy is crucial—incorrect settings can lead to failed transactions or loss of access.
Supported Keywords
Core keywords naturally integrated throughout this guide include:
OKX Wallet, custom RPC, Web3 wallet, EVM-compatible chains, blockchain network, RPC endpoint, add network, and testnet.
These terms reflect high-intent search queries from users seeking technical setup guidance, ensuring strong SEO performance while maintaining natural readability.
How to Add a Custom RPC to OKX Wallet
You can add a custom RPC via either the mobile app or the browser extension. The process is straightforward but requires precise input of network details.
On Mobile App
- Open the OKX Wallet app on your device
- Tap the network selector dropdown at the top of the main screen
- Select "Custom" or "Add Network"
Enter the required network parameters:
- Network Name: A label for easy identification (e.g., “My Local Testnet”)
- RPC URL: The HTTPS endpoint provided by your node service (e.g.,
https://rpc.example-chain.org) - Chain ID: The unique identifier for the blockchain (e.g.,
80001for Polygon Mumbai) - Currency Symbol (optional): Native token symbol (e.g.,
ETH,MATIC) - Block Explorer URL (optional): For viewing transaction history (e.g.,
https://mumbai.polygonscan.com)
- Tap "Confirm" or "Save"
Once saved, the network will appear in your network list and can be selected anytime.
On Browser Extension
- Log in to your OKX Wallet browser extension
- Click the network selector at the top of the wallet interface
- Choose "Add Network" from the dropdown menu
Fill in the following fields carefully:
- Network Name: Assign a descriptive name
- New RPC Endpoint: Must be a valid HTTPS URL (never HTTP)
- Chain ID: Numeric ID; must match the actual chain
- Currency Symbol: Optional but recommended for clarity
- Block Explorer URL: Optional link to view on-chain data
- Click "Save" or "Add"
The new network will now be available for immediate use within the wallet.
👉 Connect to emerging EVM chains securely using a custom RPC in seconds.
Important Notes & Best Practices
Configuring a custom RPC gives you powerful flexibility—but also responsibility. Follow these best practices to avoid issues:
✅ Always verify the RPC URL and Chain ID from official sources (project documentation, GitHub, or community announcements).
✅ Prefer HTTPS endpoints only—avoid unsecured HTTP connections for security reasons.
✅ Test the connection by checking your balance or viewing a known address on the block explorer.
✅ If transactions fail, double-check Chain ID and RPC URL formatting—typos are common causes.
✅ You can edit or remove custom networks later under Network Settings.
Using an incorrect Chain ID may result in transaction failures or even unintended cross-chain swaps if paired with dApps. Similarly, unreliable RPC endpoints can cause slow loading times or dropped requests.
Frequently Asked Questions (FAQ)
Q: What is an RPC in crypto wallets?
A: An RPC (Remote Procedure Call) is a protocol that allows your wallet to communicate with a blockchain node. It sends requests—like checking balances or broadcasting transactions—and receives real-time responses from the network.
Q: Can I add non-EVM blockchains via custom RPC in OKX Wallet?
A: No. OKX Wallet only supports EVM-compatible chains through custom RPC configuration. Non-EVM networks like Solana or Bitcoin cannot be added this way.
Q: Is adding a custom RPC safe?
A: Yes—if you use trusted sources. Only input RPC URLs from reputable providers (like Alchemy, Infura, or official project nodes). Untrusted endpoints could potentially log your activity or return false data.
Q: Why can’t I see my tokens after adding a custom network?
A: Token visibility depends on correct contract address mapping and explorer integration. Ensure the network has been properly configured and check if the token is deployed on that specific chain.
Q: Can I use multiple custom RPCs at once?
A: Yes. You can save multiple custom networks and switch between them freely in the wallet interface.
Q: What should I do if my custom network isn’t working?
A: First, verify all entered details—especially Chain ID and RPC URL. Then test the endpoint in a browser or tool like Postman. If issues persist, consult the blockchain’s official documentation or support channels.
👉 Troubleshoot and connect faster with OKX Wallet’s seamless Web3 integration.
Final Thoughts
Manually adding a custom RPC endpoint unlocks advanced functionality in OKX Wallet, giving you direct access to experimental, private, or newly launched EVM-based blockchains. Whether you're building, testing, or simply exploring decentralized ecosystems, this feature enhances both utility and autonomy.
Just remember: precision matters. Double-check every detail before saving, rely on verified sources, and always prioritize security over convenience.
With OKX Wallet’s intuitive design and robust Web3 support, integrating new networks has never been easier—or more powerful.