Add HAL push-in notification system on Aave


HAL allows protocols and DAOs to better engage their audience with on-chain events push notifications. This proposal looks to onboard HAL notification system into AAVE UI.



To integrate HAL on the AAVE UI, so that users can create recipes (pre-made triggers focusing on a specific use case, with super-easy set up) on HAL. By doing so, users will be notified via Email, Discord, Slack, Telegram, Twitter, webhook if their Pool Health Factor is reaching a predefined threshold.

Link to HAL pre-made recipe

Using this integration, the user clicks on a link on the AAVE website and gets redirected, in a new tab, to a custom made recipe on the HAL website, with all fields pre-filled and a custom template message already in place showing contextual information about the user position (total collateral, total debt, borrowing power left, current liquidation threshold, and max loan to value).



Following conversations with AAVE and HAL core team members, we’ve found that HAL is a prime candidate for AAVE, already having gathered thousands of AAVE users around the world with protocol trackers and automations.

The addition of HAL to AAVE UI will unlock additional level of protocol engagement for all AAVE users.

Benefits for the Aave community

Allow all AAVE users to be notified about their Health Factor status.

Using our recipe, AAVE users will be able to be updated at any time on the health factor conditions of their position, thus reducing the risk of being liquidated.

About HAL

HAL enables developers to connect their decentralized/centralized applications with blockchains in a matter of a minute with a SaaS solution, creating workflows from a web wizard or via APIs.

In the long run we see a single tech landscape with an intensive interaction between decentralized and centralized components where developers and companies will judiciously decide how to mix them depending on which components need to be trustless or not, and we aim to be one of the key players enabling this interaction.

HAL Recipes

Recipes are easy to use and curated triggers that focus on specific use cases, built for, and together with, the most exciting DeFI communities.

Most of our recipes are built in close collaboration with stakeholders of Ethereum’s communities: from brainstorming together ideas for recipes to what the UX would look like, down to the tiniest detail.

Previous collaborations include work done with the likes of Snapshot, Perpetual Protocols, Yearn Finance, Bancor, and many more.


HAL Twitter
HAL Telegram
HAL Website
HAL AAVE Recipes


From what I’m reading, this sounds like a perfect fit for borrowers and lenders getting more control and pointed information about their holdings.

A system called HAL that automates tasks. This can ONLY be helpful! If my take on this is wrong, you may shoot me out of the airlock later. :grin:


Gm @neptune and thank you so much for your support !
How does this written proposal sound to you?
Detailed enough? Any comments ??

Love this proposal. I appreciate that the proposed change is extremely minimal and non-intrusive. Hope to see this happen!

1 Like

Thank you so much for your support @pakim249 :raised_hands: - thanks for sharing, love hearing about products like these in the forums.

Embedding HAL in the Aave UI seems like a simple and beneficial add.

Three quick questions:

  1. Is a “recipe” synonymous for a contract?

  2. Is HAL only applicable on Etherum based protocols?

  3. How is different from a product like EPNS?

Thanks for taking the time here to provide a bit more clarity for us all.


Thanks for this clear ARC

Today only some community members use or know of HAL. Given the level of volatility of the cryptomarkets and resulting liquidations on Aave - it seems the community could use more risk management tools such as HAL. Having this messaging system inside the UI would make it more accessible.

I think this proposal would add a lot of value to Aave users.

Your tool offers the option to receive messages by mail, telegram or discord connecting this information to the corresponding wallet. How do you treat the personal information?

Is a “recipe” synonymous for a contract?

No, a recipe is synonymous with a trigger.

HAL is like IFTTT for the blockchain. A user can create a trigger based on some specific conditions: every time these conditions occur, the trigger will be triggered.

In short, a recipe is a trigger based on some particular use cases (such as monitoring the Health Factor in AAVE) built for, and together with, the most exciting DeFI communities.

Using a recipe, a user does not need to know anything about a smart contract of a specific protocol (for example, what is an event or how to read the Health Factor from the AAVE smart contract). The user only needs to know the information already in his possession, such as the address of his wallet or a threshold below which his position must not fall.

Is HAL only applicable on Etherum based protocols?

HAL supports different EVM compatible chains like Polygon, xDai, Binance, Polygon and Avalanche. HAL can support any protocols deployed on these chains.

How is different from a product like EPNS?

  • EPNS is a protocol. In order for dApps such as Aave to leverage EPNS they need to integrate the EPNS protocol, stake, and pay for transaction fees. Although this has some advantages, the adoption is slow and expensive.
    HAL is a SaaS, which has the advantage that no changes are required from the Aave team (nor from any other dApp) as HAL directly monitors the relevant blockchains (also see previous answer).
  • In fact, HAL already supports tracking the Health Factor (as well as deposits and borrow rates!) for Aave v1, v2, Polygon and Avalanche. Check it out here:
  • HAL supports a number of notification types, including email, Discord, Telegram, Twitter, Slack, and web hooks for creating further automation on top of it
  • We are working on the HAL 2.0 release that will come with a ton of new features, and a brand new frontend :)

From a privacy perspective, HAL is compliant with European restrictive GDPR rules, and therefore to US ones. We collect only the essential personal data that we need to deliver the service. “Identification data” → Name and surname, if available, collected through single sign-on. “Contact Data” → Email address, and tokens for third party integrations (e.g. Telegram). We keep this data in centralized encrypted database on a major cloud provider in Europe.