[TEMP CHECK] Focussing the Aave V3 Multichain Strategy

Hello and thank you for this (long overdue) proposal.
If I didn’t already know that ACI is working on it, I would have created something myself.

Let’s break it down on the different topics.

  1. Increases the Reserve Factor
    I fully support this measure. From the numbers in this proposal (which you can check live here Aave Analytics | TokenLogic) its clear that the only way to create at least a little bit of revenue, is to increase the RF. If there is no demand, the DAO has to take a bigger cut from the pie.

  2. Winding down instances
    It is absolutely clear that zkSync, Metis and Soneium aren’t a success for the DAO at all. Its only a big cost factor from deployment to asset listing to security checkups. All of them had several months or years to prove themselves. But there is no market fit, and so there is no need to host an Aave instance.
    I would also like to add other instances to the named ones, these are:
    CELO
    EtherFI (whiich is not listed in the table above, but still has an Aave market)

Both are very low revenue and TVL instances.
As of today, Celo is only sitting at roughly 57m.


And the chart from Defillama is showing the general trend for this chain.

For EtherFi the situation is actually different. They pivoted and their TVL is growing, but still the instance does not make sense in the way it exists currently. If EtherFI is interested in creating a special instance for their credit card product, there might be an interesting usecase. But as of now, the instance is not needed and only needs to be maintained by SP.

If EtherFI is interested they should come to the forum and propose a model that is benefitting them but also the DAO.

  1. Establishes a clear $2,000,000 annual revenue floor for new instance deployments
    For many years the DAO has basically accepted every proposal for an instance deployment and L1 and L2s. In the beginning this strategy helped to grow the protocol but overtime it was clear that thousands of L2 aren’t needed at all to scale Ethereum, which also means there is no need to have Aave on every chain out there. Focusing on the winner, like recently on Plasma, is enough.

Overall I support the threshhold of 2m annual revenue floor, although I would increase it to 2.5m$.
But how do we as a DAO make sure this is gonna happen? In my opinion there need to be clear rules around this framework.
We have had many comittments in the past, where teams said they will “bring hundreds of millions in TVL and big amounts of borrowings” which in the end never happened.

Thats why I want to add the following to this proposal @ACI.

A team, that wants to have an Aave deployment needs to guarantee a revenue floor of at least 2m$/2.5m$ per year. If this revenue isn’t there, these teams commit to deliver the rest of 2m$/2.5m$ floor - revenue made so far = Committment from these teams

This committment should should benefit the DAO but also Aave token holder.
Thats why i propose a split payment of 50/50 in GHO and AAVE token bought from the open market and send to the Aave: Treasury Collector V2 | Address: 0x464C71f6...9e5d6e18c | Etherscan or if @TokenLogic thinks another collector is better, then to this one.
The GHO can be used for payments and growth strategies and the Aave token help boost the buyback program.

Many other teams and protocols already charge fixed or flexible amounts of money to come to a chain. Aave should follow. Aave has proven to be the leader in its verticale and any great business out there is charging money, so should we. This will decrease governance workload, but also increase efficiency and hopefully as well revenue.

EDIT: Payment should not happen in a native token, only in stablecoins

9 Likes