[ARFC] Request Intermittent ENS Transfer from BGD

Governance Maintenance
1

Summary

This ARFC proposes that the Aave DAO request the transfer of ENS names currently associated with legacy operational ownership under BGD control.

The objective is to ensure that protocol-relevant ENS records are held under clear DAO-aligned ownership and remain available for ongoing governance, deployment, and infrastructure operations.

Motivation

Several ENS names tied to Aave governance, deployment, and protocol infrastructure remain under control of BGD, who have stated they will not be renewing their service provider contract.

As responsibilities transition, these names should be brought under an ownership structure that is transparent, maintainable, and aligned with current DAO operations. ENS names tied to governance contracts, deployment infrastructure, and protocol components are operational dependencies. Their control should not remain ambiguous or tied to entities stepping back from active responsibilities.

Specification

Aave Labs requests that the current holders transfer ownership and any relevant controller permissions for the following existing ENS names to 0xC77624e672E762907435725Bbd3dFe70DDD40D13. Once there is a DAO legal entity in place, the ENS names will be transferred appropriately.

  • aavelicense.eth

  • v31.aavelicense.eth

  • govv3ui.aavelicense.eth

  • govv3.aavelicense.eth

  • adi.aavelicense.eth

  • onaave.eth

Next Steps

  1. If there is community consensus, escalate to a Snapshot.

  2. If the snapshot outcome is YAE, the owner of https://app.ens.domains/0xC77624e672E762907435725Bbd3dFe70DDD40D13 should transfer ENS Domain ownership to 0xC77624e672E762907435725Bbd3dFe70DDD40D13 upon completion of the vote.

  3. Once ready to receive, transfer ownership to the Aave DAO’s legal entity.

Disclaimer

This interim structure is proposed solely to ensure continuity and orderly administration while a DAO-controlled ownership structure is being established. If this proposal advances, Aave Labs would coordinate the subsequent transition of the ENS names to the appropriate DAO-controlled entity once that structure is in place.

Copyright

Copyright and related rights waived via CC0.

1 Like
2

As far as I know 0xC77624e672E762907435725Bbd3dFe70DDD40D13 signers are not disclosed.
If transfer of ENS is needed I recommend to performed it to APE multisig address: 0xa9e777D56C0Ad861f6a03967E080e767ad8D39b6
For witch current signers are known: @EzR3aL, @LlamaRisk, @ACI, @TokenLogic

2 Likes
3

Nandy raises a valid point on
transparency. A known multisig
like APE would address the interim
custody concern more cleanly.

1 Like
4

The objective here is clear and the
transition makes sense given BGD’s
departure.

One process question worth raising:

The interim transfer is proposed to an
AaveLabs-controlled address pending a
DAO legal entity. What is the expected
timeline for that legal entity to be
established? And is there a contingency
if that timeline extends significantly?

Operational ENS names tied to
governance infrastructure should have
a defined handover deadline even in
interim structures.