> For the complete documentation index, see [llms.txt](https://docs.megaeth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.megaeth.com/developer-docs.md). # Developer Docs - [Overview](https://docs.megaeth.com/developer-docs/overview.md): Overview of developing on MegaETH — EVM compatibility, gas estimation, debugging, and bridging. - [Bridge ERC-20 Tokens](https://docs.megaeth.com/developer-docs/bridge-erc20.md): How to deploy and bridge an ERC-20 token from Ethereum to MegaETH using the OP Stack Standard Bridge. - [Send Transaction](https://docs.megaeth.com/developer-docs/overview-1.md): How to submit transactions on MegaETH — deploy contracts, estimate gas, and debug failures. - [Contracts & Tokens](https://docs.megaeth.com/developer-docs/overview-1/contracts.md): Key contract addresses and tokens on MegaETH and Ethereum Mainnet. - [Gas Estimation](https://docs.megaeth.com/developer-docs/overview-1/gas-estimation.md): How to estimate gas on MegaETH — code examples, toolchain configuration, and common pitfalls. - [Debugging Transactions](https://docs.megaeth.com/developer-docs/overview-1/debugging.md): Debug failing transactions on MegaETH — trace with debug\_traceTransaction, replay with mega-evme, and diagnose gas errors. - [Force Inclusion — Foundry](https://docs.megaeth.com/developer-docs/overview-1/force-inclusion.md): Force-include a transaction on MegaETH using Foundry (cast or forge) — step-by-step guide for scripted and automated submissions. - [Read from MegaETH](https://docs.megaeth.com/developer-docs/overview-2.md): How to query state and data from MegaETH — JSON-RPC methods, rate limiting, subscriptions, and real-time queries. - [Realtime API](https://docs.megaeth.com/developer-docs/overview-2/realtime-api.md): MegaETH Realtime API — how to use MegaETH's low-latency extensions to Ethereum JSON-RPC for real-time data access. - [RPC Reference](https://docs.megaeth.com/developer-docs/overview-2/rpc-reference.md) - [eth\_subscribe](https://docs.megaeth.com/developer-docs/overview-2/rpc-reference/eth_subscribe.md): eth\_subscribe — WebSocket subscriptions for real-time logs, state changes, mini-blocks, and block headers on MegaETH. - [eth\_callAfter](https://docs.megaeth.com/developer-docs/overview-2/rpc-reference/eth_callafter.md): eth\_callAfter — execute eth\_call after waiting for an account's nonce to reach a target value. - [eth\_getLogsWithCursor](https://docs.megaeth.com/developer-docs/overview-2/rpc-reference/eth_getlogswithcursor.md): eth\_getLogsWithCursor — paginated log queries using a cursor for incremental retrieval of large datasets. - [realtime\_sendRawTransaction](https://docs.megaeth.com/developer-docs/overview-2/rpc-reference/realtime_sendrawtransaction.md): realtime\_sendRawTransaction — submit a transaction and receive the receipt in a single call without polling. - [Error Codes](https://docs.megaeth.com/developer-docs/overview-2/rpc-reference/error-codes.md): MegaETH JSON-RPC error codes — HTTP status codes, RPC error codes, explanations, and mitigations. - [Transaction Execution](https://docs.megaeth.com/developer-docs/overview-3.md): How MegaEVM differs from standard Ethereum — contract size limits, gas forwarding, and precompile overrides. - [Gas Model](https://docs.megaeth.com/developer-docs/overview-3/gas-model.md): MegaETH dual gas model — compute gas, storage gas, bucket multiplier, resource limits, and developer tips. - [Resource Limits](https://docs.megaeth.com/developer-docs/overview-3/resource-limits.md): MegaETH resource limits — 7 per-transaction and per-block ceilings on gas, compute, data, KV updates, state growth, transaction size, and DA size. - [Volatile Data Access](https://docs.megaeth.com/developer-docs/overview-3/volatile-data.md): Volatile data access on MegaETH — what triggers the 20M compute gas cap, best practices for reading block data and oracle state, and common pitfalls. - [System Contracts](https://docs.megaeth.com/developer-docs/overview-3/system-contracts.md): MegaETH system contracts — addresses, interfaces, preconditions, and usage examples. - [Build with AI](https://docs.megaeth.com/developer-docs/build-with-ai.md): AI coding skills and tools for building on MegaETH with Claude Code, Cursor, Windsurf, and other AI assistants. - [Tooling & Infrastructure](https://docs.megaeth.com/developer-docs/tooling.md): Developer tooling and infrastructure partners on MegaETH — RPC providers, block explorers, oracles, indexers, bridges, wallets, account abstraction, developer tooling, and more. - [Verifiable Randomness (VRF)](https://docs.megaeth.com/developer-docs/vrf.md): Verifiable onchain randomness on MegaETH via DrandOracleQuicknet — a preinstalled, stateless BLS12-381 verifier for the public drand quicknet beacon. - [Onchain Payments](https://docs.megaeth.com/developer-docs/payments.md): How to accept onchain payments in a MegaETH dapp — the HTTP 402 "pay then retry" pattern, the x402 and MPP protocol families, and five concrete payment flows (one-time and pay-as-you-go, user-paid and - [Developer FAQ](https://docs.megaeth.com/developer-docs/faq.md): Frequently asked questions for MegaETH developers — EVM compatibility, gas, transactions, mini-blocks, RPC, and tooling. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.megaeth.com/developer-docs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.