MegaETH RPC
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:
- 高可靠性——全球佈局的基础設施，旨在將停機時間降至最低
- 提升效能——針對生產級應用程式優化延遲與請求處理
- 整合式生態系統——透過 Quicknode Marketplace 上的專用 API（附加元件）以及 Streams 等產品，提供額外功能
請造訪「快速入門」頁面，建立您的端點並發送第一個請求。
支援的網路
Quicknode provides access to the following MegaETH networks:
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以及eth_getBlockByHashwork for all historical blocks. - Transaction data — Transaction records and hash-to-block lookups are retained indefinitely. Methods like
eth_getTransactionByHashwork 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_getTransactionCountwith 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.
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, 交易, transaction_lookup, bodies_history.
Complete reference for developers building on MegaETH with Quicknode:
快速入門
Get started with MegaETH quickly. Follow our step-by-step quickstart to set up your endpoint and make your first API request.
供應商端點
Learn how to configure and manage your MegaETH endpoints for optimal performance and reliability.
API 概覽
探索受支援的 API、網路、Quicknode 產品以及增強的 API 功能，以建置功能強大的應用程式。
市集
探索並整合來自 Quicknode 市集的強大外掛程式與工具，以強化您的 Web3 應用程式。
端點安全
透過身分驗證、白名單機制及最佳安全實務，確保您的端點安全。
錯誤代碼
Understand common error codes and troubleshooting steps for MegaETH API requests.