What is the X Layer RPC URL?

The X Layer Mainnet RPC URL with BoltRPC is https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/xlayer. Replace YOUR_API_KEY with your API key from dashboard.boltrpc.io. The chain ID is 196.

What is OKB and how is it used on X Layer?

OKB is the native token of the OKX ecosystem and the gas token for X Layer. You need OKB to pay transaction fees. OKB can be acquired on OKX exchange and bridged to X Layer via the official bridge.

What is X Layer built on?

X Layer is OKX's Layer 2 built on Polygon CDK, a framework for zkEVM-compatible chains. It connects the OKX ecosystem to Ethereum with low fees and fast finality.

How do I add X Layer to MetaMask?

Open MetaMask, go to Settings, then Networks, then Add Network, and enter: Network Name: BoltRPC X Layer, RPC URL: https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/xlayer, Chain ID: 196, Currency Symbol: OKB, Block Explorer: https://www.oklink.com/xlayer.

Polygon CDK (Chain Development Kit) is an open-source framework for building zkEVM-compatible Layer 2 blockchains. Chains built with Polygon CDK inherit zkEVM compatibility and settle to Ethereum.

Does BoltRPC support WebSocket for X Layer?

Yes. BoltRPC provides WebSocket endpoints for X Layer at wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/xlayer.

How does X Layer's connection to OKX affect traffic patterns?

X Layer receives user and liquidity flows from OKX exchange through the official bridge. When OKX runs trading promotions or lists new tokens, bridging activity and protocol traffic spike. Dedicated RPC infrastructure handles this volume without degradation.

X Layer RPC Endpoint

X Layer connects OKX users to your dApp. A dedicated endpoint that holds up when exchange-driven traffic arrives all at once.

chain id · 196JSON-RPC 2.0WebSocketDebug

Start free trial Contact sales

LIVE LATENCY

14ms

LIVE

gateway round-trip · sampled every second

IN PRODUCTION AT Chainlink

Your endpoint, ready in one line.

Drop this URL into your RPC client, HTTP library or wallet config. No SDK install required.

HTTPS

https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/xlayer

WEBSOCKET

wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/xlayer

Replace YOUR_API_KEY with your API key. Get a free key →

Pick your stack.

Copy-paste examples for the libraries you already use. Swap the API key, hit run.

import { ethers } from "ethers";

const provider = new ethers.JsonRpcProvider(
  "https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/xlayer"
);

import { createPublicClient, http } from "viem";
import { xLayer } from "viem/chains";

const client = createPublicClient({
  chain: xLayer,
  transport: http("https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/xlayer"),
});

curl https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/xlayer \
  -X POST \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

Connect your dApp, bot, or protocol to X Layer Mainnet (OKX’s L2) with BoltRPC. For protocols integrated into the OKX ecosystem, predictable request-unit pricing eliminates the cost variability that comes with exchange-driven traffic spikes.

Chain at a Glance


Chain ID	196
Protocol	zkEVM (OKX) on ETH
Block time	~3 s
Native token	OKB
Finality	ZK proof verification on Ethereum
EVM compatible	Yes

What X Layer is Built For

X Layer is OKX’s Layer 2 blockchain built on Polygon CDK, designed to bridge the OKX exchange ecosystem to Ethereum. It connects OKB holders and OKX’s user base to DeFi and dApps with low fees and fast finality. X Layer’s DeFi activity is backed by OKX’s liquidity and user base, which provides a built-in distribution channel for protocols that integrate with OKX’s CEX infrastructure. Protocols on X Layer often serve users who arrive via the OKX exchange app and bridge to L2 for DeFi activity.

Built for teams that ship on X.

Predictable RU pricing for exchange-integrated protocols

X Layer protocols often see traffic patterns driven by OKX exchange activity: token listings, trading promotions, and bridging surges from OKX's user base. These create sudden, sharp RPC spikes. BoltRPC's published per-method request-unit pricing means those spikes do not translate into billing surprises. You pay for your plan, not for peak events.

OKX ecosystem traffic is volatile by design

X Layer's direct tie to OKX exchange means volatile traffic patterns during market events, token listings, and trading surges. BoltRPC's infrastructure handles these unpredictable spikes without dropped connections.

Polygon CDK architecture support

X Layer is built on Polygon CDK, a framework for zkEVM-compatible chains. BoltRPC supports the full JSON-RPC surface for CDK-based chains, including the same EVM methods that work on other Polygon CDK chains.

Full EVM compatibility

Any Ethereum code works on X Layer with a single endpoint change. Standard Solidity contracts, ABIs, and JSON-RPC methods all apply.

WebSocket for real-time X Layer events

Subscribe to X Layer events in real time via WebSocket. Useful for tracking bridge events between OKX CEX and X Layer in real time.

One provider for multiple zkEVM chains

BoltRPC supports X Layer alongside Linea, Scroll, and zkSync Era. If you are building across zkEVM chains, one API key covers the full set.

Full JSON-RPC coverage.

Every standard X method you would expect. Archive-only methods are available on request for qualifying plans.

STANDARD5

eth_calleth_getBlockByNumbereth_sendRawTransactioneth_getLogseth_getTransactionReceipt

X, explained.

Common questions about connecting to X over BoltRPC.

Ask a question →Read the docs

: The X Layer Mainnet RPC URL with BoltRPC is https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/xlayer. Replace YOUR_API_KEY with your API key from dashboard.boltrpc.io. The chain ID is 196.
: OKB is the native token of the OKX ecosystem and the gas token for X Layer. You need OKB to pay transaction fees on X Layer. OKB can be acquired on OKX exchange and bridged to X Layer via the official X Layer bridge. When building applications for X Layer, account for OKB gas token requirements in your wallet UX: users coming from OKX exchange will typically have OKB available, but users arriving from other ecosystems may need to bridge OKB before they can interact with X Layer contracts. Building a gas sponsorship or paymaster mechanism that abstracts OKB away from end users is a common pattern for consumer-facing X Layer applications targeting non-OKX users.
: X Layer is OKX's Layer 2 blockchain built on Polygon CDK, a framework for building zkEVM-compatible chains. It connects the OKX ecosystem to Ethereum, allowing OKB holders to use DeFi and dApps with low fees and fast finality. Because X Layer is CDK-based, it shares much of the same JSON-RPC surface as other Polygon CDK chains. Ethereum developers familiar with Polygon tools will find the transition straightforward: same libraries, same deployment process, same method names, just a different chain ID (196) and endpoint.
: Open MetaMask, go to Settings, then Networks, then Add Network, and enter: Network Name: BoltRPC X Layer, RPC URL: https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/xlayer, Chain ID: 196, Currency Symbol: OKB, Block Explorer: https://www.oklink.com/xlayer.
: Polygon CDK (Chain Development Kit) is an open-source framework for building zkEVM-compatible Layer 2 blockchains. Chains built with Polygon CDK inherit zkEVM compatibility and can settle to Ethereum. X Layer and several other L2s are built on Polygon CDK.
: Yes. BoltRPC provides WebSocket endpoints for X Layer at wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/xlayer. Use WebSocket for real-time X Layer event subscriptions.
: X Layer receives user and liquidity flows directly from OKX exchange through the official bridge. When OKX runs trading promotions or lists new tokens, bridging activity spikes. Protocols that serve these users see corresponding RPC traffic increases that are concentrated, short-lived, and difficult to predict. A listing on OKX can send a surge of users to bridge within minutes of the announcement. Public endpoints may throttle during these peak periods, returning errors precisely when user demand is highest. Dedicated RPC infrastructure sized for the workload absorbs these spikes without dropped connections or rate limit responses.

Ship on X this week.

An API key in under 60 seconds, X plus 23 other chains, and a team that answers when you write.

Start free trial View pricing