# Aave approves the Ink whitelabel deployment at ARFC

> The approved plan would license Aave code for a centrally governed lending deployment, provide initial Aave service-provider support, create DAO revenue sharing, and permit incentive funding.

- URL: https://riadefi.com/on-chain/2025-07-21-aave-v3-ink-whitelabel-arfc-approval/
- Type: Governance
- Stage: Approved, not executed
- Evidence: confirmed
- Materiality: watch
- Event date: 2025-07-21
- Version: 1, published 2026-08-22 (first published 2026-08-22)
- Follow-up: 2025-08-08
- Advisor-relevant: no
- Affects: Aave v3 (protocol)

## What happened

Aave DAO voters approved an ARFC authorizing progression toward a whitelabel Aave v3 instance governed by the Ink Foundation.

## What changed

The approved plan would license Aave code for a centrally governed lending deployment, provide initial Aave service-provider support, create DAO revenue sharing, and permit incentive funding.

## What did not change

No Ink lending instance was confirmed live in July. The planned instance would not be governed by Aave DAO and would not be covered by Aave's Umbrella system.

## Confirmed

- The Snapshot closed on July 21, 2025 with approximately 789,556 voting YAE and 1,579 NAY.
- The proposal specifies centralized governance by the Ink Foundation without an initial governance token.
- The Aave DAO revenue share must be at least the equivalent of a 5% reserve factor based on borrow volume.
- Initial Aave service-provider support is specified for six months.
- The proposal expressly excludes the whitelabel instance from DAO-operated Umbrella coverage.

## Still open

- The final AIP, deployed contracts, governance transfer, and launch date.
- Final collateral, oracle, liquidation, pause, upgrade, and custody controls.
- The commercial support arrangement after the initial six months.
- Whether incentives create a genuinely advisor-accessible product requiring a separate Ketju object.

## What it means for an advisor

- Track the final deployment as a separate, centrally governed exposure rather than extending Aave v3 approval by brand or code lineage.
- Map executed controls and insurance boundaries before adding the Ink instance to the research perimeter.

## Sources

1. [[ARFC] Deploy a Whitelabel Aave V3 Instance on Ink](https://snapshot.org/#/aavedao.eth/proposal/0x4185135ca5693f3a7022372dc989ee432c1ca792cde020275f3dfb472a90d6f1) · Aave DAO Snapshot · 2025-07-17


---

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