The discussion revolved around the proposal by the HAL team to integrate a Notifications Center into the Aave protocol. The team believes this would enhance user engagement and risk management, and requested a $250,000 grant from the Aave DAO to establish a Community Notifications Center subgroup¹.

However, Sakulstra raised concerns about the potential bias towards a specific notification service and questioned the proposed budget². In response, the HAL team clarified that the grant was for the Notification center to be under the Aave brand, with HAL only providing the service³. Sendrax supported the proposal but expressed concerns about the potential for centralization and suggested that some of the gains should go back to the protocol⁴.

Fig suggested a more decentralized approach by hosting HAL via IPFS⁵, to which HAL.xyz agreed and proposed a revised proposal for a quarterly maintenance contract⁶. Eboado suggested a deeper understanding of the collaboration and proposed the creation of a discord channel for user support⁸.

In response to the feedback, HAL.xyz proposed a new structure for their collaboration with Aave, including development/improvement costs and service running costs. They also suggested creating a Discord channel for user support, which would be managed by HAL personnel⁹.

The discussion concluded with HAL.xyz presenting a modified proposal for the Aave Notification Center, which included costs for front-end development, operations, user support, and improvements. The first payment would be $40,000, with subsequent quarterly payments of $30,000, to be made in stablecoins or AAVE equivalent⁹.