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

Adding a custom Remote Procedure Call (RPC) to your OKX Wallet unlocks access to blockchain networks that aren't pre-configured in the wallet by default. Whether you're exploring niche EVM-compatible chains, testnets, or private networks, understanding how to manually configure these connections is essential for developers and advanced Web3 users alike.

This guide walks you through the step-by-step process of adding a custom RPC endpoint to OKX Wallet—both on mobile and browser extension versions—while ensuring security, accuracy, and seamless integration with emerging blockchain ecosystems.

👉 Discover how to connect to any EVM-compatible network in seconds.

What Is a Remote Procedure Call (RPC)?

RPC stands for Remote Procedure Call, a protocol that enables your OKX Wallet to communicate with a specific blockchain network. In simple terms, it acts as a bridge between your wallet interface and the underlying blockchain, allowing you to send transactions, check balances, and interact with decentralized applications (dApps).

While major networks like Ethereum, BNB Chain, and Polygon are integrated by default, many emerging or specialized blockchains require manual setup via a custom RPC configuration.

Why Add a Custom RPC?

There are several scenarios where adding a custom RPC becomes necessary:

Accessing testnets: Developers often need to test dApps on staging environments like Goerli, Sepolia, or project-specific testnets.
Using niche EVM-compatible chains: New blockchains may not yet be supported natively in OKX Wallet.
Connecting to private or enterprise blockchains: Organizations may run internal chains requiring secure, direct RPC access.
Bypassing limited native support: Some Layer 2 solutions or sidechains aren’t auto-detected during dApp interactions.

By configuring a custom RPC, you gain full control over which networks your wallet connects to—expanding your Web3 exploration beyond mainstream options.

How to Add a Custom RPC in the OKX Mobile App

Follow these steps to manually add a new network via custom RPC on the OKX Wallet mobile application:

Open the OKX Web3 Wallet app on your smartphone.
Tap the network dropdown menu located at the top of the wallet screen.
Select "Custom" or "Add Network" from the list of available networks.
Enter the required network details:
- Network Name: Assign a recognizable name (e.g., “Manta Testnet”).
- RPC URL: Input the HTTPS-based RPC endpoint provided by the blockchain team or service (e.g., https://pacific-rpc.manta.network/http).
- Chain ID: The unique numeric identifier for the blockchain (e.g., 169 for Manta Pacific).
- Currency Symbol (optional): Specify the native token symbol (e.g., MNT, ETH).
- Block Explorer URL (optional): Add a link to view transaction history (e.g., https://pacific-explorer.manta.network).
Tap "Confirm" or "Save" to complete the setup.

Once saved, the new network will appear in your network list and can be selected anytime you wish to interact with it.

👉 Learn how developers use custom RPCs to build next-gen dApps.

How to Add a Custom RPC in the OKX Browser Extension

The process is similarly straightforward when using the OKX Wallet browser extension:

Log in to your OKX Wallet extension.
Click the network switcher usually displayed at the top of the wallet interface (e.g., showing "Ethereum," "BNB Chain").
Choose "Add Network" from the dropdown menu.
Fill in the following fields:
- Network Name: Give your network a clear label (e.g., “Arbitrum Nova”).
- New RPC URL: Enter a valid HTTPS RPC endpoint (avoid HTTP for security reasons).
- Chain ID: Insert the correct chain ID (you can verify this on resources like Chainlist or the official blockchain documentation).
- Currency Symbol: Optional, but helpful for clarity (e.g., “ETH”).
- Block Explorer URL: Optional; enables transaction tracking directly from the wallet.
Click "Save" or "Add".

Your custom network is now active and ready for use. You can switch to it instantly when connecting to dApps or sending assets.

Best Practices for Secure RPC Configuration

While adding a custom RPC is simple, incorrect settings or untrusted endpoints can lead to issues:

✅ Use reliable RPC providers: Stick to official sources such as Alchemy, Infura, or the blockchain’s own public nodes.
❌ Avoid unknown or HTTP endpoints: Unencrypted connections pose security risks and could expose sensitive data.
🔢 Double-check Chain IDs: A mismatched Chain ID can result in failed transactions or lost funds.
🛠️ Test with small amounts first: Before deploying assets or interacting with dApps, verify functionality using minimal value transfers.

Additionally, always refer to the official documentation of the blockchain you're integrating. Reputable projects publish verified RPC URLs and Chain IDs on their websites or GitHub repositories.

Managing Custom Networks

After adding a custom RPC, you can manage it anytime:

Edit network details if updates are released.
Remove unused or outdated networks to keep your interface clean.
Switch between networks seamlessly while browsing dApps.

These settings are accessible under the Network Settings or Connected Chains section in both mobile and extension versions.

Frequently Asked Questions (FAQ)

Q: Can I add non-EVM blockchains via custom RPC?
A: No. Custom RPC configuration only works with EVM-compatible blockchains. Non-EVM chains like Solana or Bitcoin cannot be added this way.

Q: What happens if I enter the wrong RPC URL?
A: Your wallet won’t be able to connect to the network, leading to loading errors or failed transactions. Always verify the URL from trusted sources.

Q: Are there rate limits on custom RPC endpoints?
A: Yes. Public RPCs may throttle requests under heavy usage. For development or production apps, consider using premium node services.

Q: Can I import tokens after adding a custom network?
A: Absolutely. Once the network is set up, you can manually add tokens by entering their contract address, symbol, and decimals.

Q: Will my custom networks sync across devices?
A: Not automatically. You’ll need to reconfigure them separately on each device unless using a synced account system.

Q: Is there a limit to how many custom RPCs I can add?
A: There’s no strict limit, but keeping the list manageable improves usability and reduces confusion.

Final Thoughts

Adding a custom RPC to OKX Wallet empowers you to explore the broader Web3 landscape—from experimental testnets to cutting-edge Layer 2 solutions. With precise configuration and attention to detail, you can securely connect to virtually any EVM-compatible blockchain.

Whether you're building, testing, or simply exploring decentralized ecosystems, mastering this skill enhances your autonomy and flexibility in navigating the future of digital ownership.

👉 Start connecting to new blockchains today—effortlessly and securely.