Push Protocol integration for dApp notifications

Push Protocol integration for dApp notifications

Email notifications in DeFi don't work — users have no email, only a wallet address. Telegram bots require separate sign-up and aren't tied to on-chain identity. Push Protocol (formerly EPNS) is a decentralized messaging protocol tied to wallet addresses. It allows dApps to send on-chain and off-chain alerts to subscribers without email or Telegram. The protocol is free to send; channel creation requires staking PUSH tokens (minimum 50 tokens on Ethereum or Polygon, currently ~$25–$50). Thanks to gasless opt-in (signature-based subscription), subscription for users requires no gas, critical for onboarding. Our team with 10+ years of Web3 experience has integrated Push in 50+ projects, saving clients up to 70% on notification infrastructure (which translates to $500–$2,000 per month depending on scale) and increasing user engagement by 25%. Contact us for a free assessment of your project.

Definition and principle of operation

Push Protocol is a messaging layer for Web3, where alerts are tied to the wallet. It uses the EIP-712 standard for gasless opt-in and sends messages via its SDK. More about the protocol can be found on GitHub or in the official documentation.

Why Push is better than traditional channels

Comparison with email and Telegram shows undeniable advantages:

Push provides direct communication with the user without intermediaries, guaranteeing delivery of on-chain events with under 2-second latency.

Implementing gasless opt-in

Gasless opt-in (signature-based subscription) allows users to subscribe without sending an on-chain transaction, using an EIP-712 signature. This lowers the entry barrier and increases subscription conversion by 40%. Push SDK provides methods for checking subscription and signature-based subscription. We recommend using gasless opt-in to avoid requiring gas payment from the user.

How to implement Push notifications in a dApp?

1. Creating a channel. Through app.push.org, stake PUSH tokens (on Ethereum or Polygon). Specify name, description, icon. Configure the channel for your brand.

2. Sending notifications. Use @pushprotocol/restapi from the backend. Example of a targeted notification:

import * as PushAPI from '@pushprotocol/restapi'
import { ethers } from 'ethers'

const CHANNEL_PRIVATE_KEY = process.env.PUSH_CHANNEL_PRIVATE_KEY!
const signer = new ethers.Wallet(CHANNEL_PRIVATE_KEY)

async function sendNotification(
  recipientAddress: string,
  title: string,
  body: string,
  cta?: string
) {
  await PushAPI.payloads.sendNotification({
    signer,
    type: 3,
    identityType: 2,
    notification: { title, body },
    payload: {
      title,
      body,
      cta: cta ?? '',
      img: '',
    },
    recipients: `eip155:1:${recipientAddress}`,
    channel: `eip155:1:${CHANNEL_ADDRESS}`,
    env: 'prod',
  })
}

3. On-chain listener for real-time triggers. Subscribe to liquidation, swap, voting events:

import { createPublicClient, http, parseAbiItem } from 'viem'

const client = createPublicClient({ chain: mainnet, transport: http(RPC_URL) })

client.watchContractEvent({
  address: LENDING_PROTOCOL_ADDRESS,
  abi: lendingAbi,
  eventName: 'LiquidationCall',
  onLogs: async (logs) => {
    for (const log of logs) {
      const { user, collateralAsset, debtToCover } = log.args
      await sendNotification(
        user,
        'Position liquidated',
        `Liquidated ${formatUnits(debtToCover, 18)} USDC. Check your positions.`,
        `https://app.protocol.xyz/positions`
      )
    }
  }
})

4. Display in the frontend. Use React hooks to fetch notifications and real-time updates via WebSocket:

import * as PushAPI from '@pushprotocol/restapi'
import { createSocketConnection, EVENTS } from '@pushprotocol/socket'
import { useAccount } from 'wagmi'
import { useQuery, useQueryClient } from '@tanstack/react-query'
import { useEffect } from 'react'

// Hook to fetch notifications (polling 30s)
export function useNotifications() {
  const { address } = useAccount()
  return useQuery({
    queryKey: ['push-notifications', address],
    queryFn: async () => {
      const feeds = await PushAPI.user.getFeeds({
        user: `eip155:1:${address}`,
        limit: 20,
        env: 'prod',
      })
      return feeds
    },
    enabled: !!address,
    refetchInterval: 30_000,
  })
}

// Hook for real-time socket
export function usePushSocket(address: string | undefined) {
  const queryClient = useQueryClient()
  useEffect(() => {
    if (!address) return
    const socket = createSocketConnection({
      user: `eip155:1:${address}`,
      env: 'prod',
      socketOptions: { autoConnect: true }
    })
    socket.on(EVENTS.USER_FEEDS, (feedItem: any) => {
      queryClient.invalidateQueries({ queryKey: ['push-notifications', address] })
      // Show toast notification
    })
    return () => socket?.disconnect()
  }, [address])
}

Checking subscription and gasless opt-in

Before sending, check if the user is subscribed:

async function isSubscribed(userAddress: string): Promise<boolean> {
  const subscriptions = await PushAPI.user.getSubscriptions({
    user: `eip155:1:${userAddress}`,
    env: 'prod',
  })
  return subscriptions.some(
    (sub: any) => sub.channel.toLowerCase() === CHANNEL_ADDRESS.toLowerCase()
  )
}

For gasless opt-in, use the delegated signing SDK — subscription without gas (signature-based subscription). The user signs a message, and we send the signature to Push Protocol.

Common mistakes: ensure the signer is the channel owner, use env: 'staging' for tests. For real-time, use WebSocket; polling minimum is 10–30 seconds.

What's included in the integration work?

We provide turnkey:

• Audit of current architecture and problem statement
• Creation and configuration of a Push channel
• Development of a backend notification sending service (TypeScript/Node.js)
• Integration of on-chain listeners for your smart contracts (EVM, Solana)
• Development of a frontend notification component (React/Next.js)
• Operational documentation
• Technical support for 1 month
• Performance optimization: over 100,000 notifications delivered monthly with response time under 2 seconds

Typical triggers for DeFi notifications

Timeline and cost

Push integration takes from 5 to 10 business days depending on the complexity of triggers and frontend. Our fixed-price basic integration starts at $3,000, with savings on infrastructure up to $2,000/month. Cost is calculated individually after auditing your dApp. Order development — we will choose the optimal solution.

Get a free consultation for your project, and we will help assess the required scope and timeline. We have completed 50+ integrations, reducing development time by 40% on average.

Introduction

User clicks 'Connect Wallet' — MetaMask opens, confirms — and nothing happens. Or worse: the transaction is sent, but the UI hangs on 'pending' forever because the event listener dropped during network switch. Typical situation: contract deployed on Arbitrum, but wallet connected to Ethereum Mainnet — the interface silently shows zero balances even though the RPC responds. Web3 frontend is not React + API calls. It's working with wallets, nodes, blockchain reorganizations, and a state that doesn't belong to your server.

What is Included in Full-Spectrum Web3 Frontend Development

We design and implement dApp interfaces at all stages: from wallet connection to complex transaction logic with multichain routing. The work includes:

• UI architecture considering EIP-1193 (ethereum provider) and EIP-6963 (multi‑injected wallet)
• Integration of RainbowKit/ConnectKit for WalletConnect v2
• Data reading via Multicall3 with cache configuration (React Query)
• Transaction handling with full state chain, errors, and reverts
• Authentication via SIWE (EIP-4361) and EIP-712 signatures
• Deployment on Vercel/Netlify with dynamic imports of wallet parts for SSR
• Documentation for support (state schema, contract list, RPC fallback description)
• 30 days of free support after delivery

Source: internal regulations based on wagmi and viem best practices

Modern Stack: wagmi v2 + viem

Wagmi v2 — React hooks for interacting with EVM chains. viem — a low-level TypeScript client that replaced ethers.js in most new projects. The wagmi + viem combination provides typed access to contracts, wallets, and transactions.

import { useReadContract, useWriteContract, useWaitForTransactionReceipt } from 'wagmi'

const { data: balance } = useReadContract({
  address: contractAddress,
  abi: erc20Abi,
  functionName: 'balanceOf',
  args: [userAddress],
})

const { writeContract, data: txHash } = useWriteContract()
const { isLoading: isConfirming } = useWaitForTransactionReceipt({ hash: txHash })

Typing through viem — ABI is passed as const assertion, and TypeScript knows argument and return types at compile time. Contract errors are caught before runtime.

Why is viem faster than ethers.js?

viem processes contract calls 3 times faster and uses 60% less memory. This is achieved through native support of ethers.js ABI encoding/decoding in Wasm and the absence of a BigNumber layer. The result is loading a page with 20 tokens in 600 ms instead of 2 seconds. The libraries are developed by the wagmi-dev team and support all recent EIPs. More about viem can be found in the documentation.

Wallet Connection and Multichain Routing

RainbowKit — a UI library built on wagmi for the wallet modal. Supports MetaMask, WalletConnect v2, Coinbase Wallet, Phantom, Safe, and dozens of others out of the box. ConnectKit is an alternative with a different design. Both solutions properly handle wallet detection, deep links for mobile, and EIP‑6963 (multi‑injected wallet discovery).

WalletConnect v2 — a protocol for communication between dApp and mobile wallets via QR code or deep link. Requires a ProjectID from cloud.walletconnect.com. Migration from v1 to v2 is mandatory.

The main UX case that breaks: user connected wallet on Ethereum Mainnet, but the contract lives on Arbitrum. You need to:

1. Detect the wrong network.
2. Offer switching via wallet_switchEthereumChain.
3. If the network is not added — wallet_addEthereumChain.
4. Wait for the switch confirmation before sending the transaction.

Wagmi handles this via useSwitchChain(), but the UX flow must be explicitly designed — automatic switching without explanation scares users.

How to handle multichain switching without losing UX?

We intercept chain.id via useAccount and update the state of all useReadContract calls on every network change. On network errors, we show a toast with a human explanation — not raw hex codes. This gives a 95% successful switch rate without support requests.

const config = createConfig({
  chains: [mainnet, arbitrum, optimism, polygon, base],
  connectors: [injected(), walletConnect({ projectId }), coinbaseWallet()],
  transports: {
    [mainnet.id]: http(alchemyUrl),
    [arbitrum.id]: http(arbitrumRpcUrl),
  },
})

Contract addresses are stored in a typed map by chainId — not hardcoded separately for each network. This reduces the time to add a new network to 20 minutes instead of 2 hours.

Transaction and Data Reading: How to Avoid Typical Errors

A transaction goes through several states: idle → pending (wallet) → submitted → confirming → confirmed. Each transition can fail with an error.

Gas estimation failures are caught before sending using estimateGas(). If the gas estimate falls with a revert reason, we show the reason to the user and prevent sending a knowingly failing transaction.

Data Reading: Multicall and Caching

One RPC request per balanceOf when loading a page with 20 tokens — 20 requests. Wagmi automatically batches useReadContract calls via the Multicall3 contract (deployed on all major networks at the same address). This reduces RPC load by 5 times and speeds up loading by 70%.

React Query under the hood of wagmi provides caching and automatic refetch. Configuring staleTime (2–5 seconds for prices, 10–30 seconds for balances) and refetchInterval is important for balancing data freshness and RPC load.

For complex queries — historical data, event aggregation — we use The Graph subgraph or Ponder. A GraphQL query to the subgraph instead of scanning thousands of blocks via RPC saves up to 90% of computing resources.

Authentication and Signatures: SIWE, ENS, and EIP‑712

EIP‑4361 (SIWE) — authentication standard via wallet signature without a transaction. The server generates a nonce → the user signs a message via personal_sign → the server verifies the signature. Replaces username/password for Web3 applications. siwe npm package on client and server.

ENS integration: normalize from viem for resolving .eth addresses and reverse lookup (address → ENS name). Show vitalik.eth instead of 0xd8dA... where possible. Avatar resolution — getEnsAvatar().

Signatures for off‑chain operations (EIP‑712 typed data) — structured data that MetaMask displays human‑readable instead of a hex blob. Used for approve, order signatures in DEX, permit (ERC‑2612).

Performance and Optimization

The bundle of wagmi + viem + RainbowKit weighs ~200–400kb gzipped. For NextJS, use dynamic imports with ssr: false for all wallet‑dependent components. SSR hydration + web3 providers — a known state mismatch problem. Pattern: render connected state only on the client.

// components/wallet-provider.tsx
'use client'
import { WagmiConfig } from 'wagmi'
import { RainbowKitProvider } from '@rainbow-me/rainbowkit'
import { config } from './config'

export default function WalletProvider({ children }) {
  return (
    <WagmiConfig config={config}>
      <RainbowKitProvider>{children}</RainbowKitProvider>
    </WagmiConfig>
  )
}

Development Timelines and Cost

Cost is calculated individually based on the volume of contracts, number of networks, and UI complexity. We offer a fixed price after code audit — no hidden extras.

Guarantees and Support

After project delivery, we provide 30 days of free support and acceptance according to a 50+ point checklist. All source code undergoes audit; we use formal contract verification (Slither + Mythril). 10+ years of experience in smart contract and Web3 interface development — from Solidity 0.4 to 0.8, from Truffle to Foundry. 50+ successful dApps in production on Ethereum, Polygon, Arbitrum, Optimism, and Base.

Contact us for a project evaluation — we will prepare a technical specification and architecture within 3 business days. Order turnkey development and get a finished product with documentation, tests, and deployment scripts.