This is a initial step in creating a proposal to add a “user notification” feature for Lido users, similar to what Aave has added. The purpose of this initial post is to:
- Get general feedback from the community
- Identify which on-chain events are valuable to monitor and trigger notifications
- Determine how users would want to be alerted (email, telegram, etc).
Hal Notify is Web3’s most popular Notification notification service. We have front-end integrations with Aave, Liquity, Snapshot, and many other dapps. Our mission is to improve the Web3 user experience by providing end-users a seamless ability to set alerts and get customizable notifications on the Web2 platform of their choosing.
As one of the most important players in the Eth2.0 Ecosystem, Lido’s users are a natural area of interest for us. While we are not experts on Lido, we are experts on how helpful providing these notifications can be for development teams, users, and DAO votes.
We are interested in exploring a potential integration with Lido, if users in this community see value in receiving Lido-related notifications.
Rather than manufacturing a need, our team would rather hear from you first before crafting the formal proposal.
As such, your feedback is requested, read, and appreciated (even if you say NO!)
We are trusted by industry leading protocols including Aave and currently support over 20,000 users with Web3 Notifications.
Users are able to seamlessly deploy automated notifications to the destination of their choosing, with messages of their choosing, in a minute, without downloading a native app.
We can support any EVM chain that Lido operates on.
How it’s Used
For best results, the UX Flow goes like this: User logs into dapp front-end, interacts with dapp, clicks a button with the hal Logo, goes to app.hal.xyz, programs the notification result, deploys, and is done.
Here’s an example of how it looks with Aave!
The back-end integration related to event monitoring and subsequent notifications actions are all implemented by the team at Hal. Sometimes, we also support the integrated dapp with front-end modifications for the notification button, but generally it is best of the dapp’s front-end team handles that.
Integration takes between 2-4 weeks for development, QA, review, and finalization.
The cost for integration is quite low, and will be quoted once this submission receives community feedback if there is interest in the first place.
Our mission is to improve Web3 user experience by filling the need for alerts delivered on Web2 platforms. So far, Aave, Snapshot, and many other dapps have integrated our tool to the delight of those users. We hope to make using Lido easier, more seamless, and fun.
For your time in reading and responding to this.
CGO at Hal.xyz