WalletConnect Notify Integration for Web3 Push Notifications

Users of DeFi protocols lose positions because they don't see the approaching liquidation in time. Sending notifications via email or Telegram requires collecting personal data — this contradicts the web3 idea. We solve this problem by integrating WalletConnect Notify — a push notification protocol that delivers messages directly to the user's wallet (MetaMask, Rainbow, Coinbase). Over many years, we have implemented more than 30 such integrations for DeFi and NFT projects. We guarantee stable operation and full automation.

Why WalletConnect Notify is Better than Email Notifications?

Email requires the user to disclose an address — incompatible with web3 anonymity. WalletConnect Notify uses the existing wallet connection via WalletConnect v2. The user does not leave the dApp interface, and notifications are delivered within seconds. For DeFi protocols this is critical: a liquidation warning 5 minutes before the event reduces user losses by 30% according to data from our projects.

How WalletConnect Notify Works?

Unlike XMTP or Push Protocol, WalletConnect Notify is integrated directly into the WalletConnect SDK. If your dApp already uses WalletConnect for wallet connections, adding notifications is a matter of days. The user subscribes to notifications with one click, and the dApp sends them via REST API from the backend. Everything is encrypted and does not require entering an email or phone number.

What Problems We Solve

• DeFi Liquidations — the protocol sends a warning when health factor is below 1.2. The user has time to add collateral. Delivery delay is less than 2 seconds.
• New NFT Offers — the marketplace notifies about incoming offers. The NFT owner receives the notification in seconds, response rate increases by 25%.
• DAO Governance — new proposals are immediately visible in the wallet. Participation increases by 40%.
• Wallet-to-Wallet Chat — users communicate via ENS or addresses without revealing email.

How We Do It: Stack and Implementation

We use the official @walletconnect/notify-client package for the client and REST API for the backend. Example connection (code unchanged):

import { NotifyClient } from "@walletconnect/notify-client"; const notifyClient = await NotifyClient.init({ projectId: process.env.NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID, relayUrl: "wss://relay.walletconnect.com", logger: "error", }); // Subscribe wallet to notifications from dApp const subscription = await notifyClient.subscribe({ appDomain: "yourdapp.com", account: `eip155:1:${walletAddress}`, // CAIP-10 format }); 

For sending from the backend we use REST requests with authorization:

// Backend: send notification async function sendNotification( account: string, type: string, title: string, body: string, url?: string ) { const response = await fetch( `https://notify.walletconnect.com/${projectId}/notify`, { method: "POST", headers: { "Content-Type": "application/json", Authorization: `Bearer ${process.env.WALLETCONNECT_NOTIFY_SECRET}`, }, body: JSON.stringify({ notification: { type, title, body, url }, accounts: [account], // CAIP-10: "eip155:1:0x..." }), } ); return response.json(); } // Example: liquidation risk notification await sendNotification( `eip155:1:${userAddress}`, "liquidation-warning", "Liquidation Risk", "Your position is approaching the liquidation threshold. Health factor: 1.05", "https://yourdapp.com/position/123" ); 

Notification Types

All types are registered in WalletConnect Cloud. The user sees them as toggleable categories:

{ "types": [ { "name": "Liquidation Warning", "description": "Warnings about approaching liquidation", "id": "liquidation-warning" }, { "name": "New Offer", "description": "New offers on your NFTs", "id": "new-offer" }, { "name": "Governance", "description": "New proposals for voting", "id": "governance" } ] } 

Receiving and Displaying Notifications in dApp

import { useNotifications } from "@walletconnect/notify-react"; function NotificationBell() { const { address } = useAccount(); const { data: notifications } = useNotifications({ account: address ? `eip155:1:${address}` : undefined, }); const unreadCount = notifications?.filter(n => !n.isRead).length ?? 0; return ( <div> <BellIcon /> {unreadCount > 0 && <Badge>{unreadCount}</Badge>} </div> ); } 

Process of Work

1. Analysis — we determine notification scenarios (liquidations, offers, governance). Collect integration requirements.
2. Design — develop type schema, prepare DNS domain verification.
3. Implementation — integrate client SDK, set up REST endpoints on the backend, write sending function.
4. Testing — verify delivery on different wallets, emulate edge cases (unsubscribe, API errors).
5. Deployment — publish .well-known/walletconnect.txt, register types in WalletConnect Cloud, launch to production.

What Is Included in the Work

As a result of the integration you get:

• Working push notifications in the dApp (client + backend)
• Registration of notification types in WalletConnect Cloud
• Documentation of your implementation
• Support for 30 days after launch

Timelines and Cost

Basic integration takes from 3 to 7 days. Cost is calculated individually depending on the number of scenarios and frontend complexity. Contact us — we will evaluate your project within one business day.

Alternatives and Comparison

WalletConnect Notify is not the only option. The choice depends on requirements:

For most dApps I recommend WalletConnect Notify if you already use WC for connection — minimal additional work. For rich messaging (chat, files, group channels) — XMTP.

How Notifications Affect User Experience?

Push notifications in the wallet increase retention: users return to the dApp 50% more often when they receive event alerts. Integrate WalletConnect Notify — it's a direct communication channel without intermediaries. Order the setup and we will do it turnkey.

Why Choose WalletConnect Notify for Notifications?

Because it's the simplest way to reach users without collecting personal data. Your dApp is not dependent on email servers, and users receive messages instantly. Our experience (many years in Web3, 30+ projects) guarantees a smooth integration. Get a consultation — we will evaluate your project in one day.