I’ve had an opportunity to review all the comments as well as read the proposal detail and have a couple of suggestions that @AaveLabs may want to consider moving forward.
Based on the community’s feedback, an alternative approach is proposed to balance Aave Labs’ vision for institutional RWA adoption with the DAO’s desire for control, fairness, and value accrual to AAVE holders.
Integrate Horizon Fully Under Aave DAO:
Horizon should operate as a direct extension of the Aave Protocol, not a separate licensed instance with strategic independence. This ensures all value accrues to AAVE and maintains the DAO’s permissionless ethos, adapted for institutional needs through permissioned RWA features.
No New Token:
Abandon the idea of a Horizon-specific token. Instead, use AAVE as the sole governance and value-accrual token. If funding is required, Aave Labs can submit a budget proposal to the DAO, potentially funded through AAVE treasury reserves or GHO issuance, subject to community vote.
Enhanced Profit-Sharing Model:
Implement a profit-sharing structure that prioritizes Aave DAO:
- Year 1: 80% to Aave DAO, 20% to Aave Labs (or service provider).
- Year 2: 75% to Aave DAO, 25% to Aave Labs.
- Year 3+: 70% to Aave DAO, 30% to Aave Labs.
This reflects Aave DAO’s critical role in providing infrastructure, brand, and liquidity while incentivizing Aave Labs to develop and manage Horizon effectively.
Compliance and Risk Management Frameworks:
Aave Labs should collaborate with the DAO to define clear compliance and governance frameworks (e.g., KYC/AML for institutional users, audited smart contracts for RWAs). These can be integrated into Aave V3/V4 via a modular “permissioned pool” feature, allowing institutional access without fragmenting the protocol.
Establish a DAO subcommittee or hire external experts (funded by the treasury) to oversee regulatory coordination, reducing risk to the broader ecosystem.
Boost GHO Adoption:
Retain Horizon’s focus on GHO as a primary borrowing asset to drive its adoption and stability. Allocate a portion of Horizon’s revenue (e.g., 10% of Aave DAO’s share) to a GHO liquidity fund, enhancing its utility and reinforcing its role in DeFi.
Community Oversight and Transparency:
Launch a revised Temp Check with detailed specifications on operational oversight, risk parameters, and legal structures. Ensure Aave DAO retains veto power over Horizon’s asset configurations and network expansions.
Competitive Development Option:
If Aave Labs insists on a new token or low profit share, open Horizon’s development to competitive bids from other service providers this ensures the DAO secures the best terms, leveraging community suggestions that Defi/TradFi professionals are eager to participate.
My Rationale as a Aave holder
This alternative aligns with the community’s demand for “Just Use AAVE” by keeping Horizon within the Aave ecosystem, avoiding dilution, and ensuring AAVE holders benefit from RWA growth.
I hope It acknowledges Aave Labs’ motivation for institutional adoption and the technical complexity of RWAs, offering them a fair (but reduced) revenue share to incentivize development.
We all recognise the strategic importance of RWA’s and the importance of this move—provided it strengthens, not undermines, Aave DAO.
Full disclosure I’m neither a lawyer, Defi guru, coding wizard or business expert just a simple Aave token holder so really don’t know if what I’m proposing is feasible but what I do know is what has been proposed is NOT feasible in its current format.
BTW I strongly suspect if this Temp Check were actually shared with existing service providers first we wouldn’t be having this conversation……