How to Add a Blockchain Network to MetaMask Using RPC URLs

Hello! As we speak, I would like to let you know how to add a blockchain community to MetaMask with the assistance of RPC URLs from GetBlock. Let`s begin!

Open MetaMask and navigate to community settings. Within the MetaMask extension (or telephone app), click on the community selector (top-left) and choose “Add Network” (or “Add Network Manually” underneath Customized Networks). This shows a kind to enter the community particulars.

Enter community particulars. MetaMask will ask for Network Identify, New RPC URL, Chain ID, Forex Image, and (optionally available) a Block Explorer URL. For instance, Ethereum Mainnet has Chain ID 1, image ETH, and explorer etherscan.io. At all times double-check these values (by way of official docs or pages like Chainlist) earlier than saving.

Save the community. After filling in all fields, click on “Save” (or “Add”) to add the community to MetaMask. MetaMask might immediate you to verify; test that the values match the meant community. Now that you’ve got saved, the brand new community will seem in your community dropdown listing.

Buying a GetBlock RPC Endpoint

Join to GetBlock. Join to a free account on account. Solely an e-mail deal with is required, and you need to use a number of entry tokens (API keys) with the free plan.

Arrange an endpoint. Go to My Endpoints within the GetBlock dashboard and arrange a new endpoint: choose the blockchain (e.g. Ethereum, BNB Sensible Chain, Polygon (Matic), and many others.) and community (Mainnet or Testnet) and click on “Get” or “Create”. This generates a non-public RPC URL tied to your entry token. For instance, a BNB Chain endpoint could possibly be https://go.getblock.io/0b19d0cdf1af437da8adc7aa3bexxxxx. Retailer this URL.

Concentrate to request quotas. GetBlock’s free tier now has about 50,000 requests per day (about 40,000–50,000 relying on the community) with a max of 5 requests per second. This must be adequate for particular person utilization. (Above free quotas, there are paid alternate options.) Solely use the URL of your account (your API token is included) because the RPC URL in MetaMask.

By no means make your token public. After getting the RPC URL from GetBlock, paste it into MetaMask’s “New RPC URL” area (step 2 above). You now have MetaMask arrange on GetBlock’s node.

Instance Configurations

Under are pattern community configurations utilizing GetBlock’s RPC endpoints. In every case, the New RPC URL is the URL you obtained out of your GetBlock dashboard (exchange <Your_Access_Token> along with your precise token):

• Ethereum Mainnet:
  • RPC URL: https://go.getblock.io/<Your_Access_Token>
  • Chain ID: 1
  • Forex: ETH
  • Explorer: https://etherscan.io
• BNB Sensible Chain (Mainnet):
  • RPC URL: https://go.getblock.io/<Your_Access_Token>
  • Chain ID: 56
  • Forex: BNB
  • Explorer: https://bscscan.com
• Polygon (PoS Mainnet):
  • RPC URL: https://go.getblock.io/<Your_Access_Token>
  • Chain ID: 137
  • Forex: POL (previously MATIC)
  • Explorer: https://polygonscan.com

Network names in MetaMask may be any string, e.g. “Ethereum by way of GetBlock”, however chain ID, image and explorer ought to match official values.

Troubleshooting FAQ

Q1: “Invalid RPC URL” error

Trigger:URL is mistyped or incomplete.
Repair:

• Be sure that the URL begins with https:// and is copied accurately out of your GetBlock dashboard.
• Make sure you chosen the proper blockchain (e.g., Ethereum Mainnet, BNB Sensible Chain).

Q2: “Chain ID doesn’t match” error

Trigger:The Chain ID you entered doesn’t match the one returned by the RPC.
Repair:

• Double-check the official Chain ID on your chosen community.
• Instance: Ethereum Mainnet = 1, BNB Sensible Chain = 56, Polygon = 137.

Q3: Transactions not sending or caught in pending

Trigger:Incorrect community settings or RPC congestion.
Repair:

• Re-check the community identify, RPC, and Chain ID.
• Strive resetting your MetaMask account underneath Settings > Superior.

This autumn: MetaMask gained’t join to dApp after switching RPC

Repair:

• Refresh the dApp website and reconnect.
• Clear browser cache or attempt incognito mode.

My Professional Suggestions Field

• At all times confirm the Chain ID earlier than saving the community. A mismatch will stop MetaMask from working correctly.
• Use https:// RPC endpoints until your app explicitly wants WebSockets (wss://).
• Bookmark the GetBlock dashboard to shortly entry and rotate RPC keys.
• Label networks clearly in MetaMask so that you don’t confuse testnets and mainnets.
• Think about upgrading to a devoted plan on GetBlock in case your dApp scales — this avoids price limits.