Add Notifications Center to Aave v3

Governance General
6

gm @sendrax :wave:

One thing I don’t get, is that the proposal requests funds to maintain the service

The proposal is not about requesting funds to maintain the service as it is now (Aave UI integration → HAL website).

But a new and different service. That would replace (upgrade) the previous one if approved.

Users already pay to have the HAL notifications

End users don’t have to pay on hal.xyz and it has never been the end goal.

TL;DR What we are proposing is a notifications center integrated to Aave where the Aave user wont have to go to HAL again, and in which Aave users will be able to centralize all their alerts, as well as benefit from new ones created by HAL with the Aave community.

If for whatever reason HAL backend would fail, then a big part of the interface would not work, so it would be adding centralization

We have since 2020 a reputation to deliver on-chain events notifications near real time and at scale. Aave’s core services won’t anyway be affected by a disruption from a third party such as HAL, and protocol will continue working properly.

gm @fig :wave:

can HAL be hosted via IPFS?

We are flexible. As Aave open source front end, the notifications center UI can be hosted and served on IPFS. We will need to test it but don’t see any blockers.

As Aave helped bootstrap your team via a grant, do you see merit in a more preferential contract?

Aave was 12% of our revenues in 2021 and we are grateful for the early support of the Aave fam :ghost: :robot:.

For this reason we would like to push the revised proposal:

:point_right: A quarterly maintenance contract awarded to HAL for the continuous monitoring, maintaining, and improving of the deployed Notifications Center on app.aave.com/notify .

  • $30,000 (stables, or AAVE equivalent) allocated from the Aave DAO for the HAL Notifications Center development & maintenance contract. Paid 100% quarterly upon execution.

  • HAL will host and serve the Notifications Center UI (on IPFS). Everything else will still be centralized (API + backend).

  • HAL will also be responsible for the deployment, and continuous monitoring, maintenance, and improvements on the server throughout the duration of the contract.

  • If Aave DAO votes to end the contract funding will be returned against the remaining days of the quarter and we will provide sufficient training for admins to transfer those duties to a new organization.

  • The server is expected to be live within 7 days of this proposal being accepted on governance, assuming that access to the necessary systems and people is provided on a timely basis.

  • The contract will begin when this proposal is accepted on governance, and there will not be additional setup fees even if there are increased coordination costs to get the service running.

:point_right: Establish a Subgroup in the Aave Ecosystem: Community Notifications Center

  • Budget up to Aave DAO and allocated from the Aave DAO to fund this subgroup - we recommend a $50,000 (stables, or AAVE equivalent) minimum budget for community contributions related to this subgroup, including grants for development, evangelism and retroactive rewards for using the Notifications feature -

  • This subgroup will support the administration and maintenance of the Notifications Center, and will also serve a support system to onboard users and evangelize notifications to allow users to control their positions and use notifications to manage their risk.

  • Additionally, the group will be responsible for providing updates to the broader Aave fam on the evolution of the notifications.

This is a temperature check post. Feel free to comment before we push a governance proposal.