What is the Mantle RPC URL?

The Mantle Mainnet RPC URL with BoltRPC is https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/mantle. Replace YOUR_API_KEY with your API key from dashboard.boltrpc.io. The chain ID is 5000.

How do I add Mantle to MetaMask?

Open MetaMask, go to Settings, then Networks, then Add Network, and enter: Network Name: BoltRPC Mantle, RPC URL: https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/mantle, Chain ID: 5000, Currency Symbol: MNT, Block Explorer: https://mantlescan.xyz.

Is Mantle EVM compatible?

Yes. Mantle runs the EVM and standard Ethereum tooling works out of the box. Only the RPC URL, Chain ID (5000) and the MNT gas token change.

What gas token does Mantle use?

Mantle uses MNT, its native token, for gas, unlike most L2s, which use ETH. Wallets need a small MNT balance to transact.

What makes Mantle's architecture different?

Mantle is a modular rollup: execution is OP Stack derived, but data availability is handled by an external DA layer instead of Ethereum calldata, keeping fees low for data-heavy applications.

Does BoltRPC provide Mantle archive access?

Yes, partial archive: historical state is available from the archive cutoff onward, and the exact depth is measured live against our own infrastructure.

Does BoltRPC support WebSocket for Mantle?

Yes. BoltRPC provides WebSocket endpoints for Mantle at wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/mantle. Use WebSocket for real-time event streaming: new blocks, pending transactions, contract event logs.

Mantle RPC Endpoint

Mantle pairs a modular L2 with one of the largest treasuries in crypto. Get a dedicated endpoint with archive access and debug methods included.

chain id · 5000JSON-RPC 2.0WebSocketPartial archiveDebug

Start free trial Contact sales

LIVE LATENCY

20ms

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/mantle

WEBSOCKET

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

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/mantle"
);

const blockNumber = await provider.getBlockNumber();
console.log("Latest block:", blockNumber);

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

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

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

Connect your dApp, bot, or protocol to Mantle Mainnet with BoltRPC. Mantle is the modular Ethereum Layer 2 behind the mETH staking ecosystem, and predictable request-unit pricing keeps your RPC costs flat while your protocol taps one of the deepest treasuries in crypto.

Chain at a Glance


Chain ID	5000
Protocol	Modular optimistic rollup (OP Stack based, external DA)
Block time	~2 seconds
Gas token	MNT
Settlement	Ethereum mainnet
EVM compatible	Yes

What Mantle is Built For

Mantle is the Layer 2 built by one of crypto’s largest DAO treasuries, and its ecosystem reflects that: liquid staking (mETH), yield products and DeFi protocols that lean on deep native liquidity. Technically it is a modular rollup, OP Stack derived execution with data availability handled externally, which keeps fees low for data-heavy workloads. Gas is paid in MNT rather than ETH, one of the few L2s where that is the case. For developers everything else is familiar: the EVM, Solidity, ethers.js, viem, Foundry and Hardhat all work unchanged. Staking dashboards, yield aggregators and DeFi backends on Mantle poll balances, rates and positions continuously, a sustained read load that outgrows public endpoints quickly.

Common Use Cases on Mantle

Staking dashboards and yield aggregators mETH and the vault ecosystem around it are read-heavy: rates, balances and APYs polled via eth_call on short intervals, multiplied by every connected user.

DeFi protocols and market makers Lending markets and DEXes on Mantle track collateral and pool state continuously, with WebSocket streams for fills and liquidations.

Indexers and analytics pipelines Treasury trackers and TVL dashboards backfill history and follow the head. An eth_getLogs pipeline with archive reads for history runs on one endpoint.

Position history and PnL tools Balance-at-block and state-at-block queries against the archive range power PnL charts and reporting, served from the same endpoint as your live reads.

Built for teams that ship on Mantle.

Archive access included

BoltRPC serves Mantle with partial archive depth, historical state from the archive cutoff onward, measured live against our own nodes and shown on this page. Recent-history features like position charts and PnL tracking work without a separate archive provider.

Debug methods included

debug_* methods are available on Mantle, so you can trace failing transactions and inspect execution without maintaining your own archive-grade node.

Built for staking and yield workloads

mETH rates, vault APYs and lending positions change continuously, and every dashboard and aggregator reads them on a loop. A dedicated endpoint keeps those reads fast at any user count.

WebSocket streaming included

Subscribe to new blocks, pending transactions and contract events over WebSocket at no extra charge. Yield rebalancers and monitoring react to events the moment they land.

One provider across the L2 landscape

BoltRPC serves Mantle alongside Ethereum, Base, Arbitrum and 20+ other networks behind one dashboard, one API key pattern and one pricing model. Add Mantle without adding another vendor.

Full JSON-RPC coverage.

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

STANDARD5

eth_calleth_getLogseth_sendRawTransactioneth_getTransactionReceiptdebug_traceTransaction

Mantle, explained.

Common questions about connecting to Mantle over BoltRPC.

Ask a question →Read the docs

: The Mantle Mainnet RPC URL with BoltRPC is https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/mantle. Replace YOUR_API_KEY with your API key from dashboard.boltrpc.io. The chain ID is 5000.
: Open MetaMask, go to Settings, then Networks, then Add Network, and enter: Network Name: BoltRPC Mantle, RPC URL: https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/mantle, Chain ID: 5000, Currency Symbol: MNT, Block Explorer: https://mantlescan.xyz.
: Yes. Mantle runs the EVM and standard Ethereum tooling, ethers.js, viem, Foundry, Hardhat, MetaMask, works out of the box. Only the RPC URL, Chain ID (5000) and the MNT gas token change.
: Mantle uses MNT, its native token, for gas, unlike most L2s, which use ETH. Wallets need a small MNT balance to transact; contract interactions are otherwise identical to any EVM chain.
: Mantle is a modular rollup: execution is OP Stack derived, but data availability is handled by an external DA layer instead of Ethereum calldata. That design keeps fees low for data-heavy applications while still settling to Ethereum.
: Yes, partial archive: historical state is available from the archive cutoff onward, and the exact depth is measured live against our own infrastructure. For full-history-since-genesis workloads, contact us.
: Yes. BoltRPC provides WebSocket endpoints for Mantle at wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/mantle. Use WebSocket when you need real-time event streaming: new blocks, pending transactions, contract event logs.

Ship on Mantle this week.

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

Start free trial View pricing