Introduction
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)

  1. 1.
    Any user who activates themselves on the protocol to send a notification is called a Channel.
  2. 2.
    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).
  3. 3.
    A wallet address can create only one Channel on the protocol.
  4. 4.
    A channel is free to delegate (or revoke delegates) sending notifications functionality to any other wallet addresses on their behalf.
  5. 5.
    Creating a channel requires 50 DAI and Channel info (Channel name, Image, description, CTA) and some ETH too.
  6. 6.
    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)
    • Showrunners Framework (Scaffold / Gasless, Best for automated logic via scaffold backend)
    • Smart contract to Smart contract (requires gas, Best for instant on-chain events, piggybacks on an on-chain transaction via Interface ABI call)
    • Manually from EPNS dApp (Gasless, Best for manual logic)
  7. 7.
    Users can gaslessly opt-in to receive notifications from these Channels. See the entire walkthrough here.
  8. 8.
    Opted-in users are called subscribers of the Channels. Subscribers of the Channel receive notifications from those Channels in their Inboxes.
  9. 9.
    Non-opted users or non-subscribers of the Channel aren't alerted when they receive a notif from a non-subscribed channel, instead, it lands in their spam folder.
  10. 10.
    Currently, we have Staging and Prod dApp that interfaces with EPNS Protocol to enable communication & notifications.
Copy link