# Aave opens final governance for a guarded Aptos activation

> Approval would begin a restricted CTF phase with APT, USDC, USDT, and sUSDe, broad initial authority held by a 4-of-7 Launch Steward, and a phased path toward Community Guardian and cross-chain DAO control.

- URL: https://riadefi.com/on-chain/2025-04-30-aave-v3-aptos-mainnet-arfc-snapshot/
- Type: Launch or access
- Stage: Proposed
- Evidence: confirmed
- Materiality: material
- Event date: 2025-06-22
- Version: 2, published 2026-08-22 (first published 2026-08-22)
- Follow-up: 2025-07-07
- Advisor-relevant: no
- Affects: Aave v3 (protocol)

## What happened

Aave created a final on-chain proposal to place its deployed Aptos market under a guarded activation process as its first non-EVM deployment.

## What changed

Approval would begin a restricted CTF phase with APT, USDC, USDT, and sUSDe, broad initial authority held by a 4-of-7 Launch Steward, and a phased path toward Community Guardian and cross-chain DAO control.

## What did not change

The proposal states that deployment contracts already exist, but public user capacity is intentionally unavailable during the initial restricted phase. Full DAO control and ordinary advisor access were not established.

## Confirmed

- The initial CTF phase is planned for approximately four to six weeks.
- The deployment team would seed up to $25,000 of each supported asset while leaving no room for user deposits during the restricted phase.
- The Launch Steward comprises Aave Labs and Aptos Foundation signers with a 4-of-7 threshold.
- Full governance requires later transfer of roles and an audited Governance V3 cross-chain executor.

## Still open

- The final vote and execution state within and after June.
- Completion and findings of the CTF, outstanding audit, and subsequent bug-bounty phase.
- The effective steward keys, role assignments, and emergency procedures.
- The timing and verification of public capacity and full DAO-control transition.

## What it means for an advisor

- Review the Aptos deployment as a distinct non-EVM control and implementation perimeter, including Launch Steward authority and cross-chain governance dependencies.
- Do not treat the restricted deployment as advisor-accessible or Ketju-approved until public capacity, executed roles, audits, and governance transition are independently verified.

## Previous interpretation

The April record treated Aptos as an ARFC-stage proposal awaiting a final AIP, guarded activation, and verification of its non-EVM control model.

## Sources

1. [Aave V3 Aptos Activation](https://vote.onaave.com/proposal/?ipfsHash=0x655034112ecc3f89cbcfc7420c490928d01772bcae507a954f1f26be02b4687b&proposalId=328) · Aave Governance · 2025-06-22


---

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