[ARFC] Deploy Aave v3 on megaETH

[ARFC] Deploy Aave v3 on megaETH

Author: ACI

Date: 2025-03-10

Simple Summary

This ARFC proposes the deployment of an Aave V3 pool on megaETH, after successful TEMP CHECK and TEMP CHECK Snapshot passing.

Motivation

MegaETH is an EVM-compatible blockchain that aims to bring Web2-level real-time performance to the crypto world for the first time. Their goal is to push the performance to hardware limits, bridging the gap between blockchains and traditional cloud computing servers.

MegaETH plans to offer several distinguishing features, including high transaction throughput, abundant compute capacity, and millisecond-level response times even under heavy load.

The network offers a performant location to the deploy the Aave protocol, and the megaETH team are planning to support Aave’s launch on the network.

Specification

Risk Parameters will be provided by Risk Service Providers during the ARFC stage and ARFC will be updated accordingly.

Useful Links

Disclaimer

The current proposal is powered by Skywards. ACI is not directly affiliated with megaETH and did not receive compensation related to this proposal.

Next Steps

  1. publish an ARFC to continue gathering community and Service Providers feedback.
  2. If the ARFC snapshot outcome is YAE, publish an AIP vote for final confirmation and enforcement of the proposal.

Copyright

Copyright and related rights waived under CC0.

Summary

LlamaRisk preliminarily supports onboarding MegaETH, an Ethereum L2, to Aave while underscoring that its ecosystem is still in the testnet phase (launched on March 6, 2025) and lacks key infrastructure components necessary for Aave such as audited codebase, Chainlink oracles, and a bug bounty program. However, according to the team, some are expected to roll out soon. MegaETH aims to achieve 100,000 TPS, 10 Ggas/sec, and sub-10 millisecond block times, using node specialization, state diff propagation instead of syncing entire state changes, and a stateless validation model.

However, these come with trade-offs, including reduced decentralization (a single active sequencer at a time ordering transactions) and security risks from untested tech at scale like stateless validation and EigenDA (external component built on EigenLayer). As the infrastructure matures and the mainnet launch approaches (tentatively projected for the end of Q2 to the start of Q3, per the team), a more precise assessment of the project’s ecosystem and real-time performance will be possible. LlamaRisk will provide asset recommendations once the network is closer to mainnet readiness.

1. Network Fundamental Characteristics

1.1 Network Overview

MegaETH is building on OP Stack customized to work with Reth. It qualifies as an optimistic validium, relying on Ethereum for settlement and EigenDA for data availability. MegaETH adopts node specialization, allowing specialized operators like sequencers to handle the heavy lifting. It uses a centralized single active sequencer because it is needed to ramp up throughput and optimizations so that the L2 can scale up to 100,000 TPS and 10 Ggas/sec.

MegaETH has two types of blocks: mini blocks and EVM blocks with 10ms and 1s block times, respectively. EVM blocks ensure backward compatibility with existing tools and applications, while Mini blocks are MegaETH specific and require its Realtime API to access the information. Both block types share the same rollback guarantees, but finality depends on factors like Ethereum reorgs, DA failures, sequencer downtimes, etc. For MegaETH, implementing robust mechanisms to mitigate these risks is crucial to maintaining the rollback guarantee for 10ms Mini Blocks.

Source: MegaETH Major Components, MegaETH.

List of modifications from MegaETH that help them achieve higher throughput and lower block times:

  • Unlike Ethereum and other L2s, where full nodes perform both consensus and execution, MegaETH introduces node specialization (four specialized node types), which eliminates consensus overhead in execution and reduces redundant computation, allowing real-time updates.
    • Sequencer: An HPC machine responsible for ingesting and ordering transactions.
    • Replica Nodes: Receive state diffs via a P2P network, enabling rapid state updates without reprocessing transactions.
    • Prover: Implements the stateless validation scheme to validate blocks asynchronously and out-of-order.
    • Full Node: Re-executes all transactions to validate blocks.
  • Replica Nodes apply state diffs instead of every node executing transactions, leading to faster state updates and improved efficiency in state synchronization.
  • MegaETH uses a centralized sequencer like some L2s but goes further by having only one active sequencer at a time. This significantly improves transaction throughput by eliminating network-wide consensus bottlenecks. However, MegaETH’s sequencer node hardware requirement is high (100-core CPUs, 1-4TB RAM, AWS r6a.48xlarge, $10/hr).
  • Full nodes validate transactions asynchronously using stateless validation proofs instead of synchronously re-executing each transaction, reducing computational overhead on the network.
  • EigenDA is used for data availability instead of Ethereum’s native solution to reduce costs and data storage efficiency.

However, some trade-offs and risks arise from these modifications:

  • A single active sequencer centralizes transaction ordering, making megaETH vulnerable to outages and MEV manipulation or censorship.
  • Replica nodes applying state diffs without re-executing transactions can lead to incorrect state propagation if proofs are compromised.
  • The stateless validation model is relatively new and untested at scale, posing risks of unforeseen issues or exploits. Similarly, reliance on EigenDA for data availability is a new solution.
  • Ethereum’s trustlessness (full nodes executing all transactions) is sacrificed by having nodes accept state diffs rather than recomputes, introducing trust assumptions in the proving mechanism.

Previously, MegaETH’s launch-pool contract (currently unavailable) was audited by OtterSec on August 16, 2024. The audit identified four findings: two critical and two informational, all of which were resolved. Though they’re building on OP Stack and Reth, given the scale of their customization, it would be essential to see publicly available audits once the code is made available as an open source.

1.2 Decentralization and Legal Evaluation

MegaETH’s decentralization remains uncertain as key infrastructure, including testnet development and security mechanisms, is still evolving. While it has been confirmed that the sequencer will remain centralized to reduce computational overhead, they plan to implement a rotating system with sequencers distributed across multiple geographic locations, each with several hot backups. The exact number of sequencers has not been finalized, as the network is still in the testnet phase. Additionally, details on governance participation, including decision-making on key proposals and network upgrades, remain unclear at this stage.

Legal Commentary

The team reported that a Cayman Islands foundation is being established to supervise MegaETH governance. At this juncture, no official terms of use or other legal documents are available that clarify the foundation’s (or any other legal entity’s) degree of control over the sequencer.

2. Network Market Outlook

2.1 Market Infrastructure

MegaETH is currently in Testnet and focuses on onboarding developers and infrastructure providers. In the meantime, the public faucet is disabled. The team announced their deployment timeline: testnet deployment on March 6, 2025, app and infra onboarding from March 6-10, and user onboarding starting March 10. Builders will initially access 1.68 Ggas/sec with 15ms effective block times on a single-threaded setup, with further scaling planned.

Source: MegaETH block time since launch, MegaETH, March 11, 2025.

The chart shows multiple spikes in block time exceeding the baseline 10ms. Following the launch, MegaETH’s RPC node experienced downtime due to an edge case vulnerability, indicating that thorough testing will be required before further upgrades are launched.

DeFi applications building on MegaETH:

Tooling
Two block explorers are available: the official real-time performance dashboard uptime.megaeth.com and the community-run megaexplorer.xyz.

MegaETH has built in-house RPC nodes to support its high-speed environment, available at carrot.megaeth.com/rpc. However, the RPC has experienced downtimes post-launch, indicating the need for further optimization.

At this stage, details about the indexer and Oracle infrastructure remain unavailable, suggesting that these components are still in development or yet to be integrated.

2.2 Ecosystem Growth Potential

On February 12, 2025, MegaETH raised $13M through its NFT mint, “The Fluffle.” Earlier, on December 13, 2024, it secured $10M via the Echo sale, attracting over 3,200 investors from 94 countries. Previously, on June 27, 2024, MegaETH raised $20M in a Seed round from notable investors, including Vitalik Buterin and Dragonfly.

The team has been working on the World Computer thesis, and to evolve it, they’ve been closely working with builders through their accelerator program “MegaMafia,” which has been a success as the projects building on it have raised more money than the chain itself. This highlights the ecosystem’s growing infrastructure and future potential.

Source: MegaETH Testnet Roadmap, MegaETH, March 11, 2025.

The roadmap indicates that the testnet infrastructure is still in development and will require more time to mature, suggesting that the mainnet launch is not imminent. Past L2s have typically taken 4 to 10 months from testnet to mainnet, depending on testing requirements and audits, for example, Optimism (10 months), Linea (4 months), and Base (6 months). The MegaETH team has stated that the mainnet launch is expected between the end of Q2 and the start of Q3.

3. Impact of Aave Deployment

MegaETH is EVM-compatible, allowing Aave to deploy using the same smart contracts. However, optimizations would be necessary to accommodate its high-speed environment, mainly if mini blocks are used, as they have significantly lower block times (10ms) than EVM blocks.

List of lending markets building on MegaETH:

  • Teko: Real-time lending market with granular micro-liquidations, margin trading, and under-collateralized borrowing, all with the same deep onchain liquidity.
  • Avon: Orderbook matching-based lending framework with lending pools at the strategy layer, demand-based rates, and sub-second liquidation.

The common thing noticed here is MegaETH’s high throughput, enabling frequent Oracle updates and quicker liquidations, allowing for a more capital-efficient deployment. However, the description is theoretical, with no real test on the security and efficiency of such systems in production.

Currently, Chainlink oracles, the preferred solution for price feeds, are not integrated.

Disclaimer

This review was independently prepared by LlamaRisk, a community-led decentralized organization funded in part by the Aave DAO. LlamaRisk is not directly affiliated with the protocol(s) reviewed in this assessment and did not receive any compensation from the protocol(s) or their affiliated entities for this work.

The information provided should not be construed as legal, financial, tax, or professional advice.

1 Like

Overview

Chaos Labs tentatively supports the deployment of an Aave instance on MegaETH, contingent upon an additional analysis performed on mainnet data and an adequately developed price feed infrastructure. This report provides a detailed examination of MegaETH’s technical specifications and the associated risks.

Technical Architecture

MegaETH is an EVM-compatible L2 that delivers millisecond-level response times under heavy load, high transaction throughput, and abundant compute capacity. Designed to bridge the gap between traditional cloud computing and blockchain performance, MegaETH enables sophisticated applications that require rapid updates and real-time feedback loops.

Node Specialization

In the MegaETH blockchain architecture, node specialization fundamentally restructures the traditional operational model by assigning distinct roles to different node types, each optimized for specific tasks. This specialization includes sequencers, replica nodes, full nodes, and ZK prover nodes. Sequencers are responsible for transaction ordering and initial execution, rapidly processing incoming transactions to ensure minimal latency. Replica nodes, on the other hand, focus on applying state diffs transmitted by sequencers, updating the blockchain state without re-executing transactions. Full nodes re-execute transactions for independent verification, maintaining network integrity, while ZK prover nodes generate cryptographic proofs that validate state transitions, providing an additional layer of security through proof-based verification.

The node specialization allows for differentiated hardware requirements. Sequencer nodes, handling the bulk of computational tasks, operate on high-end servers to maximize performance, whereas replica nodes require less powerful hardware due to their limited role in verifying proofs. Full nodes benefit from auxiliary information from sequencers to re-execute transactions efficiently, ensuring trustless validation. This approach not only enhances performance but also ensures that the hardware cost remains proportionate to the node’s function


megaETH Architecture

The EigenDA in MegaETH ensures that when a sequencer produces a block, it must submit the associated data to the DA service. This service verifies that the data is received and makes it publicly available, providing a receipt to the sequencer. EigenDA is a data availability solution built on EigenLayer. By efficiently managing blob storage, offering a high write throughput of 15MB/s (up to 654,000 TPS with compression), and enforcing security through a slashing mechanism, EigenDA offloads data availability constraints, enabling rollups to scale while preserving Ethereum’s trust guarantees.

MegaETH introduces two distinct types of blocks: mini blocks and EVM blocks. EVM blocks are standard across Ethereum-compatible blockchains. In contrast, mini blocks are unique to MegaETH. Mini blocks are streamlined versions of EVM blocks, containing a concise set of metadata fields to reduce the data footprint. They operate on a rapid schedule, being produced and preconfirmed by the sequencer at intervals as short as 10 milliseconds, allowing up to 100 blocks per second. Unlike EVM blocks, which can be bulky due to their comprehensive headers designed for longer block times, mini blocks optimize for compactness and speed, reducing the overhead on network resources and storage, particularly on mobile devices. Each transaction processed by the system is recorded in both a mini block and an EVM block, ensuring thorough documentation and consistency.

Hyper-Optimizing the EVM

MegaETH’s Hyper-Optimized EVM Execution is designed to fully utilize modern hardware by eliminating software inefficiencies that traditionally limit blockchain performance. While CPUs, SSDs, and high-speed networks are capable of supporting 100K+ TPS, existing EVM implementations fail to leverage these resources due to bottlenecks in state updates, storage access, and execution overhead. The biggest constraint is updating the Merkle Patricia Trie (MPT), which currently accounts for over 90% of block production time in Ethereum clients like Reth due to excessive random disk I/O. MegaETH overcomes this by introducing a novel state trie optimized to minimize disk operations and maintain light client compatibility.

Beyond state optimizations, MegaETH also addresses computation inefficiencies in the EVM. Standard execution relies on bytecode interpretation, which introduces significant overhead by requiring multiple instructions for even simple operations. To overcome this, MegaETH implements Just-In-Time (JIT) compilation, which translates EVM bytecode into native machine code at runtime, reducing CPU instruction complexity and achieving up to 100x speed improvements for compute-heavy smart contracts.

Additionally, parallel execution is introduced to maximize CPU utilization—unlike existing solutions like Block-STM, which suffer from cascading aborts in high-contention workloads, MegaETH’s centralized sequencer enables the use of non-deterministic concurrency control algorithms, ensuring efficient, scalable parallel execution across 100+ CPU cores.

Decentralization

MegaETH operates with only one active sequencer, which reduces consensus overhead but introduces centralization risks, such as creating a single point of failure. To mitigate these risks, MegaETH team states that they will employ a two-fold strategy: first, it rotates among approximately 15 different sequencers operated by various entities. Second, each sequencer has a slashable economic stake on the Ethereum mainnet, providing a financial disincentive for any form of misbehavior or censorship. Additionally, to address liveness concerns, MegaETH maintains a passive sequencer ready to take over should the active one fail.

Market & Ecosystem

MegaETH is currently in the testnet phase and has not launched on the mainnet yet. According to MegaETH’s proposed schedule, the testnet deployment began on March 6th, with an initial phase dedicated to onboarding apps and infrastructure that lasted until March 10th. Starting from March 10th, MegaETH began onboarding users to further test the platform. However, after launching, the system experienced a downtime caused by an edge case in its custom-developed RPC stack. Afterward, the team acknowledged the issue and announced plans to enhance the robustness of MegaETH’s infrastructure going forward.


MegaETH Official X Account

Popular projects on MegaETH include Valhalla, GTE, CAP Labs and Teko Finance. Valhalla is a perpetuals exchange built on MegaETH, which completed a $1.5M pre-seed funding round at the end of 2024. GTE is a DEX built on MegaETH, known for offering real-time, low-latency trading. CAP Labs operates a stablecoin engine that utilizes a decentralized network of specialized operators to access external yield sources. Each denomination of stablecoin at CAP has two forms: interest-bearing and non-interest-bearing. The former earns yield through agent strategies and grows in value, while the latter remains pegged to its denomination. Teko Finance is a lending protocol built on megaETH. Its features include micro-liquidation, leveraged strategies and under-collateralized borrowing.

Currently, Uptime MegaETH and MegaExplorer are the two available block explorers for MegaETH.

Oracles

As the time of this writing, appropriate oracles on MegaETH are unavailable. Consequently, we recommend delaying the deployment of Aave on MegaETH until sufficient oracle infrastructure is established to ensure accurate asset pricing.

Assets and Listing Parameters

Since MegaETH is still in its early stages and has not yet launched on the mainnet, we are unable to obtain any information on key assets within the ecosystem, including supply, DEX liquidity, and bridging. Chaos Labs will continue monitoring MegaETH and, upon mainnet launch, will provide updated assessments and recommendations on the ecosystem, proposed listing assets, and listing parameters based on real-time data.

1 Like

Great analysis @ChaosLabs @LlamaRisk, thanks for sharing. At the moment, unless the aim is to prepare for an eventual mainnet launch, it seems a bit premature to consider launching on megaETH, especially with the lack of price feeds and other critical infrastructure. Would it be better to revisit this deployment once megaETH is further developed?

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.