[ARFC] $AAVE token alignment. Phase 1 - Ownership

[sakulstra]

This was all debunked before. While the snapshot does not specifically mention frontend, the images and breakdown on the forum suggest so.

Overall, there were multiple functions involved in V3’s creation. These functions included Data Science, Risk Management, QnA, Dev Ops, Smart Contract Engineering, Front-end Engineering, Back-end Engineering, Product, and Design.

@sakulstra

• The interface was payed for on the retroactive funding.
• The inteface was very actively marketed as “decentralized interface”, with huge emphasis on app.aave.com, only pointing to some ipfs hash for most of the time.
• if you look at the contributions over time, you will see that other SP contributors (tokenlogic, aci, bgd-labs) have contributed significantly to various features, on the common “decentralized interface”.
• Aside from direct contributions, tremendous effort has flown into supporting Avara on integrating new ecosystem contracts like governance v3, umbrella, new stk tokens, migrations(v2->v3, stkv1 → stkv2)
• In addition to these direct contributions, DAO SPs have spent a good amount of time improving paraswap, by optimizing routes and contributing to paraswap-dex-lib/src at master · VeloraDEX/paraswap-dex-lib · GitHub directly integrating GHO-GSMs and boosting Balancer boosted pool usage