Web3 Notifications
Quick explainer of what web3 notifications are, who can trigger them, its different types etc
Any successfully created channel, in its active state, can send notifications to its subscribers about a wide range of things related to defi, governance proposals, web3 news, or any other crucial updates about their protocol/services.
Notifications land in the inbox of those users who are subscribed to the channel. Non-subscribers of a particular channel aren't alerted about notifications from that channel as they land in their spam box.

Who can Send Notifications?

As per the current design of the protocol, there can be 3 main actors who can send notifications:
1. Channel Owners: The owners of a particular channel can send notifications to their subscribers.
2. Delegate Notification Senders: Channel owners can allow any particular wallet address to send notifications on behalf of his/her channel. This feature is called delegated notifications and you can read more about it in this section πŸ‘‰What are Delegated Notifications?​
3. Notifications To Yourself: The EPNS Communicator allows any address to send notifications to themselves πŸ˜ƒ It’s important to note, however, that the address sends the notification to themselves only.
Note:
Sending notifications is a gasless transaction and therefore notification senders need not pay any gas fee while sending notifications via the Dapp.
Gas Fees are only applicable when on-chain notifications are triggered directly from smart contracts.
​
Now that you have a brief overview of notifications in the protocol, let's understand and explore the different ways to send notifications to your users.

How to Send Notifications?

How to Receive Notifications?

Learn more about Notification

Copy link
On this page
Who can Send Notifications?
How to Send Notifications?
How to Receive Notifications?
Learn more about Notification