The Aave protocol is a decentralized ecosystem of smart-contracts running on several EVM networks. This ecosystem is permisionless and anyone with the required tech knowledge can freely use 100% of the Aave protocol features.
That being said, for a more accessible user experience, the Aave companies created the Aave application allowing the interaction with the Aave protocol without technical knowledge.
To reinforce the decentralization of the application, the Aave app is deployed on IFPS and considering Flux hosting to avoid centralization of hosting,
also, the Aave app, is fully open source and allows any developer to contribute to the improvement of the application for the benefit of the end-users.
As recently, we have witnessed multiple demands from third-parties to be integrated in the aave App (wallets, on-ramps etc…) The presented framework intends to provide governance guidelines to standardize the process of integration into the Aave App.
Brief presentation of the entity and ecosystem 250 words max
Brief presentation of the requested integration
- a wallet requesting a direct support on user onboarding
- an onramp requesting the integration of an onramp widget
- a notification system requesting to be integrated into user’s dashboard
- a portfolio tracker requesting link in users dashboard
In this section, the entity should detail which specific section of the app should be modified to integrate the entity.
- Is the Aave app highlighted in the entity application?
- How does the integration benefit the Entity Aave’s current and potential future users?
- Link to Aave interface PR requesting the integration
This framework is intended to provide standardization of UI/UX integration of the Aave App.
The proposed governance process for a UI integration is to have each entity do a governance thread open for at least 5 days.
Then open a snapshot vote with a starting voting period of 24h in the future with at least 3 days open vote period considered valid with a 100k AAVE YAE vote quorum.
the proposed options for the snapshot must be YAE/NAY/ABSTAIN.
The Aave interface GitHub maintainers will then review the integration PR and provided they don’t detect security issues, will merge the PR.
In the case of a security issue detected with the PR and not discussed before the snapshot vote, the GitHub maintainers will open technical communication channels with the entity in an effort to allow the integration to be merged but will keep a veto right regardless of the governance process in the case the integration is considered harmful to Aave users security.