Want to update you on the status of the grant to integrate Hal Notifications into the SSV protocol.
Hal has built a custom Notify Recipes for SSV that allows SSV users to automatically monitor and get custom notifications for protocol specific events.
Of the three activities detailed in the spec, all are completed and running in production
Custom development of recipes - Done
Hal Engine licence for SSV - running in production, ongoing out the grant timeframe
Maintenance and monitoring - ongoing out the grant timeframe
The main work was in create the custom recipes for SSV use-cases.
Allowing the user to directly set up the notifications for the use cases they care about and get notified over the channel they choose. The available notifications for the SSV recipes will be:
Operational runway recipe, enabling users to receive their operational runway (expressed in days) both periodically or based on a defined threshold, defined as “accountBalance / accountBurnRate”.
Operator Fees Change recipe, enabling users to be notified once an operator either declares a change of fee or executes it. We would get the operator list when the user sets up the notification (meaning that if they change operators, they would have to re-create such a recipe to update the list).
Network Fee Change recipe, enabling users to be notified when the network fee change was updated.
Liquidation Notification recipe, enabling users to be notified once they got liquidated.
Operator Removed recipe, enabling users to be notified when an operator is removed
Hi everybody, just to followup and confirm that, as decided on Discord, we are happy to extend the service of this payment/grant scope from “1 year” to “1 year from when SSV will go live in mainnet”.