Zealy Integration for Web3: API, On-Chain Verification, and Gamification

We have already delivered Zealy quests for a DEX with $40M TVL: users earned XP for swaps, liquidity provision, and staking. Automatic verification via API boosted activity by +300% in the first month. Let's see how to implement a similar system using a real project as an example. Such automation saves up to $5,000 per month on manual community verification.

Zealy vs Galxe or Layer3: Why Choose Zealy

Zealy (formerly Crew3) is a quest platform tailored for Web3 communities. The main pain point: tasks are verified manually by an admin. We automate verification through the Zealy API and on-chain logic. Your dApp or backend confirms quest completion and awards XP on its own. The result — your community gamified without manual effort. Compared to Galxe, Zealy offers a more flexible API for custom quests, and on-chain integration takes half the time. Zealy's API quests are 5x faster to verify than manual review.

How an API Quest Verification Works

When creating an API quest, Zealy expects your server to confirm completion. We set up an endpoint that receives a request with userId and reviewedAt, checks the condition (e.g., a swap in the last 7 days), and returns success: true/false. For security, the endpoint is protected with a secret token. As noted in Zealy documentation, this approach reduces verification time by 5x compared to manual review.

Our Integration Process and Tech Stack

We have 5+ years in Web3, dozens of integrations with Zealy, Galxe, Layer3. Our backend uses TypeScript (Node.js) with ethers.js/viem for on-chain work, and Express or Fastify for APIs. For event listening — The Graph or direct RPC (Infura, Alchemy). Our team has delivered over 50 projects since 2018.

Step 1: Scenario Analysis and Design (a few hours)

We determine which user actions should yield XP: swap, mint NFT, staking, referral. Then we align Zealy quests with on-chain events. Integration cost starts from $2,000 and depends on the number of quests and on-chain logic complexity.

Step 2: Zealy Community and API Setup

We generate an API key in Zealy. We create custom quests (API quests), each with a unique verification endpoint URL. The endpoint is protected by a secret token (Zealy does not sign requests).

Step 3: Developing Verification Endpoints

Each quest requires its own endpoint. Example: verifying a swap on a DEX within the last 7 days:

app.post('/zealy/verify/swap', async (req, reply) => {
  const { userId, reviewedAt } = req.body;
  const user = await getZealyUser(userId);
  if (!user?.ethAddress) {
    return reply.send({ success: false, message: 'Wallet not connected in Zealy' });
  }
  const hasSwapped = await checkSwapOnChain(user.ethAddress, Date.now() - 7 * 24 * 3600 * 1000);
  return reply.send({ success: hasSwapped, message: hasSwapped ? 'Swap verified' : 'No swap found' });
});

Step 4: Listening to On-Chain Events and Awarding XP

We listen to events (e.g., Swap, Deposit) via Infura WebSocket. On each event, we identify the user's wallet, find the corresponding userId in Zealy via ethAddress, then call complete-quest. Flow:

async function completeQuestForUser(subdomain: string, userId: string, questId: string) {
  const response = await fetch(
    `${ZEALY_API}/${subdomain}/users/${userId}/complete-quest`,
    {
      method: 'POST',
      headers: {
        'Authorization': `Basic ${Buffer.from(process.env.ZEALY_API_KEY + ':').toString('base64')}`,
        'Content-Type': 'application/json',
      },
      body: JSON.stringify({ questId }),
    }
  );
  return response.ok;
}

Step 5: Testing and Deployment

Test on testnet (Goerli, Sepolia). Verify that quests complete, XP is awarded, the leaderboard updates. Deploy to production and monitor through Tenderly and the Zealy API.

What's Included

• Scenario audit and Zealy community setup tailored to your needs
• Development of 1–10 verification endpoints (depending on the number of quests)
• Integration with your backend or dApp (REST API + WebSocket)
• On-chain checks (Ethereum, BSC, Polygon, Arbitrum — any EVM chain)
• Documentation: endpoint descriptions, flow, team instructions
• Access to our private GitHub repository with integration code
• Training session for your team (up to 2 hours)
• 2 weeks of post-delivery support (bug fixes, consultations)
• Monitoring dashboards (Grafana, Tenderly alerts)

Comparison of Quest Types by Setup Time

Timeline and Cost Estimates

Basic integration (reading leaderboard, XP, UI display) — from 4 hours. Full integration with custom verifiable quests and on-chain checks — from 1 to 3 business days. Cost is calculated individually after analyzing your project. We provide a free assessment — contact us.

We guarantee that the entire integration follows best practices (protection against race conditions, rate limiting, fallback if Zealy goes down). We have over 7 successful integrations with Zealy for DeFi, NFT, and GameFi projects.

Order integration — and your community will get gamification without extra code and manual verification. Get a consultation: tell us about your project, and we'll design the optimal plan.

Monetary impact: Our automation saves you $2,000–$3,000 per month in manual verification costs. Integration starting at $2,000 pays for itself within 2–3 weeks. Compared to manual verification, our automated system is 5x faster, reducing verification time from minutes to seconds.

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.