# BTC.b and Aave launch on MegaETH mainnet

> The previously proposed Aave MegaETH deployment and BTC.b listing were represented by a first-party issuer as live, expanding both watched objects to a new chain and operational dependency perimeter.

- URL: https://riadefi.com/on-chain/2026-01-30-aave-v3-megaeth-deployment-arfc/
- Type: Launch or access
- Stage: Live launch
- Evidence: confirmed
- Materiality: material
- Event date: 2026-02-09
- Version: 2, published 2026-08-22 (first published 2026-08-22)
- Advisor-relevant: no
- Affects: Aave v3 (protocol); Lombard BTC.b (asset)

## What happened

Lombard reported that MegaETH mainnet launched with BTC.b as its canonical Bitcoin asset and that Aave was one of four live protocols supporting BTC.b at launch.

## What changed

The previously proposed Aave MegaETH deployment and BTC.b listing were represented by a first-party issuer as live, expanding both watched objects to a new chain and operational dependency perimeter.

## What did not change

The launch did not make MegaETH, its Aave market, or BTC.b exposure on that chain approved for Ketju clients. The notice did not provide verified contract addresses, an executed Aave payload, or independent liquidity and oracle observations.

## Confirmed

- Lombard dated the launch notice 2026-02-09.
- The notice states that MegaETH mainnet and its BTC.b infrastructure were live.
- BTC.b was identified as MegaETH's canonical Bitcoin asset.
- Aave, Avon, Kumbaya, and Prism were identified as live BTC.b venues at launch.

## Still open

- The final Aave governance execution, deployed market and asset addresses, oracle configuration, caps, liquidation settings, and administrative controls were not reconciled in this record.
- BTC.b minting, bridging, redemption, proof-of-reserve coverage, and stressed liquidity on MegaETH required separate verification.
- MegaETH's sequencer, upgrade, data-availability, bridge, and exit controls were outside the supplied evidence.

## What it means for an advisor

- Supersede the proposal-stage MegaETH interpretation in the Aave and BTC.b diligence files, while keeping the new chain exposure unapproved pending review.
- Require chain-specific verification of Aave contracts, BTC.b contracts, oracles, caps, liquidation liquidity, bridge routes, reserve coverage, and exit mechanics.
- Do not infer safety or suitability from the launch announcement or promotional performance claims.

## Previous interpretation

Aave's MegaETH deployment and BTC.b inclusion were previously recorded as proposed, with no live market or verified deployment established at the January boundary.

## Sources

1. [BTC.b Is Live on MegaETH](https://www.lombard.finance/blog/hardest-money-meets-fastest-chain-btc-b-is-live-on-mega-eth/) · Lombard Finance · 2026-02-09


---

Published by Ketju Research on RIADeFi (https://riadefi.com). Educational research for financial professionals; not investment, legal, tax, or compliance advice.