Quest/Task Platform Development for Crypto Projects

Quest/Task Platform Development for Crypto Projects

We build quest platforms turnkey—from designing on-chain verification to deploying reward smart contracts. The client's main pain: how to prove a user completed a task without trusting their word? On-chain actions require transaction verification via RPC, while off-chain actions need OAuth integration. Any verification loophole opens the door for sybil attacks, where one user boosts their rating with hundreds of wallets.

In practice, verifying Ethereum transactions takes 2–5 seconds, and token balance checks can take up to 10 seconds during network congestion. For off-chain tasks like Twitter follow, verification time is under 1 second. However, fast verification doesn't guarantee protection against abuse—a comprehensive approach using snapshots and anti-sybil filters is required.

We use a combination of methods: for off-chain—OAuth 2.0 with PKCE (Twitter, Discord), for on-chain—RPC calls via publicClient with event confirmation. Each request is logged, and data is cached for 5 minutes to avoid redundant blockchain queries.

Task Verification: On-Chain vs Off-Chain

Off-Chain Tasks

Twitter follow, Discord join, email subscription—verification via OAuth:

• Twitter: OAuth 2.0 with PKCE, verification via Twitter API v2 (GET /2/users/:id/following)
• Discord: OAuth2 + Discord Bot API for checking server membership and role assignment
• Telegram: Telegram Login Widget + Bot API (getChatMember)

All this is server-side logic. OAuth tokens must be stored encrypted and refreshed—Twitter access token lives 2 hours.

On-Chain Tasks

This is more interesting and complex. Typical categories:

• Holder verification—user must hold X tokens or NFTs from a specific collection. Verification: balanceOf(address) call via RPC. Simple, but you need to handle the time check—balance might have existed at snapshot time but not now.
• Transaction verification—user performed a swap, provided liquidity, made a bridge. Verification via indexer or RPC:

// Check if the address did a swap on Uniswap v3 in the last N days
const logs = await publicClient.getLogs({
  address: UNISWAP_V3_ROUTER,
  event: parseAbiItem('event Swap(address indexed sender, address indexed recipient, ...)'),
  args: { recipient: userAddress },
  fromBlock: BigInt(fromBlock),
  toBlock: 'latest',
})
const completed = logs.length > 0

• Contract interaction—user called a specific function of your contract. The most reliable method: emit an event in the contract, index it.

Comparison of On-Chain and Off-Chain Verification

How to Protect Against Sybil Attacks?

The main problem with quest platforms is sybil attacks. One person creates 1000 wallets, completes all tasks, collects rewards. We use a combination of methods:

• Gitcoin Passport—score based on Web2 and Web3 activity. API: GET /registry/score/:address. A score threshold (e.g., 15+) eliminates most sybil accounts.
• Proof of Humanity / Worldcoin—biometric proof of unique human. More reliable but creates friction for users.
• On-chain activity score—check wallet age, number of transactions, ETH/asset holdings. A new wallet with zero history is a red flag.
• Rate limiting by IP + fingerprint—not perfect but filters out lazy bot operators.

System Architecture

Backend

REST API (Next.js API routes or Express)
├── /api/quests — list quests, status
├── /api/verify/:taskId — verify a specific task
├── /api/claim — claim reward after completing all tasks
└── /api/leaderboard — top users by XP

Database — PostgreSQL:

• users: address, twitter_id, discord_id, passport_score
• quests: id, title, reward_type, reward_amount, requirements JSON
• task_completions: user_id, task_id, verified_at, proof JSON
• rewards_claimed: user_id, quest_id, tx_hash

Smart Contract for Rewards

If the reward is tokens or NFTs, a contract is needed:

contract QuestRewards {
    mapping(address => mapping(uint256 => bool)) public claimed;
    
    function claimReward(
        uint256 questId,
        bytes32[] calldata merkleProof
    ) external {
        require(!claimed[msg.sender][questId], "Already claimed");
        require(
            MerkleProof.verify(merkleProof, questRoots[questId], 
                keccak256(abi.encodePacked(msg.sender))),
            "Invalid proof"
        );
        claimed[msg.sender][questId] = true;
        token.transfer(msg.sender, questRewards[questId]);
    }
}

Merkle tree approach: the backend compiles the list of eligible addresses, calculates the Merkle root, and publishes it on-chain. The user receives a Merkle proof from the server and claims themselves, paying gas. This reduces server load and decentralizes claiming. More about Merkle tree can be read on Wikipedia.

Frontend

Key screens:

• Dashboard — active quests, progress, accumulated XP
• Quest detail — list of tasks with statuses (locked/available/completed/claimed)
• Leaderboard — top participants, can be weekly/all-time
• Profile — reward history, connected socials

UX detail: task verification status should not be synchronous. User clicks "Verify" — show spinner, backend makes the request, checks on-chain/off-chain data, returns result. Typical time — 2–5 seconds for on-chain verification.

What's Included in Turnkey Development?

Our engineers have 10+ years of experience in smart contract development and over 50 successful DeFi and NFT projects. We use Foundry for contract testing and Tenderly for monitoring.

Estimated Timelines

Basic system with a few task types and verification — from 1 week. Full platform with anti-sybil, Merkle-based claiming, and integrations — up to 2 weeks. We'll give an exact estimate after analyzing your requirements.

Common Mistakes in Quest Platform Development

• Using only off-chain verification without on-chain — users cheat the system.
• Lack of snapshot logic — rewards go to those whose balance existed for a second.
• Synchronous verification — user waits for response, interface freezes.
• No sybil protection — rewards go to bots.

Avoiding these problems requires proper architecture and an experienced team. If you are developing a crypto project and want to implement a quest system, contact us for a free project assessment.

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.