Glide L1 Protocol XP

Add Glide L1 Protocol XP to Your Wallet — MetaMask, OKX, Rabby, Trust Wallet

Chain ID: 251·Symbol: GLXP

Glide L1 Protocol XP is an EVM-compatible blockchain with Chain ID 251 and native token GLXP. This page lets you add Glide L1 Protocol XP to MetaMask, Rabby Wallet, OKX Wallet or Trust Wallet in one click — no manual Chain ID or RPC entry required.

RPC Endpoints
https://rpc-api.glideprotocol.xyz/l1-rpc/
WSS
wss://rpc-api.glideprotocol.xyz/l1-rpc/

What is Glide L1 Protocol XP?

Glide L1 Protocol XP is an EVM (Ethereum Virtual Machine) compatible blockchain network. Any EVM wallet — MetaMask, Rabby, OKX Wallet, Trust Wallet, Coinbase Wallet — can connect and transact on Glide L1 Protocol XP once you add the network configuration.

Why do you need to add Glide L1 Protocol XP to your wallet?

MetaMask and most wallets only come pre-configured with Ethereum Mainnet. To transact, swap tokens, or use dApps on Glide L1 Protocol XP, you need to add the network first. Entering an incorrect Chain ID or RPC can put your assets at risk. Use the "Add to wallet" button above — data sourced directly from chainid.network, the canonical Ethereum chain registry.

How to add Glide L1 Protocol XP to your wallet

  1. 1

    Click Add to wallet

    Press the "Add to wallet" button above. MetaMask, OKX Wallet, Rabby Wallet or Trust Wallet will show a popup asking you to confirm adding the Glide L1 Protocol XP network.

  2. 2

    Confirm in your wallet

    Your wallet shows the Glide L1 Protocol XP network details: Chain ID 251, native token GLXP. Verify the Chain ID is correct, then click "Approve" or "Add Network".

  3. 3

    Switch to the new network

    After confirming, your wallet automatically switches to Glide L1 Protocol XP. You can start transacting right away — you will need GLXP to pay gas fees.

Glide L1 Protocol XP network technical details

To add manually, go to Settings → Networks → Add Network in MetaMask (or your wallet's equivalent) and enter the details below:

NameGlide L1 Protocol XP
Chain ID251
Native tokenGLXP
Decimals18
RPC Endpointhttps://rpc-api.glideprotocol.xyz/l1-rpc/

Important notice

  • Always verify Chain ID 251 before confirming — attackers sometimes create fake networks with similar names but different Chain IDs
  • You need GLXP tokens in your wallet to pay gas fees for transactions on Glide L1 Protocol XP
  • Data on this page is sourced from chainid.network — the community-verified Ethereum chain registry
  • If the "Add to wallet" button doesn't work, your wallet may not support wallet_addEthereumChain — add the network manually using the details below

Frequently asked questions

Is it safe to add Glide L1 Protocol XP to MetaMask?
Yes, if you use the "Add to wallet" button on this page. Data is sourced from chainid.network — the community-audited Ethereum registry. Adding a network does not expose your private key or grant any permissions to the dApp.
What is Glide L1 Protocol XP Chain ID?
The Chain ID of Glide L1 Protocol XP is 251. This unique number identifies the network and prevents MetaMask and other EVM wallets from mixing up transactions across different chains.
Do I need GLXP tokens to use Glide L1 Protocol XP?
Yes. Every transaction on Glide L1 Protocol XP requires GLXP to pay gas fees. You can purchase GLXP on exchanges and bridge it to Glide L1 Protocol XP, or use a faucet if this is a testnet.
What is the Glide L1 Protocol XP RPC endpoint?
An RPC endpoint is the server address your wallet uses to communicate with the Glide L1 Protocol XP blockchain — sending transactions, reading balances, and checking state. One popular Glide L1 Protocol XP RPC is https://rpc-api.glideprotocol.xyz/l1-rpc/. This page shows live latency for each RPC so you can pick the fastest one.
My wallet says Glide L1 Protocol XP already exists when I click Add — what do I do?
That's completely normal. If Glide L1 Protocol XP is already in your wallet, it will simply switch to that network instead of adding a duplicate — no error or conflict.
I added Glide L1 Protocol XP but the network won't load — what's wrong?
The most common cause is a broken or overloaded RPC endpoint. Your wallet uses RPC to connect to the blockchain — if the RPC is down, the network won't load even if it was added correctly. Fix: copy a different RPC from the list above (prefer green low-latency ones), then go to Settings → Networks in your wallet and replace the old RPC with the new one. Watch the tutorial video above for step-by-step instructions on updating your RPC.