How to Add a Custom RPC URL to a Web3 Wallet

Understanding RPC Endpoints in Web3 Wallets

1. An RPC endpoint serves as the communication gateway between a wallet interface and a blockchain node.

2. Each supported network—Ethereum Mainnet, Polygon, Solana Devnet—requires a dedicated HTTP or HTTPS URL pointing to a live node instance.

3. Wallets like MetaMask, Phantom, and Trust Wallet expose RPC configuration via network settings, allowing manual entry of custom URLs.

4. The RPC URL must conform to JSON-RPC 2.0 specification and respond to standard methods such as eth_blockNumber, eth_getBalance, and eth_call.

5. Misconfigured or unreachable endpoints result in failed transaction broadcasts, inaccurate balance displays, and stalled contract interactions.

Step-by-Step Manual Configuration

1. Open the wallet extension or mobile app and navigate to Settings → Networks → Add Network (or equivalent path).

2. Input the network name, e.g., Base Sepolia, and assign a chain ID such as 84532.

3. Paste the full RPC URL—including protocol, domain, and optional API key—into the designated field; example: https://base-sepolia.infura.io/v3/YOUR_INFURA_KEY.

4. Enter the native currency symbol (e.g., ETH) and its decimal precision (typically 18).

5. Confirm submission; the wallet validates connectivity by issuing a test eth_chainId request before saving the configuration.

Solana-Specific RPC Handling

1. Solana wallets require distinct RPC semantics compared to EVM chains; methods like getBalance and getLatestBlockhash are invoked using solana-kit’s Rpc client rather than legacy Connection objects.

2. AppKit’s Solana adapter now initializes both Connection and Rpc clients simultaneously from the same rpcUrl, ensuring consistency across balance reads and transaction confirmations.

3. When switching networks, the adapter reconstructs both clients using the target chain’s rpcUrls.default.http[0], preventing stale or mismatched RPC states.

4. Developers integrating @reown/appkit-adapter-solana must pin @solana/kit@8.3.0 to guarantee method signature compatibility with the new Rpc interface.

5. Custom Solana RPC URLs must support getFeeForMessage, sendTransaction, and getSignatureStatuses to enable full dApp functionality.

Security Considerations for Custom RPCs

1. Public RPC providers such as Infura, Alchemy, and QuickNode enforce rate limits and API key authentication; omitting credentials exposes requests to throttling or rejection.

2. Self-hosted nodes must restrict CORS headers to trusted origins only; permissive Access-Control-Allow-Origin: * configurations increase exposure to front-running and data leakage.

3. Wallets validate RPC responses against known chain IDs and block hash formats; malformed or inconsistent payloads trigger internal integrity checks and may disable the network entry.

4. Third-party RPC services with unverified uptime histories introduce single points of failure; fallback URLs are not natively supported in most wallet UIs without code-level modifications.

5. RPC endpoints embedded in dApp code—such as those passed to viem’s http() transport—must match the wallet’s configured chain ID to prevent signature mismatches during transaction signing.

Frequently Asked Questions

Q: Can I use the same custom RPC URL across multiple wallet extensions?A: Yes, provided the URL supports cross-origin requests and the wallet enforces no provider-specific restrictions. However, some wallets apply caching or connection pooling that may affect concurrent usage patterns.

Q: Why does my wallet show “Invalid RPC” even when curl returns valid JSON?A: Wallets perform additional validation beyond HTTP status codes—they verify response structure, required fields like jsonrpc version, and correct error code formatting per JSON-RPC 2.0 spec.

Q: Does adding a custom RPC require exposing my private key to the endpoint?A: No. RPC endpoints never receive private keys. Signing occurs locally within the wallet; only signed transactions and read queries are transmitted.

Q: What happens if my custom RPC goes offline after being added?A: The wallet ceases to fetch real-time data and defaults to cached balances or fails transaction submissions with timeout or network unreachable errors.