RPC Basics: How Your Wallet Talks to the Blockchain

Every time you check your balance, view your Native Digital Rewards, or send a transaction, your wallet is quietly talking to a blockchain behind the scenes. That conversation happens through something called an RPC. This FAQ explains what an RPC is, why your wallet needs one, and how to use the right one safely. At the bottom of this page you will find the Network RPC Directory, which lists the official network details for each blockchain in our ecosystem.

💡 You do not need to understand RPCs to use your Connect wallet. Your Connect wallet and brand wallets already connect to the right networks for you. This information is most helpful if you use a third-party wallet such as MetaMask, or if you are simply curious about the technical side of how things work, or if you like to do your own research (DYOR) on-chain, etc.

In this article

1. What is an RPC?
2. What is an RPC endpoint (RPC URL)?
3. When does my wallet use an RPC, and why do I need one?
4. What is a Chain ID?
5. What is the difference between a public RPC and a private RPC?
6. How do I add a network to MetaMask?
7. Why is my transaction stuck, or why am I seeing an RPC error?
8. Is it safe to use an RPC? Can an RPC steal my funds?
9. What is the difference between a block explorer and an RPC?
10. What does "EVM-compatible" mean?
11. Network RPC Directory

1. What is an RPC?

RPC stands for Remote Procedure Call. It is the way an app, such as your wallet, asks a blockchain node for information or hands it a transaction to process. Your wallet does not store the whole blockchain on your phone or computer. Instead, it sends questions to a node that does, and the node sends back the answers.

Everyday analogy: Think of an RPC like calling a bank's customer service line. You do not walk into the vault to count your money yourself. You call the line, ask "What is my balance?", and a representative who has access to the records tells you. The RPC is that phone line between your wallet and the blockchain.

Technical details

The blockchains in our ecosystem use JSON-RPC 2.0, the same standard that Ethereum uses. A wallet sends an HTTPS POST request containing a small JSON message that names a method (for example, eth_blockNumber or eth_getBalance), and the node replies with a JSON result.

Example request asking the WIN Blockchain for its latest block number:

curl -X POST https://rpc.mainnet.win.blockfabric.net/ \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

Example response:

{"jsonrpc":"2.0","id":1,"result":"0x20a305"}

The result is written in hexadecimal. 0x20a305 equals block number 2,138,885 in regular numbers. Your result will be higher, because the WIN Blockchain adds a new block roughly every 12 seconds.

2. What is an RPC endpoint (RPC URL)?

An RPC endpoint is the web address your wallet uses to reach a blockchain node. It usually looks like a normal website address, such as https://rpc.mainnet.win.blockfabric.net/. When a wallet asks for a "New RPC URL" or "Network URL," this is the value it wants.

Everyday analogy: If the RPC is the customer service line, the RPC URL is the phone number. Dial the wrong number and you will reach the wrong company, or nobody at all.

Technical details

An RPC URL points to a server that runs a blockchain client (for our networks, clients such as GoQuorum or Hyperledger Besu) and exposes its JSON-RPC interface over HTTPS. One network can have more than one valid RPC URL. For example, the WIN Blockchain answers on both https://rpc.mainnet.win.blockfabric.net/ and https://rpc.win.blockfabric.net/, and both return the same chain and the same block data.

You can confirm which network an RPC URL belongs to by asking for its Chain ID:

curl -X POST https://rpc.mainnet.win.blockfabric.net/ \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

{"jsonrpc":"2.0","id":1,"result":"0x3b2"}

0x3b2 equals 946, which is the WIN Mainnet Chain ID.

3. When does my wallet use an RPC, and why do I need one?

Your wallet uses an RPC almost every time you open it. It uses the RPC to look up your balances, to show your transaction history, to estimate fees, and to deliver a transaction to the network after you approve it. Without a working RPC, your wallet cannot see or do anything on that blockchain.

Third-party wallets such as MetaMask come with a few popular networks already built in, such as Ethereum. Our brand blockchains are not built in, so you add them yourself by entering the network's RPC URL and other details. This is why you may see your WIN ERC-20 tokens in MetaMask right away, but you will not see Native WIN Rewards until you add the WIN network.

Everyday analogy: A TV only shows the channels it is tuned to. Ethereum is a channel your TV already knows. The WIN network is a channel you need to program in once, and after that you can flip to it any time.

Technical details

Common JSON-RPC methods a wallet calls in the background include:

4. What is a Chain ID?

A Chain ID is a unique number that identifies one specific blockchain. For example, the WIN Mainnet Chain ID is 946. Your wallet uses the Chain ID to make sure it is talking to the network you think it is, and it stamps that number into every transaction you sign.

Everyday analogy: A Chain ID is like a country calling code on a phone number. Two phone numbers can look almost the same, but the country code makes sure your call goes to the right country.

Technical details

Chain IDs were introduced in Ethereum's EIP-155 to provide replay protection. Because the Chain ID is part of what you sign, a transaction signed for one network cannot be copied and replayed on a different network. When you add a network, MetaMask calls eth_chainId on the RPC URL you entered, and it will show an error if the number returned does not match the Chain ID you typed.

Wallets may display the Chain ID in decimal (946) while the RPC returns it in hexadecimal (0x3b2). Both mean the same thing.

5. What is the difference between a public RPC and a private RPC?

A public RPC is an endpoint anyone can use without an account, like the official network RPC URLs listed in the directory below. A private RPC is an endpoint that belongs to a specific person, app, or paid provider, and it usually requires a personal key in the URL. Most community members only ever need the official public RPC.

Everyday analogy: A public RPC is like a public library. Anyone can walk in, and it can get busy at peak times. A private RPC is like a private study room you have reserved. It is quieter, but it is set up for you specifically.

Technical details

Public endpoints may apply rate limits to keep the service fair for everyone, which can occasionally cause slow responses or "too many requests" (HTTP 429) errors during busy periods. Private endpoints are typically used by developers, exchanges, or apps that make a high volume of requests. If a private RPC URL contains an API key, treat that URL like a password and do not share it publicly.

6. How do I add a network to MetaMask?

You can add any network from the directory below to MetaMask in a few steps. We use the WIN network as the example here.

1. Log into your MetaMask wallet.
2. Click the network selector in the top left corner.
3. Click + Add network.
4. Click Add a network manually.
5. Fill in the following details:
   • Network Name: Win Mainnet
   • New RPC URL: https://rpc.mainnet.win.blockfabric.net/
   • Chain ID: 946
   • Currency Symbol: WIN
   • Block Explorer URL: https://win.elevatescan.com/
6. Click Save.

The WIN network has now been added to MetaMask. You can switch to it at any time from the network selector. To add a different brand's network, repeat these steps using the values for that network in the Network RPC Directory.

Everyday analogy: Adding a network is like saving a new contact in your phone. You enter the details once, and after that you just tap the name.

💡 Pro-Tip: After you add a network, you may still need to import custom tokens to see them. See Import Custom Tokens to MetaMask.

Technical details

Behind the scenes, apps can ask MetaMask to add a network using the wallet_addEthereumChain request (EIP-3085). The information you enter by hand is the same information that request carries:

{
  "chainId": "0x3b2",
  "chainName": "Win Mainnet",
  "nativeCurrency": { "name": "Win", "symbol": "WIN", "decimals": 18 },
  "rpcUrls": ["https://rpc.mainnet.win.blockfabric.net/"],
  "blockExplorerUrls": ["https://win.elevatescan.com/"]
}

MetaMask requires the native currency of a custom network to use 18 decimals, so decimals is always 18 in this request.

Several of our networks use Chain ID numbers that are also registered to unrelated blockchains in public chain lists (for example, Chain ID 8, 120, 1776, and 6941). If MetaMask suggests a different network name or shows a warning when you enter the Chain ID, that is the reason. Always enter the network name and RPC URL exactly as shown on this page, and never accept a suggested RPC URL from a third-party list for our networks.

Third-Party Wallet Disclaimer: MetaMask is a third-party Web3 wallet and is not owned, operated, endorsed, or supported by Connect. Any instructions or examples provided in this FAQ are for educational purposes only. MetaMask may update its platform, terminology, or workflows at any time, so steps shown here may differ from what you see. For the most current instructions, please refer to MetaMask's official support resources.

7. Why is my transaction stuck, or why am I seeing an RPC error?

Most "stuck" transactions and RPC errors come from one of a few common causes. The table below lists them along with what you can try.

Everyday analogy: If your GPS says "no signal," your car still exists and so does the road. The app simply cannot reach its map service right now. An RPC error works the same way. It means your wallet cannot reach the network at the moment. It does not mean your funds are gone.

Technical details

JSON-RPC errors come back in a standard format. For example:

{"jsonrpc":"2.0","id":1,"error":{"code":-32000,"message":"nonce too low"}}

Codes from -32700 to -32600 usually mean the request itself was malformed, -32601 means the method is not supported by that endpoint, and -32000 covers server-side errors such as nonce or gas problems. You can always confirm whether a transaction reached the network by looking up its transaction hash on that network's block explorer, which reads the chain independently of your wallet's RPC.

8. Is it safe to use an RPC? Can an RPC steal my funds?

An RPC cannot move your funds on its own. Your funds can only move when a transaction is signed with your private key, and signing happens inside your wallet, not on the RPC. The RPC only reads information and delivers transactions that you have already approved.

However, a fake or malicious RPC can still cause problems. It could show you incorrect balances, track which addresses you look up, or trick you into approving something harmful. That is why you should only use the official RPC URLs listed on this page or on your brand's official support site.

Everyday analogy: An RPC is like a mail carrier. The mail carrier delivers letters you have already signed and sealed, but cannot sign a check on your behalf. A fake mail carrier could still hand you a fake letter, which is why you should only trust the official one.

Stay safe:

• Never share your 12-word Recovery Phrase or private key with anyone. No RPC, wallet setup, support agent, or network ever needs it. Connect Support will never ask for it.
• Only copy RPC URLs from this Help Center or your brand's official support site. Do not use RPC URLs sent to you in direct messages, comments, or social media posts.
• Read every approval screen carefully before you confirm, especially requests to "approve" or "set approval for all."
• If something feels off, stop and submit a request to our Support team.

Learn more: What's the Difference Between my Account Password, Encryption Passcode and Recovery Phrase? and Recovery Phrase or Seed Phrase.

Technical details

Methods that read data (eth_getBalance, eth_call, eth_getTransactionReceipt) do not need your key at all. The only method that changes the chain is eth_sendRawTransaction, and it only accepts a transaction that has already been signed locally by your wallet. A malicious RPC cannot forge that signature. The real risks of an untrusted RPC are privacy (it can log your IP address and the addresses you query), false data (it can return fake balances or fake results), and censorship (it can refuse to broadcast your transaction).

9. What is the difference between a block explorer and an RPC?

A block explorer is a website for people. It lets you search a wallet address or transaction hash and see the results on a web page. An RPC is a connection for apps. Your wallet uses it to read and send data automatically. Both look at the same blockchain, but they are built for different users.

Everyday analogy: A block explorer is like a store's public receipt lookup on its website, where you type in a receipt number and see what happened. An RPC is the cash register's direct line to the store's system, which the register uses automatically every time you check out.

Each blockchain has its own explorer and its own RPC. A Native WIN transaction will appear on the WIN Block Explorer but not on Etherscan, and the WIN RPC will not know about Ethereum transactions. For more on explorers, see What is a Blockchain Explorer (block explorer)? and How do I use the WIN Block Explorer or Etherscan?.

Technical details

Block explorers such as ElevateScan index the blockchain by reading from nodes (often over the same JSON-RPC interface) and store the results in a searchable database. That is why an explorer can quickly show a wallet's full history, while a plain RPC is better at answering one precise question at a time, such as "What is this address's balance right now?"

10. What does "EVM-compatible" mean?

EVM stands for Ethereum Virtual Machine, the engine that runs smart contracts on Ethereum. An EVM-compatible blockchain understands the same kind of addresses, transactions, and smart contracts as Ethereum. All of the brand networks in the directory below are EVM-compatible, which is why they work with Ethereum-style wallets such as MetaMask and why your wallet address looks the same (starting with 0x) on every one of them.

Everyday analogy: EVM compatibility is like different countries using the same electrical plug. Your device works in all of them without an adapter, even though each country runs its own power grid.

Technical details

Our networks run on Ethereum-based clients (GoQuorum and Hyperledger Besu), which expose the standard eth_* JSON-RPC methods. Although your address is the same on every EVM network, each network keeps its own separate balances. Holding WIN on the WIN Blockchain does not mean you hold anything at the same address on Ethereum or on another brand's chain.

11. Network RPC Directory

Use the details below to add a network to a third-party wallet such as MetaMask. Values were confirmed against each live network on September 29, 2026. If a value here ever differs from what you see elsewhere, please submit a request before using it.

Add to wallet: In MetaMask, go to the network selector, choose + Add network, then Add a network manually, and copy the values from the row for your network. The Block Explorer URL is optional, but we recommend adding it so you can open transactions directly from your wallet.

Notes about specific networks

• Give: Give Blockchain technology is currently being updated, and Give Nodes are not distributing during these updates. 
• Galvan: The Galvan explorer is available at both ize.elevatescan.com and galvan.elevatescan.com.

Remember: RPC URLs never need your Recovery Phrase or private key. If any website, message, or person asks for your 12 words in order to "connect," "sync," or "fix" a network, it is a scam.

Related articles

• How do I add the WIN network to my MetaMask wallet so I can see Native WIN Rewards?
• How do I get my WIN Wallet in Metamask?
• Import Custom Tokens to MetaMask
• Block Explorer
• What is a Gas Fee?
• What is a node?
• WIN Bridge