Skip to main content

Connect to Neon RPC

TL;DR​

RPC endpoints are available on Chainlist.

Introduction​

This tutorial explains how to connect to a Neon RPC via Chainlist. You may connect an EVM-compatible wallet to a network and accept the default Proxy. Alternatively, you can manually set up your Proxy Operator.

The Proxy Operator you choose is responsible for settling your Neon transactions on Solana. Chainlist will assign a default, but you can edit this later.

Connect via Chainlist​

To connect an EVM-compatible wallet such as MetaMask to Neon EVM:

1.1 Visit Neon's Chainlist page.

1.2 Click "Connect Wallet"

With most wallets, simply click "Approve" to connect your wallet.

Chainlist assigns their default Proxy; you can reconfigure this.

Choose a remote Proxy​

Before sending a transaction to the Neon EVM, users should choose the Operator that's optimal for them to perform transactions.

Selecting the RPC address an Operator provides assigns your transactions to that Operator.

One Proxy may be available on different networks (i.e. Devnet and Mainnet). The Proxy interacts with one EVM loader, which can be deployed in different Solana chains.

To view the available RPC endpoints, expand the card details of the network of your choice.

Notice that if several Proxy Operators offer public RPC endpoints, you have a choice over who to use.

If your chosen Proxy Operator isn't the default provided during the wallet connection step, you will need to connect manually.

Connect manually​

The preceding steps demonstrate how to connect to a Solana cluster via Chainlist. Alternatively, you can connect to the Neon EVM manually or edit your choice of Proxy. While steps may differ slightly according to your EVM-compatible wallet, the principles will closely match the tutorial on connecting manually via MetaMask.

Connect dev tools to Neon EVM​

To connect to a Proxy check out the following resources:

Please note that, for Hardhat, you need to set up the configuration file by setting the URL and the network_id/chainId to the RPC URL (and ID) selected from Chainlist. This is described in detail in the relevant tutorial sections.

Gotchas​

Should the main "Connect Wallet" button not function, use the dropdown and use the "Connect Wallet" for a specified RPC server address.

What next?​

If you wish to transact via your RPC, then checkout the supported RPC API methods.

Was this page helpful?