Hello Orbs community!
DeFi.org recently launched the public beta app for The Open DeFi Notifications Protocol - a community led initiative to provide users with decentralized and free mobile notifications for on-chain events, powered by the Orbs network.
You can read more about it here.
If you’re unfamiliar with the Notification app give it a go! It's available on both Apple AppStore and Google Play.
Since the official launch, the app has seen great progress with an increasing trend of active users and over 20 protocol integrations across 5 networks: Ethereum, BSC, Polygon, Fantom and Avalanche!
One of those integrations includes Orbs PoS notifications which enables Orbs stakers to set up free, real-time notifications to track their staking on both the Ethereum and Polygon chains.
You can find more info on that in this link.
Recently, the defi.org team shared some cool stats on the app and, as can be seen, Orbs is the 2nd more popular use-case with the most active notifications!
It’s great to see so many Orbs Delegators making use of the notification app, and we already received feedback from app users who reached out to us with some excellent input and suggestions for improvements. Therefore, we thought it would be a good idea to get additional feedback from the rest of the community.
We would appreciate it if you could take the time to fill in this short survey from your experience of using the app:
Any feedback is valuable and can help us improve the app for all users!
Exceptional responses, such as those that lead to bug fixes or noteworthy improvement in the app, will earn its submitter a gift voucher to the Orbs merchandize shop at the discretion of the Orbs team.
The Open DeFi Notification Protocol is a beta version that is still under active development, and all underlying digital assets, blockchain networks and DeFi platforms are also subject to ongoing development, and as such, the protocol or the underlying platforms: (a) may contain bugs, errors and defects, (b) may function improperly or be subject to periods of downtime and unavailability, (c) may result in total or partial loss or corruption of data or a delay or a failure to send or receive expected notifications.