MegaETH RPC

With Quicknode, you get access to our global MegaETH network which always routes your API requests to the nearest available location, ensuring low latency and the fastest speeds.

Try free

Beta

MegaETH Overview

MegaETH is a high-performance blockchain platform featuring MegaEVM, an advanced execution environment built on Ethereum standards. The latest hardfork, Rex, is based on Optimism Isthmus (derived from Ethereum Prague), ensuring broad smart contract compatibility with the Ethereum ecosystem.

MegaETH is EVM-compatible, allowing most existing Ethereum-based Solidity contracts to run with minimal or no changes. All standard development tools like Hardhat, Foundry, and Remix work seamlessly. Key enhancements include a multidimensional gas model (separating compute and storage costs), higher contract limits (512 KB vs Ethereum's 24 KB), and advanced resource management. Note that contracts using deprecated opcodes like SELFDESTRUCT or relying on specific gas mechanics may require adjustments.

Interacting with MegaETH's APIs

MegaETH nodes expose a JSON-RPC interface that is compatible with Ethereum's JSON-RPC API. This means developers can use Ethereum's native tools, such as Foundry, Hardhat, and popular Web3 libraries, without modification.

However, due to MegaETH's architectural differences (including its multidimensional gas model and enhanced contract limits), some RPC methods may behave differently from those on Ethereum. We highly recommend cross-referencing with the official MegaETH documentation for the latest updates and technical specifications.

Make MegaETH API Calls

The quickest way to start building on MegaETH is to create a Quicknode endpoint and send your first JSON-RPC request.

Quicknode provides managed MegaETH endpoints, giving you immediate access to the MegaETH Mainnet and Testnet without the overhead of running infrastructure. These endpoints offer:

High reliability – globally distributed infrastructure designed to minimize downtime
Enhanced performance – optimized latency and request handling for production-grade apps
Integrated ecosystem – additional functionality through specialized APIs (add-ons) on the Quicknode Marketplace and products like Streams

Visit the QuickStart page to create your endpoint and send your first request.

Supported Networks

Quicknode provides access to the following MegaETH networks:

Mainnet

Type:Production

Chain ID:

4326

HTTP:

WSS:

Archive:No

Pruning:Block and transaction data retained indefinitely; historical state data pruned with ~15-day retention window

Network

Type

Chain ID

HTTP

WSS

Data Availability & Pruning Policy

Quicknode's MegaETH nodes run with --prune.policy=full, which applies a ~15-day (1,296,064-block) retention window for certain data categories. Here's what this means for data availability:

Available indefinitely:

Block data — Block headers and bodies are never pruned. Methods like eth_getBlockByNumber and eth_getBlockByHash work for all historical blocks.
Transaction data — Transaction records and hash-to-block lookups are retained indefinitely. Methods like eth_getTransactionByHash work for all historical transactions.

Subject to ~15-day retention window:

Receipt data — Transaction receipts (eth_getTransactionReceipt, eth_getBlockReceipts) are pruned from the database after ~15 days but are also persisted in static files.
Historical state queries — Methods that require account or storage history at a past block (e.g., eth_call, eth_getBalance, eth_getStorageAt, eth_getCode, eth_getTransactionCount with a historical block number) are limited to the ~15-day pruning window. Queries for state older than ~15 days may return errors or incomplete data.

Pruning Details

The following data categories are pruned under the full policy:

account_history — account state change sets (~15-day window)
storage_history — storage state change sets (~15-day window)
receipts — transaction receipts (~15-day window)
salt_history — salt change sets (~15-day window)
withdrawal_history — (~90-day window)
sender_recovery — fully pruned

The following are never pruned: headers, transactions, transaction_lookup, bodies_history.

Complete reference for developers building on MegaETH with Quicknode:

QuickStart

Get started with MegaETH quickly. Follow our step-by-step quickstart to set up your endpoint and make your first API request.

Provider Endpoints

Learn how to configure and manage your MegaETH endpoints for optimal performance and reliability.

API Overview

Explore supported APIs, networks, Quicknode products, and enhanced API features for building powerful applications.

Marketplace

Discover and integrate powerful add-ons and tools from the Quicknode Marketplace to enhance your web3 applications.

Endpoint Security

Secure your endpoints with authentication, whitelisting, and best security practices.

Error Codes

Understand common error codes and troubleshooting steps for MegaETH API requests.