MegaETH

MegaETH is built around an extreme performance thesis: instead of incrementally improving EVM throughput (like Monad’s parallel execution), scale single-sequencer performance to the maximum physically possible on modern hardware. The result is a chain where one powerful sequencer processes transactions at 100,000+ TPS with sub-millisecond block times — creating what the team claims is the first blockchain capable of supporting “real-time” applications. Backed by Vitalik Buterin (personal investment), Dragonfly Capital, and several Ethereum core developers, MegaETH attracted attention for both its technical ambitions and its unconventional “single hot sequencer” architecture.


Core Architecture: Real-Time Sequencer

Standard rollup architecture:

  • Transactions submitted to sequencer
  • Sequencer batches transactions into blocks every ~1-2 seconds
  • Blocks settled to Ethereum periodically
  • Result: 1-2 second “soft” confirmation

MegaETH architecture:

  • Single powerful sequencer processes transactions as a stream (no block batching)
  • Transactions processed in sub-millisecond “mini-blocks”
  • Real-time application-level latency: transactions visible to dApps in <1ms
  • Periodic settlement to Ethereum (like standard optimistic rollup but with much higher inbound throughput)

The “real-time” claim:

At sub-millisecond latency, MegaETH claims applications can be built that are impossible on slower chains:

  • Real-time order books (matching engine speed)
  • Gaming with on-chain state at 60+ FPS equivalent
  • High-frequency DeFi operations
  • On-chain real-time AI inference

Performance Specifications (Claimed)

  • TPS: 100,000+ (theoretical maximum; real-world depends on transaction complexity)
  • Block time: 1ms to 10ms (sub-100ms for most operations)
  • Gas limit per block: 100 megagas (50,000x higher than Ethereum)
  • Latency to inclusion: <10ms typical
  • Ethereum settlement: Periodic L1 settlement (preserving security with Ethereum as DA/settlement)

Technical Design Choices

The following sections cover this in detail.

Single Sequencer

  • Pro: Maximum throughput (no distributed consensus latency)
  • Con: Point of centralization (sequencer can censor or reorder)
  • Mitigation: Force-include mechanism (users can force transactions through L1 in case of censorship)
  • Roadmap: Decentralized sequencing planned but not immediate

Custom EVM Implementation

  • Maximum parallel execution where possible (similar to Monad)
  • Cache-friendly state access patterns
  • Hardware-specific optimizations (SIMD instructions)

Node Types

  • Sequencer: The single hot throughput node (writes chain state)
  • Full nodes: Verify transactions and maintain state (slower but decentralized)
  • Streaming nodes: Receive and verify real-time mini-blocks for dApp state updates

Pegged Ethereum Settlement

  • Like optimistic rollups, transactions ultimately settled to Ethereum
  • EigenDA or Ethereum calldata for data availability
  • Challenge period for fraud proofs

Supported Use Cases (By Team)

On-chain order books:

At 100,000 TPS, exchange-grade matching engines can run on-chain with DEX parameters. Centralized exchange matching speed (~1ms per trade) becomes achievable. This is the key claim that distinguishes MegaETH from other high-throughput chains.

Real-time gaming:

On-chain game state that updates fast enough for real-time gameplay — not turn-based but action games. The latency requirement for 30 FPS = 33ms per frame; MegaETH’s sub-10ms latency theoretically supports this.

AI inference:

Real-time AI model inference with on-chain verification — verify that an AI response was correctly computed by a registered model, in real-time.

High-frequency DeFi:

Automated strategies, arbitrage bots, and market making at frequencies not possible on chains with 400ms+ block times.


Investor Backing

  • Vitalik Buterin — personal investment
  • Dragonfly Capital — lead investor
  • Various Ethereum ecosystem funds and angel investors
  • The Vitalik backing is notable: he does not typically personally invest in specific L2/L1 projects

MEG Token / Launch Plans

MegaETH conducted a “Fluffle” NFT campaign (rabbit-themed NFT holders get ecosystem benefits at mainnet), which created early community membership and speculative activity before token launch.

Mainnet: Public launch May 2025

Token: Details to be announced; typical tokenomics for EVM chain (gas + staking)


MegaETH vs. Monad

Both are high-performance EVM chains with similar target users. Key differences:

Property MegaETH Monad
Architecture Single sequencer real-time Parallel EVM L1
TPS claim 100,000+ 10,000+
Finality model Optimistic rollup on ETH Native L1 consensus
Latency <1ms ~1-2 seconds
Settlement Ethereum Own L1
Decentralization Centralized sequencer Distributed validators
EVM compat 100% 100%

MegaETH maximizes raw throughput + latency. Monad maximizes decentralized throughput. Different engineering bets.


How to Access MegaETH

At mainnet (post-launch):

  1. Get ETH via
  2. Bridge to MegaETH (standard EVM bridge)
  3. Add MegaETH to MetaMask (chainID + RPC endpoint)
  4. Deploy or use dApps — any Solidity/EVM contract works

For asset security:


Social Media Sentiment

MegaETH attracted intense interest before mainnet, largely because of Vitalik’s personal backing (rare and noteworthy signal) and the extreme performance claims. The “100,000 TPS” number generated both enthusiasm and skepticism. Technical critics noted that single-sequencer claims should always be discounted against real-world conditions: mixed transaction complexity, adversarial users, and network conditions. The Fluffle NFT campaign created a dedicated community but also speculation. Post-mainnet feedback was generally positive about actual performance exceeding most L2 chains, though the 100,000 TPS claim under realistic conditions was evaluated by community benchmarkers. As with Monad, the “real-time applications” thesis needs actual applications to demonstrate the value — until developers build games, order books, or AI inference apps that specifically require sub-millisecond latency, the performance advantage is theoretical.


Last updated: 2026-04

Related Terms


Sources

Fox, R., & Weintraub, B. (2024). Real-Time Sequencing for Blockchain Applications. arXiv.

Kalodner, H., Goldfeder, S., Chen, X., Weinberg, S. M., & Felten, E. (2018). Arbitrum: Scalable, Private Smart Contracts. USENIX Security Symposium.

Bronshtein, A., Guo, X., Levi, G., & Levit, V. (2022). Parallel Transaction Execution for Scalable Blockchain Performance. arXiv:2210.01898.

Clark, J., Bonneau, J., Felten, E., Kroll, J., Miller, A., & Narayanan, A. (2014). On Decentralizing Prediction Markets and Order Books. Workshop on the Economics of Information Security.

Luu, L., Narayanan, V., Zheng, C., Baweja, K., Gilbert, S., & Saxena, P. (2016). A Secure Sharding Protocol For Open Blockchains. Proceedings of the 2016 ACM SIGSAC CCS.