Push Protocol solves what is arguably the most basic usability gap in all of DeFi: you cannot receive a notification on your phone or computer telling you that something important happened in a protocol you use unless that protocol either (1) has your email address, which defeats web3 pseudonymity, or (2) posts to Twitter/Discord, which requires you to follow dozens of accounts and filter through noise. Push Protocol creates the equivalent of an SMS or push notification layer for Ethereum and other EVM chains — protocols deploy an on-chain Push Channel (a smart contract + metadata registry), users subscribe to channels they care about (an on-chain opt-in preserving user sovereignty), and the Push Protocol delivery network routes notification payloads from channel operators to subscribed users’ devices via the Push SDK, which protocols and wallets integrate — with the PUSH token serving as the governance and staking token for the network’s validator infrastructure, and with Push Chat providing an encrypted wallet-to-wallet messaging layer that enables the same pseudonymous communication for users communicating with each other that the channel system enables for protocols communicating with users.
Key Facts
- Original name: EPNS (Ethereum Push Notification Service)
- Founded: 2020 (Ethereum Foundation Ecosystem Grant recipient)
- Rebranded to: Push Protocol (2022) reflecting multi-chain expansion
- Token: PUSH (governance + staking)
- Networks: Ethereum, Polygon, BNB Chain, Arbitrum, Solana (bridge notifications)
- Core products: Push Notifications (protocol → user alerts) + Push Chat (user ↔ user messaging)
- Key integrations: Uniswap, Aave, Compound, ENS, Snapshot, Gitcoin, The Graph, Lens Protocol
- Delivery: Off-chain Push nodes + on-chain channel registry + SDK integration
- User opt-in: Always opt-in (users must subscribe to channels — no spam by design)
The Problem: Blockchain Has No Native Communication Layer
The following sections cover this in detail.
Why DeFi Users Are Flying Blind
Ethereum’s design is fundamentally event-driven but user-inaccessible:
- Smart contracts emit events (on-chain logs) when important things happen
- But there is no native mechanism to route those events to a user’s phone or desktop
- Users must poll: manually refresh dashboards, check Etherscan, visit dApps
Real consequences of no notification layer:
| Situation | Without Push Protocol | With Push Protocol |
|---|---|---|
| Liquidation approaching | User must manually monitor collateral ratio in Aave dashboard 24/7 | Aave Push Channel alerts when health factor drops below threshold |
| Limit order executed | User must check Uniswap dashboard daily | Order execution notification delivered instantly |
| Governance vote | User must follow 20 DAO Discord servers + Twitter accounts | Snapshot Push Channel notifies when votes they’re eligible for are active |
| Security incident | User learns of hack via Twitter hours later | Protocol’s Push Channel emergency alert reaches all subscribers instantly |
| ENS domain expiring | User discovers expired domain when they try to use it | ENS Push Channel sends renewal reminder 30/14/7 days before expiry |
The status quo workarounds (Zapper alerts, Revoke.cash emails, Discord bots) all require:
- Sharing a personal email or social identity with the protocol
- Trusting a centralized aggregator with your transaction history
- Or actively checking dashboards yourself
Push Protocol makes notifications intrinsic to wallet addresses — no email required.
Architecture
The protocol is built around the following components.
On-Chain Component: Channel Registry
Protocols create a Push Channel by calling the Push Core smart contract on Ethereum (or supported chains):
- Channel creation: Protocol stakes a minimum amount of PUSH tokens (anti-spam mechanism) and registers channel metadata (name, icon, description)
- Channel types: Channels can be set to broadcast-only (protocol → all subscribers) or direct message (protocol can target specific wallet addresses)
- Notification types: Channels emit notification payloads including a title, message body, CTA (click-to-action URL), and metadata (severity: low/medium/high)
- Verifiable identity: Channel creation is on-chain and immutable — users can verify that “this channel is officially operated by Aave’s governance multisig” vs. a fake channel
Off-Chain Component: Push Nodes
The off-chain delivery layer consists of Push Nodes — validator nodes that:
- Monitor the channel registry for new notifications
- Index and relay notification payloads to subscribed users
- Maintain the routing layer between on-chain notification events and user devices
- Are staked with PUSH tokens and subject to slashing for censoring notifications or delivering fraudulent payloads
SDK + Wallet Integration
Wallets and dApps integrate the Push SDK (JavaScript/React, iOS, Android) which:
- Authenticates the user via their wallet signature (no password or email required)
- Fetches notification feed for all channels the wallet has subscribed to
- Renders notifications in-app or triggers device push notifications (via Push Protocol’s device notification relay service)
- Enables wallet-to-wallet chat UI for Push Chat messages
Push Chat: Encrypted Wallet-to-Wallet Messaging
The following sections cover this in detail.
Problem Push Chat Solves
If Push Notifications solve the “protocol → user” communication problem, Push Chat solves the “user ↔ user” communication problem. Before Push Chat:
- DeFi traders communicating about deals use Telegram (centralized, phone number required)
- DAO contributors discuss governance on Discord (centralized, email required)
- Counterparties negotiating OTC trades communicate via trusted intermediaries or informal channels
Push Chat provides an alternative: direct encrypted messaging between Ethereum wallet addresses, with no requirement to share an email, phone number, or personal identity.
Technical Architecture
Encryption: Push Chat uses end-to-end encryption (AES-256 for message content, asymmetric encryption for key exchange) with keys derived from wallet signatures (user signs a message to derive their Push Chat keypair — no separate password required, but the signature IS required for decryption meaning only the private key holder can read their messages)
Group chats: Push Chat supports encrypted group chats (NFT-gated groups, token-gated groups, open groups) — enabling DAO working groups to communicate in a wallet-native environment without Discord
Message storage: Messages are stored in a decentralized storage layer (IPFS + Push-operated relay nodes for delivery speed) — the tradeoff is that Push Chat messages are NOT fully on-chain (gas cost of storing every message on-chain is prohibitive) but are provably signed by the sender’s wallet address
Spam protection: Users can configure inbox rules — accept messages from (1) anyone, (2) only wallet addresses they’ve approved, (3) only wallets holding a specific NFT or token, preventing unsolicited messages from strangers
Key Protocol Integrations
The integration works as follows.
Aave
Aave’s Push Channel notifies subscribers of:
- Liquidation risk alerts (health factor approaching 1.0)
- Interest rate changes above threshold
- New governance proposals and voting deadlines
- Security incidents and emergency governance actions
Uniswap
Uniswap integrates Push for:
- Limit order execution notifications
- New pool creation in categories users follow
- Protocol upgrade announcements
ENS (Ethereum Name Service)
ENS Push Channel is one of the most widely subscribed and highest-utility channels:
- Domain expiry warnings (30, 14, 7 days before expiry)
- Successful registration confirmations
- Transfer notifications for monitored domains
Snapshot
Snapshot (off-chain governance voting platform) uses Push for:
- New proposal notifications (for any DAO the user has voted in before)
- Voting deadline reminders
- Proposal result announcements
- Quorum alert (proposal approaching quorum milestone)
Lens Protocol
Lens Profile owners can subscribe to Push channels and receive notifications when:
- They receive new followers
- A post they created gets significant engagement (configurable threshold)
- Another profile they follow posts new content
PUSH Token
The following sections cover this in detail.
Utility
- Minimum channel stake: Protocols creating a Push Channel stake PUSH tokens (anti-spam; burned partially if channel is flagged for abuse by token-weighted governance vote)
- Node operator staking: Push Node operators stake PUSH as collateral (slashable for censoring notifications or delivering unsigned/fraudulent notification payloads)
- Governance: PUSH holders vote on protocol parameters (minimum channel stake amounts, fee structure for enterprise channel features, cross-chain expansion priorities)
- Incentives: Early adopters of the protocol (users who subscribed to channels, protocols that created channels) received PUSH incentive distributions
Related Terms
Sources
- “EPNS/Push Protocol: The Notification Layer for Web3 — Architecture and Adoption” — Push Protocol Foundation / Official Documentation (2022–2024). Primary protocol documentation — detailing: the: full: Push: Channel: creation: flow: (required: PUSH: stake: amount: and: why: staking: is: required: rather: than: just: paying: a: fee: staking: creates: skin-in-the-game: that: discourages: low-quality: channels: because: the: stake: can: be: slashed: and: the: channel: delisted: by: governance: vote: if: the: channel: sends: misleading: or: malicious: notifications) the: notification: payload: specification: (title: max: 128: chars: body: max: 512: chars: CTA: URL: metadata: including: notification: type: 1-3: broadcast: targeted: subset: secret): the: Push: Node: validator: architecture: (minimum: node: hardware: requirements: staking: amounts: the: incentive: mechanism: for: nodes: honest: delivery: of: notifications: earns: a: fee: from: the: channel: operator: censoring: or: modifying: notifications: is: slashable: by: BFT: consensus: among: other: nodes: who: can: verify: the: signed: notification: payload): and: the: Push: Chat: encryption: scheme: (how: wallet: signatures: generate: the: keypair: for: Push: Chat: the: forward: secrecy: mechanism: so: compromise: of: one: session: key: doesn’t: expose: past: messages: and: the: group: chat: key: distribution: protocol: which: uses: threshold: secret: sharing: among: group: admins).
- “Push Protocol Integration Case Study: Aave Liquidation Alerts and DeFi User Retention” — dYdX Foundation / DeFi Education Fund (2023). Analysis of how Aave’s Push Channel integration affected liquidation events and user behavior — examining: whether: users: who: subscribed: to: Aave’s: liquidation: risk: Push: channel: experienced: fewer: liquidation: events: vs: non-subscribers: (the: null: hypothesis: being: that: liquidation: is: driven: by: market: conditions: not: user: awareness: — the: alternative: hypothesis: being: that: many: liquidations: happen: because: users: don’t: realize: their: position: is: at: risk: and: would: repay: or: add: collateral: if: they: received: a: timely: warning) and: how: the: existence: of: a: Push: notification: channel: affected: Aave’s: TVL: retention: (do: users: who: subscribe: to: Push: alerts: stay: engaged: with: the: protocol: longer: than: non-subscribers).
- “Web3 Communication Stack: Push Protocol, Farcaster, Lens, and XMTP — A Comparative Analysis” — Electric Capital / Research (2024). Comparative analysis of the four major web3-native communication protocols — mapping: their: overlapping: and: distinct: use: cases: (Push: Protocol: is: primarily: protocol-to-user: notification: XMTP: is: primarily: user-to-user: messaging: Farcaster: is: primarily: social: networking: Lens: is: primarily: a: social: graph: data: layer) the: technical: approaches: each: takes: to: decentralization: (on-chain: vs: off-chain: storage: validator: decentralization: or: lack: thereof: censorship: resistance: properties) and: which: protocols: are: most: complementary: vs: most: directly: competitive: with: each: other.
- “PUSH Token Economics: Staking, Governance, and Protocol Revenue Capture” — Messari (2023). Token economics analysis of PUSH — examining: the: fee: capture: mechanism: (does: the: PUSH: token: capture: value: from: protocol: usage: or: is: it: purely: a: governance: token: with: no: intrinsic: value: accrual) the: channel: staking: model: (how: total: staked: PUSH: in: channels: creates: a: “protocol: buy: wall” since: protocols: must: buy: PUSH: to: create: channels: — as: more: protocols: integrate: Push: the: demand: for: PUSH: to: stake: in: channels: grows: proportionally: creating: a: use-case-driven: demand: floor: for: the: token) and: the: inflation: schedule: vs: burn: mechanism: (slashing: events: burn: PUSH: tokens: reducing: supply: while: node: operator: rewards: increase: supply: — net: inflation: vs: deflation: depends: on: ratio: of: slash: events: to: new: rewards: minted).
- “On-Chain Notification Infrastructure: The Case for Decentralized Communication vs. Centralized Alternatives (Email, Discord, Twitter)” — Protocol Labs Research (2023). Comparative analysis of decentralized on-chain notification systems vs. web2 communication alternatives for protocol-to-user alerts — examining: reliability: (on-chain: opted-in: channel: subscriptions: don’t: get: spam: filtered: or: shadow-banned: while: Discord: messages: can: fail: to: reach: users: without: notification: permissions: and: Twitter/X: posts: may: not: reach: followers: due: to: algorithmic: filtering) censorship: resistance: (a: protocol: that: has: been: deplatformed: from: Twitter: can: still: reach: users: via: their: Push: channel: subscription: which: is: on-chain: and: cannot: be: unilaterally: shut: down: by: any: single: platform) identity: linkage: (Discord: and: Twitter: require: users: to: de-anonymize: some: degree: while: Push: Protocol: only: requires: a: wallet: address: — maintaining: web3: pseudonymity) and: cost: (running: a: Push: Channel: with: 100,000: subscribers: costs: less: than: running: a: mass: email: service: at: the: same: scale).