MegaETH

• Name: MegaETH
• URL: https://www.megaeth.com/
• Category: real-time Ethereum L2 / low-latency sequencer architecture / stateless-validation performance stack
• Tags: ethereum-ecosystem
• Summary: MegaETH is worth cataloging not as just another fast EVM chain, but as a particular decomposition of high-performance rollup design: a large-RAM sequencer optimized for real-time execution, mini-block streaming to replica RPC nodes, OP-Stack-style settlement to Ethereum, and independent stateless validation built around SALT witnesses rather than full-state replay on every validator. Its primary materials make clear that the interesting mechanism is not simply more TPS; it is the split between who executes first, who streams user-visible state, who independently verifies blocks, and which parts of the system still remain centralized or operator-run today. The reusable mechanism insight is that MegaETH turns real-time blockchain into a comparison-ready control plane spanning sequencer hardware assumptions, witness distribution, replica-versus-full-node trust, data-availability dependence, and dispute-proof design.
• What it does:
  • Runs an Ethereum-compatible OP Stack L2 whose sequencer produces mini-blocks roughly every 10 milliseconds and EVM blocks roughly every second
  • Streams mini-block results to geographically distributed RPC nodes so wallets and apps can read receipts, logs, and updated state within milliseconds
  • Exposes a MegaEVM execution environment with Ethereum compatibility plus chain-specific differences such as a dual gas model and higher contract-size limits
  • Uses EigenDA for data availability and settles to Ethereum L1 through OP Stack-style batching and dispute resolution
  • Publishes a stateless validator that re-executes each block against compact SALT-based witnesses rather than maintaining a full local state trie
  • Open-sources key infrastructure components including MegaEVM, the stateless validator, and SALT, the authenticated key-value structure used to shrink witness and validation costs
• Key claims:
  • MegaETH’s site and GitHub org frame the chain around real-time execution with sub-second / sub-10ms user feedback and >100,000 TPS-style throughput goals, but the more useful mechanism detail is how that performance is packaged.
  • The architecture docs explicitly describe a single sequencer producing ~10ms mini-blocks and ~1s EVM blocks, then streaming state to globally distributed RPC nodes. That makes MegaETH a strong comparison point for systems where user experience depends on fast offchain state distribution before L1 settlement is complete.
  • The docs separate replica nodes from full nodes. Replica RPC nodes apply sequencer output without re-execution, while full nodes re-execute independently. That is an important trust split that generic fast L2 marketing usually flattens away.
  • MegaETH’s stateless-validation path is one of its clearest analytical contributions. The docs say validators can independently verify every block without maintaining full chain state by re-executing blocks against compact witnesses, and that laptop-class hardware can keep up in real time.
  • SALT is the main enabling sublayer behind that claim. The SALT repo describes a two-tier authenticated key-value structure meant to keep the authentication layer in memory and avoid random disk I/O during state-root updates, which turns state-layout design into a first-class performance and verification control surface.
  • The validation stack also exposes implementation-diversity and auditability questions. The stateless-validator repo says the default validator keeps a small trusted computing base around revm, and also supports a K-semantics-based executor path developed with Pi Squared, while sequencer nodes use a different high-performance execution path.
  • MegaETH’s docs also reveal meaningful current centralization surfaces. The sequencer is singular (with a standby failover path), and the developer FAQ says externally hosted or self-run RPC nodes are not yet available; current public RPC access remains team-operated. That caveat is important when comparing real-time Ethereum claims against decentralization narratives.
  • The settlement layer is also more specific than generic L2 branding. MegaETH uses EigenDA for block-data availability and Kailua, a RISC-Zero-based zk fraud-proof system, for OP-Stack dispute resolution, so its security story depends on more than just Ethereum finality.
• Whitepaper: No single canonical MegaETH whitepaper surfaced in this pass. The strongest primary materials were the official site, architecture and developer docs, stateless-validator and SALT repositories, and the GitHub organization overview collected in ../whitepapers/megaeth-primary-sources-2026-05-14.md.
• Sources:
  • https://www.megaeth.com/
  • https://docs.megaeth.com/architecture
  • https://docs.megaeth.com/developer-docs/overview
  • https://docs.megaeth.com/node-operation/stateless-validation
  • https://docs.megaeth.com/developer-docs/faq
  • https://github.com/megaeth-labs
  • https://github.com/megaeth-labs/stateless-validator
  • https://github.com/megaeth-labs/salt

Internal linkages

• Best low-latency execution contrast: firedancer.
• Best shared-confirmation contrast: espresso.
• Best lightweight-verification cousin: helios.

Comparison cut

• MegaETH is not interesting because it says fast.

• The note matters because one sequencer executes first, replica RPC nodes stream the result, and independent validation happens later through witnesses.

• That split is the real comparison surface.

• Last reviewed: 2026-05-31 UTC