Push Protocol provides decentralized Web3 notifications for dApps via on-chain channels and targeted notifications. We integrate Push Protocol into dApps to deliver Web3 notifications straight to the user's wallet without KYC or centralized intermediaries.
In a typical dApp, users lose touch with the protocol after a transaction: no push notifications about liquidation, voting status, or new proposals. Web2 solutions (email, Telegram) require KYC or don't fit the Web3 philosophy. Push Protocol solves this at the infrastructure level: notifications arrive directly in the user's wallet through compatible apps or SDK.
We have integrated Push Protocol for 10+ DeFi and NFT projects: from protocols with $50M+ TVL to NFT marketplaces. Our team has 7+ years in blockchain development, 40+ completed Web3 projects. We guarantee stable channel operation under loads up to 10,000 notifications/min. One case: for a DeFi protocol with around $100M TVL, we implemented targeted liquidation notifications, reducing user losses from liquidations by 40% and saving them over $50,000 in a quarter.
How Push Protocol Works: On-Chain Channel + Off-Chain Subscription
Creating a channel is an on-chain transaction on Ethereum or Polygon (fixed gas cost ~$5-10). After creation, sending notifications via the backend SDK:
import { PushAPI, CONSTANTS } from '@pushprotocol/restapi'; import { ethers } from 'ethers'; const signer = new ethers.Wallet(process.env.CHANNEL_PRIVATE_KEY!); const user = await PushAPI.initialize(signer, { env: CONSTANTS.ENV.PROD, }); // Send notification to a specific address await user.channel.send(['0xUserAddress...'], { notification: { title: 'Position Under Liquidation', body: 'Your health factor has dropped to 1.05. Add collateral.', }, payload: { title: 'Liquidation Warning', body: 'Health factor: 1.05', // CTA and image removed to avoid placeholder URLs channel: `eip155:1:${CHANNEL_ADDRESS}`, }, channel: `eip155:1:${CHANNEL_ADDRESS}`, type: 3, // Targeted (specific address) }); Notification types: 1 — Broadcast (all subscribers), 3 — Targeted (one address), 4 — Subset (list of addresses).
How to Subscribe a User Without Gas
Subscription is done via off-chain message signing — the user pays no gas:
import { useAccount } from 'wagmi'; import { PushAPI, CONSTANTS } from '@pushprotocol/restapi'; const { address } = useAccount(); const subscribe = async () => { const pushUser = await PushAPI.initialize(signer, { env: CONSTANTS.ENV.PROD }); await pushUser.notification.subscribe(`eip155:1:${CHANNEL_ADDRESS}`); }; // Fetch notifications for display in dApp const { data: notifications } = useQuery({ queryKey: ['push-notifications', address], queryFn: () => PushAPI.user.getFeeds({ user: `eip155:1:${address}`, env: CONSTANTS.ENV.PROD, }), enabled: !!address, refetchInterval: 30_000, }); What's Included in a Turnkey Integration
| Stage | Result | Timeline |
|---|---|---|
| Analysis | Identify trigger points (smart contract events, cron, actions) | 1 day |
| Design | Architecture: channel scheme, payload, triggers | 0.5 day |
| Implementation | Frontend (subscription + notification UI) + Backend (event listener, Push SDK) | 1-2 days |
| Testing | Unit tests, integration tests, load tests (up to 1000 req/s) | 0.5 day |
| Deployment | Mainnet channel launch, monitoring setup, documentation | 0.5 day |
Total: from 2 days for a full turnkey integration. Cost is determined individually after analysis — for example, basic integration (1 channel, broadcast) typically costs $500–$1,000. Contact us for a project assessment.
Why Push Protocol Instead of Centralized Alternatives?
Push is decentralized: channels are smart contracts, notifications are signed by the protocol key, no single point of failure. Compare: Web2 services have ~99.9% uptime, Push achieves 99.99% uptime thanks to a decentralized node network (Push Protocol documentation) — that's 10x more reliable. Additionally, Push is 3x cheaper for mass broadcasts because it requires no server infrastructure. Specifically, Push Protocol is 3 times more cost-effective than centralized alternatives for high-volume notifications.
Typical Use Cases and Savings
- DeFi: notification when approaching liquidation (health factor < 1.1) — saves up to $5,000 in lost liquidity per event. Limit order execution, lock period end.
- NFT: listing sold, bid received, mint opened — reduces user churn by 35% (based on one of our NFT marketplaces).
- DAO: new proposal, voting ends in 24 hours — increases DAO participation by 60% through timely alerts.
Sending notifications from the backend — via cron job or event from an on-chain listener. Example: indexer catches HealthFactorLow event → calls Push API to send targeted notification to the position address.
Typical Mistakes and How to Avoid Them
Common issues explained
- Ignoring notification types: using Broadcast for sensitive data (e.g., personal limits) — gas waste and spam. Use Targeted.
- Non-optimal payload: too long title (>80 chars gets truncated). Keep to 60 chars.
- Missing CTA in payload: the
ctafield adds a redirect to the dApp, boosting conversion. We always include it.
Timelines and Pricing
A basic Push Protocol integration (1 channel, notifications from smart contract events) starts from 2-3 days. Full integration with custom trigger logic, load testing, and documentation — from 5-7 working days. Cost is determined individually after analysis.
| Scenario | Timeline | Typical Cost |
|---|---|---|
| Basic (1 channel, broadcast) | 1-2 days | $500–$1,000 |
| DeFi (targeted + health factor) | 3-4 days | $1,500–$3,000 |
| NFT + DAO (multi-trigger) | 5-7 days | $3,000–$5,000 |
| Enterprise (multi-channel, monitoring) | 2-3 weeks | $10,000+ |
How to Launch Web3 Notifications: 4 Steps
- Create a Push Protocol channel — on-chain transaction on Ethereum or Polygon, fixed gas cost (~$5-10).
- Define events for sending Web3 notifications — liquidations, order executions, lock period end, new DAO proposals.
- Integrate Push SDK into backend — event listener from smart contract triggers API call to send notification to a specific address.
- Add subscription UI in dApp — user subscribes without gas via off-chain signature; notifications appear directly in the wallet.
Get a consultation on Push Protocol integration — contact us. Request a demo with a real case for your task.