For web3, a notification mechanism that can notify users or wallet addresses of important updates, events, actions and so on, does not exist yet. As a result of this lack, a lot of important events or required user actions end up being missed completely: for example, the expiration of ENS blockchain domains is inefficiently broadcast on Twitter, with the hopes that the grace domain user potentially reads about their domain’s expiry. If a protocol gets compromised, people have to look for other methods (besides the now-compromised protocol) through which they can notify the users.
Push tries to solve this with its push notification service.
To do this efficiently, the notification is stored and treated like a JSON payload, and this is transformed as per the rules of the different carriers when the notification ends up reaching them. The JSON payload can differ with payload types, and this ensures the flexibility of the content, as well as the data, storage interpretation and delivery.
What this means is that Push can allow users to be in direct, full control of what services they end up getting notifications from, and impose rules on the services, which includes spam protection for users, and limits for Push ability to add wallets as subscribers. This means that notifications are treated as a social feed rather than a piece of information.
There are four types of users: service providers, which want to send notifications, users, who want to receive notifications if they deem them to be beneficial, wallets enable users to receive notifications through their centralized or decentralized solutions, and token holders, who can define the rules between the above users.