Chainlist fails to connect your wallet when the browser cannot reach the wallet provider in its page, or that provider cannot answer the account request. The Chainlist directory is a concrete example: its Connect Wallet feature uses that provider while you look up EVM chain IDs and JSON-RPC endpoints. Browser wallets commonly expose a provider as window.ethereum. A connection request calls eth_requestAccounts; adding a network later calls wallet_addEthereumChain. Either request may open a wallet prompt, return an error, or appear to do nothing.
Why Chainlist Connect Wallet Fails
The usual causes are a competing wallet extension, an unfinished wallet prompt, a browser without an injected wallet, or a setting that blocks the wallet on the page. Start with the symptom you can see.
Another Extension Answers the Request
Several wallet extensions can compete to supply window.ethereum. The result is often a prompt in the wrong wallet, even though the wallet you wanted is installed and unlocked. The provider chosen can depend on which extension injects its code last, a conflict described in EIP-6963.
Disable the extra wallet extensions, refresh the page, and try Connect Wallet again. If your wallet offers a default-provider setting, select the wallet you intend to use; Rabby Wallet’s MetaMask toggle is one example of a setting to inspect. Illustrative case: before disabling MetaMask, a Rabby user gets a MetaMask prompt. Afterward, Rabby answers. The account and network details have not changed; the extension receiving the request has.
The Wallet Is Locked or a Prompt Is Still Open
A locked wallet or an earlier unanswered request can hold up the connection. You may see a wallet notification waiting in another browser window, or repeated clicks may produce no new prompt. Open the wallet, unlock it, and approve or reject the request already waiting. Then return to the page and try once more. A rejected request needs a fresh click; it does not grant account access.
The Browser Has No Injected Wallet
A browser without a wallet provider has nothing to answer eth_requestAccounts. This commonly happens when you open the directory in an ordinary phone browser while the wallet lives in a separate app. Open the site inside your wallet’s in-app browser and try there. On a computer, make sure a compatible browser wallet is installed and allowed to run on the site. MetaMask, for instance, recommends its in-app browser for mobile connections.
Browser Settings Block the Wallet
Privacy extensions or strict browser settings can prevent the wallet’s script from reaching the page. A useful clue is that the same unlocked wallet connects elsewhere but produces no prompt here. Allow the wallet extension to run on this site, temporarily relax the relevant blocker for this site, and refresh. If the prompt then appears, restore your other settings one at a time to identify the rule responsible.
If one unlocked wallet still cannot connect in its supported browser after you have cleared pending prompts and extension conflicts, record the exact error and your browser and wallet versions. Contact the wallet’s support when its prompt never opens; report the issue to the directory operator when the wallet works on other sites but this page alone fails.
Keep only the wallet you intend to connect active while testing. That simple step spares you from approving a request in the wrong extension.
Related Network Questions
Why Does Chainlist Say the Network Already Exists?
The wallet may already have that chain ID saved. Compare the chain ID in your wallet with the one you meant to add, then select the existing network. If the JSON-RPC endpoint needs changing, edit the saved network in your wallet where that option is available. The wallet_addEthereumChain specification prevents duplicate entries for the same chain ID.
Can Chainlist Add Networks to a Hardware Wallet?
A hardware wallet usually relies on a compatible browser wallet to manage network settings. Connect the device through that wallet, add the EVM network there, and use the device to approve signing when needed. Whether a particular chain works depends on the device and companion wallet.
Questions After the Wallet Connects
How Do I Remove a Network I Added by Mistake?
Remove the custom network in your wallet’s network settings. This changes the wallet’s saved configuration; it does not move funds or erase activity on the chain. Wallets may keep built-in networks that cannot be removed.
Can I Use Chainlist With WalletConnect Wallets?
The injected-provider connection requires a wallet available to the page. A WalletConnect-only wallet needs a WalletConnect pairing option where one is offered; otherwise, use its in-app browser or enter verified network details manually in the wallet.
Why Does My Wallet Switch Networks After Connecting?
Your wallet may switch after you approve a separate network request. Adding a chain and selecting it are separate actions, so read each wallet prompt before approving. You can select your previous network again in the wallet; switching changes the active network, not where your assets are held.
Top comments (0)