Notifications are the building blocks of communication across Web3. Check out how EPNS is building the communication layer of decentralized Web
Ethereum Push Notification Service (EPNS) is the world’s first decentralized communication & notification protocol for Web3.
Using the protocol, any smart contract, dApp, or backend service can send on-chain or off-chain notifications tied to the wallet addresses of users in a gasless, multichain, open, and platform-agnostic way.
Being an open communication middleware, notifications can be integrated and shown on any crypto wallet, mobile app, browser extension, or dApps enabling a native communication layer for Web3.0
How to EPNS (in 10 steps or less)
Any user who activates themselves on the protocol to send a notification is called a Channel.
In other words, a Channel is any service (protocol, dApp, or even web2 service) that wants to send notifications out to web3 usernames (wallet addresses).
A wallet address can create only one Channelon the protocol.
A channel is free to delegate (or revoke delegates) sending notifications functionality to any other wallet addresses on their behalf.
Creating a channel requires 50 DAI and Channel info (Channel name, Image, description, CTA) and some ETH too.
Channels can send notifications to their users(wallet addresses) in a number of ways including:
Backend SDK (Gasless, Best for automated logic from dApp / Backend)