Add HAL push-in notification system on Aave

Reading time saved: 3 minutes

8 replies, 3117 views, 11 likes

governance.aave.com

TL;DR:

The proposal by HAL.xyz to integrate the HAL notification system into the AAVE UI, allowing users to create triggers for Pool Health Factor updates, was generally well-received. The system aims to increase protocol engagement and reduce liquidation risk, with HAL.xyz clarifying its functionality, compatibility, and data privacy compliance in response to user queries.

The discussion revolved around the proposal by HAL.xyz to integrate the HAL notification system into the AAVE UI. This integration would allow users to create "recipes" or triggers on HAL, which would notify them about the status of their Pool Health Factor on various platforms. The aim is to increase protocol engagement and reduce the risk of liquidation by keeping users informed about their position's health factor conditions1.

The proposal received support from users like Neptune and Pakim249, who appreciated the control and information it would provide to borrowers and lenders, and its minimal and non-intrusive nature respectively2,4. Questions were raised by Fig and Alex_BertoG about the term "recipe", the applicability of HAL on Ethereum-based protocols, how HAL.xyz differs from a product like EPNS, and the treatment of personal information6,7.

In response, HAL.xyz clarified that a "recipe" is a trigger based on specific use cases, and that HAL operates like IFTTT for the blockchain. They explained that HAL supports various EVM compatible chains and can support any protocols deployed on these chains. They also differentiated HAL from EPNS, stating that while EPNS requires dApps to integrate it, HAL is a SaaS that directly monitors the relevant blockchains and supports tracking various Aave metrics. They also assured that HAL is compliant with European GDPR rules and US ones, and only collects essential personal data needed to deliver the service8,9.

In conclusion, the integration of the HAL notification system into the AAVE UI was generally well-received, with users appreciating the additional control and information it would provide. The proposal is seen as a step towards increasing protocol engagement and reducing the risk of liquidation for AAVE users.

Posted 2 years ago

Last reply 2 years ago

Summary updated 2 months ago

Last updated 08/12 04:39