Cowrie Research

megaeth-primary-sources-2026-05-14

3 min read

MegaETH primary sources

Reviewed: 2026-05-14 UTC

Official site framing

  • https://www.megaeth.com/
    • Best concise public framing of the project.
    • Used to confirm MegaETH’s headline positioning around real-time Ethereum, sub-10ms block timing claims, and very high throughput targets.
    • Also useful because the site links the performance story to specific architectural workstreams like SALT and stateless validation rather than leaving the claims fully abstract.

Core architecture

  • https://docs.megaeth.com/architecture
    • Best source for the end-to-end role decomposition.
    • Used to confirm the explicit split among sequencer, mini-block streaming, geographically distributed RPC nodes, EigenDA-backed data availability, OP-Stack settlement, and Kailua-based dispute resolution.
    • Especially useful because it distinguishes replica RPC nodes from full nodes, which exposes where read scaling and independent verification actually diverge.

Developer overview

  • https://docs.megaeth.com/developer-docs/overview
    • Best source for the developer-facing execution model.
    • Used to confirm MegaEVM as the execution environment, its dual gas model, OP-Stack-derived bridge path, and the project’s claim of Ethereum-smart-contract compatibility with chain-specific execution differences.

Stateless validator docs

  • https://docs.megaeth.com/node-operation/stateless-validation
    • Best source for the validation architecture.
    • Used to confirm that MegaETH’s stateless validator re-executes each block against a witness, anchors from a trusted block hash, and is intended to run on commodity hardware.
    • Also useful because it makes the witness path, bootstrap trust anchor, concurrency model, and operational assumptions concrete instead of leaving stateless validation as a slogan.

Developer FAQ / current operational constraints

  • https://docs.megaeth.com/developer-docs/faq
    • Best source for current edge cases and centralization-adjacent caveats.
    • Used to confirm the 512 KB contract-size limit, public-RPC operational behaviors, mini-block semantics, and the important disclosure that self-hosted or externally run RPC nodes are not yet supported.
    • This matters because it shows where current network openness still differs from the project’s broader decentralization story.

GitHub organization overview

  • https://github.com/megaeth-labs
    • Best source for the broader implementation surface.
    • Used to confirm the public repos for MegaEVM, the stateless validator, SALT, and other performance-oriented components.
    • Also useful because the org description names the whole-stack optimization agenda directly: execution engine, native-code compilation, concurrency control, transaction streaming, novel trie design, and better blockchain-state databases.

Stateless validator repository

  • https://github.com/megaeth-labs/stateless-validator
    • Best source for implementation details and trusted-computing-base framing.
    • Used to confirm the partial-stateless model, on-demand bytecode fetching, linear scaling across CPU cores, revm-based small-TCB execution, and optional K-semantics-based executor support.
    • Important because it turns independent verification into a concrete design with explicit tradeoffs, not just a docs claim.

SALT repository

  • https://github.com/megaeth-labs/salt
    • Best source for the authenticated-state sublayer.
    • Used to confirm SALT’s two-tier architecture, fixed shallow top trie, dynamic bucket structure, memory-oriented design, and goal of eliminating random disk I/O during state-root updates.
    • This is the main technical reason MegaETH belongs in the corpus rather than being left as a generic performance-L2 brand.

Main takeaways from this pass

  • MegaETH clears the bar because it is not just another fast EVM or throughput-marketing page.
  • The most reusable analytical split is between single-sequencer real-time execution, streamed replica reads, stateless witness-based verification, and Ethereum-anchored settlement.
  • SALT and the stateless validator are the most important sublayers to carry forward into future comparisons, because they expose how MegaETH tries to offset the centralization pressure created by high-spec sequencer hardware.
  • MegaETH is especially useful in the corpus as a comparison point for Fogo / Firedancer / Based OP / other performance-first stacks where the real question is not only speed, but where execution authority, replay authority, witness serving, and user-visible finality actually sit.

Graph View