[ARC] UI/UX upgrade governance framework

Governance
1

[ARC] - UI/UX upgrade governance framework

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.

Title [ARC] - integrate [Entity] into the aave app

[Proposal]

Brief presentation of the entity and ecosystem 250 words max

[Proposed integration]

Brief presentation of the requested integration

examples:

  • 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.

[Current and proposed integration of Aave in the Entity ecosystem]

  • Is the Aave app highlighted in the entity application?
  • How does the integration benefit the Entity Aave’s current and potential future users?

[Technical integration]

  • 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.

3 Likes
2

Can we update it so that a github issue will link to the snapshot post and all relevant information

1 Like
3

This update announces the deprecation of the current UI/UX framework and governance process used to integrate third parties into the Aave App. The Aave protocol is a decentralized ecosystem of smart contracts running on several EVM networks. This ecosystem is permissionless and anyone can freely use 100% of the Aave protocol features if they are familiar with interacting with deployed code on-chain. However, because smart contract development experience should not be a prerequisite for interacting with permissionless protocols, there should be a multitude of various applications created by the Aave ecosystem to allow for a more accessible variety of user experiences.

The Aave Companies have contributed to the work of the Aave ecosystem by creating one of the applications that utilize the permissionless Aave Protocol as a backend; the Aave App. The development of the app is fully open source, and the team welcomes any developer to contribute to the improvement of the open-sourced app for the benefit of end-users.
In the past, integrations with the Aave app have typically gone through Aave governance. Some examples of what an integration may include are:

• A wallet requesting direct support on user onboarding.
• An onramp requesting the integration of an onramp widget.
• A notification system requesting to be integrated into users’ dashboards.

Integrations were added using the framework this comment is in response to.

Following the governance process, the Aave interface GitHub maintainers would review the integration pull request and provided they didn’t detect security issues, would merge it.

Whilst this process had benefits, integrators typically had difficulty interacting with it and there have been few examples of the process successfully onboarding integrators. This means the user interface hasn’t evolved as efficiently and effectively as it could.

Therefore, after careful consideration, we have determined that this process is no longer optimal for the functioning of the Aave App, and we believe that its removal will improve the App interface in the long run.

Going forward, prospective integrators should reach out to Aave Companies at integrators@aave.com to discuss the process for integrations.

It is important to note that the Aave App is still fully open source, allowing any developer to contribute to the improvement of the application for the benefit of end-users. Anyone can build a front-end for the Aave Protocol which is what makes DeFi so powerful.

2 Likes