Adding Gravity to MetaMask sounds simple, but there is one twist that catches almost everyone: Gravity actually has two live networks. There is the newer Gravity L1 mainnet built by Galxe, and the older Gravity Alpha L2 — and they use completely different chain IDs. Add the wrong one and you will be staring at a zero balance, wondering where your money went.
In this guide, you will learn what Gravity is, which network you actually need, how to add it to MetaMask both automatically and manually, how to verify you did it correctly, and how to avoid the phishing scams that target custom network setups. Everything here follows the steps as they work in the current version of MetaMask in 2026.
- What Gravity actually is
- Why you would add Gravity to MetaMask
- Before you start: pick the right network
- Method 1: add Gravity automatically
- Method 2: add Gravity manually (step by step)
- Comparing the two methods
- How to verify you did it right
- Common mistakes (and how to fix them)
- FAQs
- The Bottom Line
id=”what-is-gravity”>What Gravity actually is
Gravity is a blockchain built by Galxe, the Web3 credentials and community platform you may know from on-chain quest campaigns. It is EVM-compatible, which means it works with Ethereum-style wallets like MetaMask and runs smart contracts written for Ethereum without modification.
The confusing part is that “Gravity” refers to two different networks, and you need to know which one you want before you touch MetaMask:
- Gravity Mainnet (L1) — the current flagship network. As of this guide’s writing, its chain ID is 127001 and its native token is G (18 decimals). This is where Galxe’s own apps, loyalty campaigns, and most new ecosystem activity live.
- Gravity Alpha Mainnet — the older Layer 2 network built on Arbitrum Nitro technology. Its chain ID is 1625. It still exists and some older apps use it, but new development has largely moved to the L1.
If someone tells you to “add Gravity to MetaMask” without specifying which one, ask. Nine times out of ten in 2026, they mean the L1 mainnet at chain ID 127001. Adding chain 1625 instead will not show your L1 tokens, and vice versa — which is exactly the kind of confusion this guide exists to prevent.
Both networks are EVM-compatible, so once the network is added, you interact with it the same way you would any other chain in MetaMask: connect dApps, sign transactions, and view activity in a block explorer. The official Gravity docs and site describe it as a high-throughput chain with fast finality, aimed squarely at Galxe’s community and omnichain use cases. Treat performance marketing claims with the usual healthy skepticism — what matters for this guide is that it works with MetaMask, and it does.
Why you would add Gravity to MetaMask
MetaMask ships with Ethereum and a handful of major networks preconfigured. Everything else — including Gravity — has to be added by hand. So when is it worth doing?
You are using Galxe or its ecosystem. Galxe’s campaigns, quests, and community rewards increasingly settle on the Gravity chain. If you want to claim rewards, vote, or use apps built for the ecosystem, MetaMask needs the Gravity network configured first.
You hold or use the G token. G is the native gas token of Gravity. You need the Gravity network in MetaMask to see, send, or receive G on-chain. Without the network added, the tokens are still on the blockchain — you just cannot see or move them from your wallet.
You want to explore the ecosystem. NFT projects, DeFi apps, and community tools on Gravity all require a wallet connection to the right chain. Adding the network once unlocks all of them.
There is no obligation to add a network you do not use. An unused network in MetaMask is harmless — it just sits in your network list. But there is one reason to hold off: if you are not sure which Gravity network an app needs, do not guess. A wrong guess costs you time and confusion, not money (your funds stay on the chain they are on), but it is still a hassle worth avoiding. If you are new to juggling multiple networks, our guide on how to switch networks in MetaMask safely explains the mechanics that apply to every chain, including Gravity.
Before you start: pick the right network
Do not skip this step. The single most common “bug” people report after adding Gravity is not a bug at all — it is the wrong network.
As of this guide’s writing, the network details are:
| Field | Gravity Mainnet (L1) | Gravity Alpha (L2, legacy) |
|---|---|---|
| Chain ID | 127001 | 1625 |
| Native currency | G (18 decimals) | G (18 decimals) |
| RPC URL | mainnet-rpc.gravity.xyz (HTTPS) | gravity-alpha.drpc.org (HTTPS, third-party) |
| Block explorer | mainnet-explorer.gravity.xyz | explorer.gravity.xyz |
A few honest caveats. First, RPC endpoints can change — projects retire old URLs and publish new ones. Before you save a manual entry, take a minute to cross-check the current RPC against Gravity’s official docs or MetaMask’s own network directory. Second, the dRPC endpoint above is a third-party public RPC, not Gravity’s official one; public RPCs can be rate-limited or slow, and you should never paste a network configuration from an unverified source into your wallet.
Also confirm your MetaMask is up to date. Recent versions added Chainlist suggestions right inside the add-network form, which makes the automatic method below much smoother. If your app or extension has not been updated in a long time, update it first — old versions sometimes behave differently on the networks screens.
Finally, remember that adding a network never moves your funds. It only gives your wallet the address book it needs to read and transact on that chain. If you already hold G somewhere, it is sitting on the chain it was issued on, waiting for you to look at the right one.
Method 1: add Gravity automatically
The automatic method is the fastest and, for most people, the safest. Instead of typing RPC details by hand, you let a trusted directory fill them in for you.
Step 1 — Open MetaMask. Launch the extension or mobile app and unlock your wallet.
Step 2 — Open the network menu. Click or tap the network selector at the top of the wallet (it probably says “Ethereum Mainnet” or whatever you used last).
Step 3 — Add a network. Choose Add network. In recent MetaMask versions, the add-network form shows Chainlist suggestions as you type — this is the feature you want.
Step 4 — Search for Gravity. Type “Gravity” in the network name field. You should see suggestions appear. Look carefully at the chain ID next to each result: you want 127001 for the L1 mainnet. Select it.
Step 5 — Review and approve. MetaMask prefills the name, chain ID, symbol, RPC URL, and explorer. Read them. Check the chain ID is 127001 and the symbol is G. If anything looks off — a weird RPC domain, a wrong chain ID — stop and add the network manually instead.
Step 6 — Save and switch. Approve the addition. MetaMask will usually ask if you want to switch to the new network. Say yes, and confirm the network name appears correctly in the selector.
That is it. You are done in under a minute. If no Chainlist suggestion appears for Gravity — which can happen if the directory is temporarily unreachable — fall back to Method 2 below.
Some wallet or dApp sites also offer an “Add to MetaMask” button that triggers the same approval flow. Those are fine as long as the site itself is legitimate. A button on a fake site can add a malicious RPC endpoint just as easily as a good one — so the golden rule is: only click add-network buttons on sites you arrived at deliberately and trust.
Method 2: add Gravity manually (step by step)
Manual setup takes a couple of minutes and gives you full control. Use it when the automatic method does not offer Gravity, when you want a specific RPC endpoint, or when you simply prefer to see exactly what goes into your wallet.
Step 1 — Open MetaMask and go to Networks. Unlock the wallet, click the network selector at the top, then Add network, then Add a network manually (on mobile: Settings → Networks → Add network → Add a network manually).
Step 2 — Enter the network details. For Gravity Mainnet (L1), fill in the fields exactly, using the values as of this guide’s writing (and cross-check them against Gravity’s official docs before saving):
- Network name: Gravity
- New RPC URL: https://mainnet-rpc.gravity.xyz
- Chain ID: 127001
- Currency symbol: G
- Block explorer URL: https://mainnet-explorer.gravity.xyz
Type the chain ID as plain 127001 — no “0x” prefix, no commas. MetaMask validates the chain ID against the RPC endpoint, so if you mistype it, you will get an error rather than a silently wrong network. That validation is your friend.
Step 3 — Save. Click Save. MetaMask pings the RPC endpoint to confirm it responds for that chain ID. If the endpoint is down or unreachable, you will see an error — in that case, double-check the URL for typos before assuming anything is broken.
Step 4 — Switch to Gravity. After saving, switch to the new network from the network selector and make sure “Gravity” appears at the top.
If you need the legacy Gravity Alpha L2 instead (chain ID 1625), the same steps apply with its details — but be deliberate about it. Most readers should not need this network. Mixing the two up is the number one source of “my tokens disappeared” panic with Gravity, and the fix is always the same: add the other network and look again.
If you have added other EVM networks before, the flow will feel familiar — the same manual steps work for Polygon, Soneium, and most L2s, which is why guides like our Polygon and Soneium walkthroughs read almost identically.
Comparing the two methods
Which should you use? Here is the honest comparison.
| Automatic (Chainlist suggestion) | Manual entry | |
|---|---|---|
| Speed | Under a minute | A few minutes |
| Typing errors | Practically impossible | Possible — double-check the chain ID |
| RPC choice | Whatever the directory lists | You pick the exact endpoint |
| Works offline-ish | Needs the directory to be reachable | Works as long as the RPC responds |
| Trust model | You trust the Chainlist data | You trust your own source for the details |
| Best for | Most users, most of the time | Power users, or when auto-add fails |
For a first-time setup of Gravity, start with the automatic method and verify the result (next section). If the suggestion list does not include Gravity or shows a chain ID you do not recognize, do the manual method instead of approving something uncertain. Certainty beats speed when it is your money on the other end.
How to verify you did it right
Adding the network is only half the job. Run these checks before you deposit anything:
1. Confirm the chain ID. The network selector should show “Gravity”. If MetaMask lets you view network details, the chain ID should read 127001 for the L1 mainnet. This single check catches most mistakes.
2. Check the currency symbol. Your balance area should show G, not ETH. If it shows ETH, you have added a different network (or an Ethereum testnet) by mistake.
3. Open the block explorer. From the network details, open the explorer link and paste your wallet address into its search. The explorer should load and show the chain’s data. If the explorer URL 404s or looks wrong, revisit the network settings.
4. Send a tiny test transaction. Before moving any meaningful amount, send the smallest amount you can — or better, receive a small amount first — and confirm it arrives and displays correctly. This is cheap insurance against every class of configuration error.
5. Check an existing balance. If you already hold G on Gravity, it should now appear in your wallet. If it does not, do not panic: double-check you added the right chain (127001 vs 1625), then verify on the explorer that the tokens are at your address. Tokens do not vanish because of a wallet setting — they are either at your address on that chain, or they were never there.
Common mistakes (and how to fix them)
“My balance is zero — where are my tokens?” Almost always the wrong Gravity network. You added 1625 but your tokens are on 127001, or vice versa. Add the other network and check again. Then confirm on the block explorer.
“Chain ID already in use” error. MetaMask is telling you that chain ID is already configured — possibly under a different name. Check your network list; Gravity may already be there with a slightly different label.
RPC endpoint errors when saving. Usually a typo in the URL, an endpoint that is temporarily down, or a network issue on your side. Re-check the URL character by character, and try again. If it persists, try an alternative public RPC from a source you trust.
Transactions stuck or failing. Make sure you are on the Gravity network (not Ethereum) and that you hold G for gas — ETH on Ethereum does not pay for Gravity transactions. If a transaction is pending, check it on the Gravity explorer rather than Etherscan.
Added the network but dApps do not see it. Some dApps cache the network list. Refresh the page, disconnect and reconnect your wallet, or restart the browser. Also confirm the dApp actually supports Gravity — not every app does.
Accidentally approved a suspicious network. If you clicked “add network” on a site you now doubt, remove the network from MetaMask settings immediately and do not transact on it. Adding a network alone does not give anyone your keys, but a malicious RPC is not something you want in your wallet.
FAQs
The Bottom Line
Adding Gravity to MetaMask takes a few minutes: use the automatic Chainlist suggestion for chain ID 127001 when it is available, or enter the network details manually and double-check them against official sources. The one thing that actually trips people up is not the setup itself — it is the two-network problem, so confirm whether you need the Gravity L1 mainnet or the legacy Alpha L2 before you start. Verify with a tiny test transaction, ignore anyone who DMs you “better” RPC settings, and you will be set.
This guide is for education only — not financial advice.
