• © Goverland Inc. 2026
  • v1.0.2
  • Privacy Policy
  • Terms of Use
Aave DAOAave DAOby0xF1dF824419879Bb8a7E758173523F88EfB7Af193XG177

[TEMP CHECK] Deploy Aave v3 on megaETH

Voting ended 11 months agoSucceeded

[TEMP CHECK] Deploy Aave v3 on megaETH

Author: ACI

Date: 2025-02-21

Simple Summary

This TEMP CHECK proposes the deployment of an Aave V3 pool on megaETH.

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

  • megaETH
    • Website: https://www.megaeth.com/
    • Whitepaper: https://www.megaeth.com/research

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 a TEMP CHECK in order to get initial feedback from Community and Service Providers.
  2. Escalate proposal to TEMP CHECK Snapshot.
  3. If TEMP CHECK Snapshot pass, publish an ARFC to continue gathering community and Service Providers feedback.
  4. 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.

Off-Chain Vote

YAE
816.54K AAVE100%
NAY
2.36 AAVE0%
Abstain
0.23 AAVE0%
Download mobile app to vote

Discussion

Aave DAO[TEMP CHECK] Deploy Aave v3 on megaETH

Timeline

Feb 27, 2025Proposal created
Feb 28, 2025Proposal vote started
Mar 03, 2025Proposal vote ended
Feb 03, 2026Proposal updated