MegaETH RPC Endpoint

MegaETH pushes the EVM into real time with millisecond mini-blocks. Get a dedicated endpoint with full archive, trace and debug, built for apps that can't wait.

chain id · 4326JSON-RPC 2.0WebSocketFull archiveTrace + debug
LIVE LATENCY
58ms
LIVE
gateway round-trip · sampled every second
IN PRODUCTION ATChainlinkEnjinTiingoGains Network

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/megaeth
WEBSOCKET
wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/megaeth

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

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

Connect your dApp, bot, or protocol to MegaETH with BoltRPC. MegaETH is the real-time Ethereum Layer 2 that produces mini-blocks in milliseconds, and predictable request-unit pricing keeps your costs flat while your application reads a chain that never pauses.

Chain at a Glance

Chain ID4326
ProtocolReal-time Ethereum L2 (specialized sequencer architecture)
Block timeMillisecond-range mini-blocks
Gas tokenETH
SettlementEthereum mainnet
EVM compatibleYes

What MegaETH is Built For

MegaETH’s premise is that blockchains should feel like servers: state updates in milliseconds, not seconds. It reaches that with a specialized node architecture: a high-performance sequencer executes transactions in real time and streams mini-block updates, while replica nodes serve reads. That pushes the EVM toward the latency of a conventional backend. That makes it the natural home for applications that were previously impossible on-chain: order-book exchanges, real-time games, streaming payments and anything where a one-second block time is nine hundred milliseconds too slow. It stays EVM compatible, so Solidity contracts and standard tooling carry over. The catch for infrastructure: a chain that updates every few milliseconds produces state faster than any polling loop can follow, so WebSocket streaming stops being an optimization and becomes the integration model.

Common Use Cases on MegaETH

On-chain order books and trading Millisecond state updates make central-limit-order-book exchanges viable on-chain. Their market makers and takers read book state continuously, a latency-sensitive workload where the RPC round-trip is part of the spread.

Real-time games and interactive apps Games that settle every action on-chain need reads that keep up with gameplay. WebSocket streams push state to game servers the moment it changes.

High-frequency DeFi Liquidations, arbitrage and rebalancing compress from seconds to milliseconds. Bots on MegaETH compete on infrastructure quality more than on strategy.

Simulation and debugging pipelines Full trace and debug support means CI pipelines and risk systems can replay transactions step by step against real chain state without running an archive node.

Built for teams that ship on MegaETH.

Full archive plus trace and debug

BoltRPC serves MegaETH with full historical state and both trace_* and debug_* method families, the deepest capability tier we measure. Query any state at any block, trace any transaction, all on the standard endpoint.

Built for real-time workloads

On a chain with millisecond mini-blocks, your RPC layer is the bottleneck if it isn't engineered for it. BoltRPC's infrastructure sustains the concurrent, high-frequency read patterns that real-time apps generate.

WebSocket-first integration

Subscribe to blocks, transactions and events over WebSocket at no extra charge. At MegaETH's cadence, streaming beats polling on freshness and on request volume, often by orders of magnitude on both.

EVM compatibility, zero migration friction

MegaETH is EVM compatible. Contracts, scripts and infrastructure written for Ethereum work with the usual changes only: RPC URL and Chain ID 4326.

Predictable pricing at high frequency

Real-time applications make a lot of calls. Every method has a fixed, published RU weight, so a high-frequency workload has a predictable monthly cost instead of a surprise invoice.

Full JSON-RPC coverage.

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

STANDARD6
eth_calleth_subscribeeth_sendRawTransactioneth_getLogstrace_transactiondebug_traceTransaction

MegaETH, explained.

Common questions about connecting to MegaETH over BoltRPC.

Ship on MegaETH this week.

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