Mega Docs
  • 🐰Hi!
  • Getting Started
  • Introduction
    • What is MegaETH?
    • Just Another L2?
      • What Is a Blockchain?
      • Consensus & Execution
      • User Transaction
      • State Sync & Gas Limits
      • Legend
    • MegaLabs
    • Roadmap
  • Deep Dive
    • Overview
    • Node Specialization
    • Hyper-Optimizing the EVM
    • EigenLayer
  • Guide
    • User Guide
      • Onboarding
      • Hunting
    • Builder Guide
      • Programs
      • Build
  • Community & Projects
    • Mega Civilization
    • Ecosystem
      • Tools
      • Projects
Powered by GitBook
On this page
  • Diagram of Node Roles and Interactions
  • How the Diagram Works
  • Why Node Specialization Matters
  • Hardware Requirements
  • Conclusion
  1. Deep Dive

Node Specialization

PreviousOverviewNextHyper-Optimizing the EVM

Last updated 3 months ago

As discussed in the page, traditional Layer-1 (L1) blockchains often require every node to perform all the heavy lifting—consensus, transaction ordering, and execution—leading to redundant work and inherent scaling limits. Node specialization breaks this monolithic model by assigning specific tasks to dedicated nodes, unlocking significant gains in throughput and responsiveness.

Diagram of Node Roles and Interactions

Below is a high-level diagram illustrating how MegaETH implements node specialization. You’ll see the four major node roles—Sequencer, Prover, Replica, and Full Node—as well as the interactions among them and an external EigenDA component for data availability.

How the Diagram Works

  1. Sequencer Node (Leader)

    • Role:

      • Orders and executes transactions in real time.

      • Acts as the central processor, managing transaction sequencing and state updates.

    • Interaction:

      • To Replica Nodes: Sends state diffs (state changes) via the p2p network.

      • To Full Nodes: Sends complete blocks for re-execution and validation.

      • To Provers: Sends blocks and witnesses to facilitate proof generation.

      • To EigenDA: Publishes blocks, witnesses, and state diffs for long-term availability.

    • Key Advantage: Combines transaction ordering and execution into a single, high-performance node, eliminating consensus overhead and enabling real-time processing.

  2. Replica Nodes

    • Role:

      • Receive state diffs from the Sequencer and directly apply them to maintain an up-to-date local state.

      • Do not re-execute transactions but rely on prover-generated proofs for block validation.

    • Interaction:

      • From Sequencer: Receive state diffs through the p2p network.

      • Verification: Validate blocks indirectly using proofs generated by Provers.

    • Key Advantage: This lightweight design dramatically lowers hardware requirements, making it cost-effective for users.

  3. Full Nodes

    • Role:

      • Re-execute every transaction in the received blocks to validate their correctness and maintain a trustless, fully verified state.

      • Ensure network integrity for power users like bridge operators and market makers who require fast finality.

    • Interaction:

      • From Sequencer: Receive complete blocks for re-execution and validation.

    • Key Advantage: While hardware costs are higher than Replica Nodes, Full Nodes benefit from auxiliary information to optimize transaction re-execution. Their functionality ensures trustlessness across the network.

  4. Prover Nodes

    • Role:

      • Generate cryptographic proofs that attest to the correctness of state transitions asynchronously and out-of-order.

      • Facilitate indirect block validation for Replica Nodes.

    • Interaction:

      • From Sequencer: Receive blocks and witnesses to generate proofs.

      • To Replica Nodes: Provide proofs that ensure block validity.

    • Key Advantage: Provers isolate computationally intensive tasks, ensuring the broader network remains lightweight. Depending on the proof mechanism (e.g., ZK, Optimistic), their hardware requirements range from minimal to highly specialized (e.g., GPUs, FPGAs).

  5. EigenDA

    • What It Is:

      • An external data availability solution built on EigenLayer.

    • Interaction:

      • From Sequencer: Receives blocks, witnesses, and state diffs for decentralized storage.

      • To Nodes: Provides the network with access to required data for validation and re-execution.


Why Node Specialization Matters

  1. Efficiency Gains: Eliminates redundant work across nodes, focusing computation where it’s most needed.

  2. Optimized Hardware and Software: Critical tasks are concentrated in specialized nodes, enabling them to be tuned for maximum throughput.

  3. User-Friendly Options: Low-barrier replica nodes coexist with high-performance sequencers, ensuring decentralization.

  4. Liveness and Security

    • Robust: If the sequencer fails, the network can swiftly elect a new one.

    • Trustless: Provers ensure block validity, and full nodes independently verify state, preserving security guarantees.

Hardware Requirements

Node Type
CPU
Memory
Network
Storage
Example VM Cost ($/h)

Sequencer

100 cores

1-4 TB

10 Gbps

SSD

$10 (AWS r6a.48xlarge)

Prover (OP)

1 core

0.5 GB

Slow

None

$0.004 (AWS t4g.nano)

Replica Node

4-8 cores

16 GB

100 Mbps

SSD

$0.4 (AWS Im4gn.xlarge)

Full Node

16 cores

64 GB

200 Mbps

SSD

$1.6 (AWS Im4gn.4xlarge)


Conclusion

MegaETH pushes node specialization further than traditional L2s by ensuring only full nodes re-execute transactions, while other nodes focus on lightweight, optimized tasks. This eliminates redundancy, maximizes performance, and maintains decentralization, setting a new benchmark for blockchain scalability.

Specialized nodes are the foundation of MegaETH’s efficiency. Next, discover how Hyper-Optimizing the EVM unleashes their full potential.

For more details, refer to the .

EigenLayer page
Consensus & Execution