Quicknode supports the following MegaETH APIs on all endpoints. Using your MegaETH endpoint, you can call any of the methods available in these APIs. For a complete list of supported RPC methods, refer to the documentation for each API.
対応API
対応ネットワーク
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. - 過去のステータス照会 — 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: ヘッダー, 取引, transaction_lookup, bodies_history.
対応製品
The following Quicknode products are supported on the MegaETH blockchain:
API Specifications (OpenRPC, OpenAPI)
Download the machine-readable API specifications for use with compatible tooling (e.g. OpenRPC Playground).