Skip to main content
Merkle Street

Protocols, markets, policy, people

Why MetaMask rejects Solana and Bitcoin custom RPCs

Why can’t I add a non-EVM network to MetaMask with a custom RPC? MetaMask checks eth_chainId, so use a compatible Snap or chain-native wallet.

Merkle Street Newsroom#aeb30e4 min read

Why MetaMask rejects Solana and Bitcoin custom RPCs

MetaMask’s custom network form rejects Solana or Bitcoin RPCs because it checks for the Ethereum JSON-RPC method eth_chainId. Those chains use different APIs, so their nodes cannot answer that check in the format MetaMask expects.

Why can’t I add a non-EVM network to MetaMask with a custom RPC?

MetaMask uses the custom network form for Ethereum Virtual Machine (EVM) networks. When you submit an RPC endpoint, MetaMask asks it for eth_chainId, which identifies the EVM chain. If the call fails or the node returns “method not found,” MetaMask refuses the network.

Think of eth_chainId as a required handshake: the wallet needs the endpoint to speak the expected protocol before it can connect. A Solana or Bitcoin RPC may be working correctly for its own chain, but it does not implement that Ethereum JSON-RPC method.

Does Chainlist list non-EVM chains?

No. Chainlist lists EVM networks and their chain IDs, RPC endpoints, native currencies and related details. Its data comes from the ethereum-lists/chains registry, which covers EVM networks.

For more on which networks fit this EVM setup and why, Chainlist covers the EVM network directory and the information it provides. Using an endpoint from Chainlist can help you add a supported EVM network, but it cannot make a Solana or Bitcoin RPC compatible with MetaMask’s network form.

Why can’t an EVM account sign for Solana or Bitcoin?

EVM and non-EVM chains can use different key curves, derivation paths and address formats. Ethereum accounts use secp256k1 keys and 0x-prefixed hexadecimal addresses; Solana uses ed25519 keys and base58 addresses.

The address is the visible result of a chain’s account rules, while the key and derivation path determine how the wallet creates and uses that account. An EVM account therefore cannot simply sign Solana transactions because you entered a Solana RPC. The wallet needs an account system that supports Solana’s format and signing rules.

What is a MetaMask Snap?

A MetaMask Snap is an extension that adds capabilities to MetaMask, including support for certain non-EVM chains. A compatible Snap can provide the chain-specific account and transaction handling that the EVM network form lacks.

To use one, find a Snap that supports your target chain and follow its setup steps. The Snap’s support is the key step: adding a regular RPC endpoint alone will not create the right account or teach MetaMask how to sign that chain’s transactions.

How do I reach a non-EVM chain or a mixed chain setup?

Use a wallet with native support for the chain, a compatible MetaMask Snap, or a chain-native wallet. Those routes handle the chain’s own RPC API, keys and addresses. For an EVM network, use an EVM RPC with its own chain ID; Chainlist can help you find the network details.

This distinction also applies within one ecosystem. Avalanche C-Chain is EVM-compatible, so it can be added with its EVM RPC and chain ID. Avalanche X-Chain and P-Chain are not EVM networks, so their RPCs do not pass MetaMask’s EVM network check.

Some non-EVM chains also have an EVM layer. That layer has its own chain ID and EVM-compatible RPC, so add that endpoint to MetaMask rather than the base chain’s RPC. The practical tip: identify whether your target is the base chain or its EVM layer before copying an endpoint; it spares you from troubleshooting a valid RPC that speaks the wrong protocol.

What should I know before using another chain?

How do I move tokens from an EVM chain to Solana?

Use a bridge that supports both the source EVM network and Solana. The bridge handles the cross-chain transfer; first confirm the destination token and Solana account are supported.

Is Tron compatible with MetaMask?

Tron’s base network is not an EVM network, so its RPC does not work in MetaMask’s custom network form. Use a Tron-compatible wallet or another supported integration.

Are Snaps safe to install?

Review a Snap’s publisher, permissions and reputation before installing it. A Snap can add wallet capabilities, so only install one you trust and understand.

Can a hardware wallet sign for both EVM and non-EVM chains?

Some hardware wallets support multiple chain types, but support depends on the device, wallet software and chain. Confirm that the full setup supports the target chain’s account format and transaction signing.