Book a call, opens in a new tab

Case study · Reward platforms

One reward engine, two live products: Bondkoin Labs and Voltara

Bondkoin Labs and Voltara are reward platforms on BNB Chain. A user taps once to open a 24-hour reward window, points build up on the server, and verified users convert them into the product's own BEP-20 token, paid out on-chain. We built the engine both run on: the API, the web app and the admin and finance console, plus a React Native (Expo) mobile app.

Evidence: Named client. Status: In production.See the drawing 

Visit live site: bondkoinlabs.com , opens in a new tabVisit live site: voltaragrid.com , opens in a new tabLive · checked 26 Sep 2026

Named client: client work shown by name, with the client's permission.In production: we've confirmed it's live. We show the date we checked.

Sheet
W-02 One engine, three paths
Clients
Bondkoin Labs · Voltara
Live at
bondkoinlabs.com · voltaragrid.com
Industry
Consumer reward platforms (Web3)
Engagement
Since Aug 2026 · in active development
Evidence
Named client
Status
In production
Tokens
$BONDKOIN and $VLTR: each client's own BEP-20 token on BNB Chain
Bondkoin Labs
55,000+ monthly active usersClient figure from the Bondkoin Labs admin dashboard, Sep 2026
Stack
NestJS · Prisma + PostgreSQL · Redis · ethers.js · Next.js (PWA, next-intl) · React Native (Expo)

Two products, one engine

Both are live on BNB Chain, each with its own brand, token and domain. The engine underneath is shared: accounts, rewards, payments, KYC, payouts and the admin console.

The Bondkoin Labs landing page: a dark reward console showing points accumulated and a tap button.
The Bondkoin Labs landing page on a phone, with the headline, the start button and the KYC and payout notes.

Reward platform on BNB Chain

Bondkoin Labs

The engine as a daily reward platform for $BONDKOIN, a BEP-20 token on BNB Chain. A user taps once to open a 24-hour reward window. Points build up on the server and convert to $BONDKOIN after KYC and an admin's review.

55,000+ monthly active users

Client figure from the Bondkoin Labs admin dashboard, Sep 2026

  • Paid boosters, bought with USDT or BNB and verified on-chain
  • Referral tiers and bounty tasks: a daily wheel, a quiz and social tasks
  • A leaderboard, and a marketplace page in preview
  • A web app and a React Native mobile app, in English, Chinese and Korean
Visit live site: bondkoinlabs.com , opens in a new tab
The Voltara landing page: “Build the rig. Hold the grid.”, beside a rig console with grid stability and six empty slots.
The Voltara landing page on a phone, with the headline, two buttons and the note that the rig is a simulation.

Reward game on BNB Chain

Voltara

The same engine with a game on top, for $VLTR, a BEP-20 token on BNB Chain. Users build a six-slot rig from cores, cooling and power, and a grid-stability score multiplies their reward rate: the better the rig is cooled and powered, the higher it goes. The heat and the power are a simulation: there is no hardware and no electricity cost.

  • Six slots, 30-day parts and a grid-stability score
  • Grid events, squads and a player market
  • A weekly blueprint challenge, with every build re-checked on the server
  • KYC and direct BEP-20 payouts, from the same engine
Visit live site: voltaragrid.com , opens in a new tab
The Voltara rig section: “Six slots. Two ceilings. One number.”, beside a rig at full grid stability with one core installed.
The rig section: one core installed, at full grid stability.

Captured from the live sites on 26 Sep 2026. The words on these pages, “mining” among them, are the clients' own, not ours.

The problem

The client wanted a daily reward product with a real token at the end of it: points that build up on a schedule, paid boosters bought with crypto, referral tiers, social tasks, mandatory identity checks and payouts an admin approves. It also had to hold up against multi-accounts, shared devices, bot farms and fake referrals.

The technical crux was the two places where points meet real value. A booster payment accepted by mistake hands out a paid booster for free. A payout approved for a farmed account sends real tokens to the wrong person.

Engineer view

Points live in the platform's ledger, counted in integer milli-points. The engine touches BNB Chain in two places only: it reads booster payments (USDT or BNB), and it sends the product's BEP-20 token when a payout is approved.

Constraints

  • Real crypto in, for boosters (USDT or BNB), and a real BEP-20 token out, for payouts.
  • Mandatory KYC, reviewed by a person.
  • Abuse as the default: multi-accounts, shared devices, bot farms and fake referrals.
  • Web, mobile and admin on one API, in English, Chinese and Korean.
  • Two branded products on one engine.

How we built it

Everything that decides a reward or moves value sits behind the API, in small parts that can be tested without a chain. The chain is touched in two places: payments in, payouts out.

W-02One engine, three paths

Evidence: Named client. Status: In production.Redrawn; details changed to protect the client

One engine, three paths: the daily reward, a booster payment and a payout.

  1. All reward maths lives in one place, tested on its own.Deterministic, side-effect-free functions in integer milli-points, so balances never drift by a rounding error.
  2. A payment counts only when the chain agrees.Refuses failed or unconfirmed transactions, the wrong recipient, sender or token, underpayment, and transfers mined well before the purchase began.
  3. Identity and abuse checks come before any payout.KYC with manual review; step-up email code; captcha with the action and hostname checked; sign-up caps per /24 subnet; device fingerprints.
  4. A person approves each payout.Approve sends the token; reject refunds the points. The finance view is scoped per payment collector.
  5. Off-chain, testnet or mainnet is a setting, not a code change.Every module calls one payout interface; the mode is chosen by configuration.

Key decisions

Decision 1

Keep the reward maths in one pure module

Decision
Every reward rule lives in one module of deterministic functions with no side effects, counting in whole milli-points.
Alternative
Work rewards out wherever they're needed, in floating point.
Why
One place to test, and to change when the client changes a rule. Whole numbers mean balances never drift by a rounding error.
Engineer view

The 24-hour claim window caps accrual and gates the next tap. The rate combines the base rate, active boosters and the referral tier. The rules mirror the written spec, and unit tests cover the engine.

Decision 2

Accept a payment only when the chain agrees

Decision
A booster activates only after the platform reads the payment from BNB Chain and it passes every rule. Reading the chain and deciding are kept apart.
Alternative
Trust the transaction hash the user submits, or have an admin check each payment by eye.
Why
This is money code: a false accept gives a paid booster away. Each rule closes one specific way that could happen.
Engineer view

The chain reader only reports what the chain says. The payment rules, pure and unit-tested without a chain, refuse a failed or unconfirmed transaction, the wrong recipient, a sender other than the wallet bound when the purchase started, the wrong token, an underpayment, or a transfer mined more than 30 minutes before the purchase began. Overpayment is accepted. Payments can be spread across several collector wallets.

Decision 3

Put identity and abuse checks in front of every payout

Decision
Payouts need an approved KYC, a fresh email code and an admin's approval, and sign-ups meet abuse checks before any points build up.
Alternative
Rely on KYC alone.
Why
Each check closes a different cheap trick: throwaway emails, one person with many accounts, scripted sign-ups, referral farms.
Engineer view

Captcha with the action and hostname checked; sign-up caps per /24 subnet, not just per address; device fingerprints; a blocklist of throwaway email domains; Gmail dot and +tag aliases folded into one mailbox; step-up email codes for login and withdrawals; a ranked list of suspected referral farmers; and a KYC reviewer who sees how crowded the applicant's network is.

Payouts follow published rules: points convert to the product's token at a fixed ratio, with a minimum balance and one request a week. Each request waits in an admin queue: approving it sends the token on BNB Chain, rejecting it refunds the points. The admin console has its own sign-in and role permissions, and the finance view shows each payment collector only its own money.

Engineer view

The payout layer is one interface with three modes, off-chain, testnet and mainnet, chosen by configuration, so switching never touches business logic. On mainnet a hot wallet sends the BEP-20 transfer. Admin tokens are their own type: a user's token is refused on every admin route.

What we deliberately didn't build

Mining. Nothing here mines cryptocurrency: points build up on a server-side schedule, and the only on-chain parts are the crypto payments for boosters and the BEP-20 token payouts. The token contracts are the clients' own.

What we delivered

  • The APIAccounts, the reward engine, boosters, referrals, a leaderboard, tasks, withdrawals, the payout layer, KYC, support, email codes and health checks, on 14 data models.
  • Payment verificationBooster payments in USDT or BNB, read from BNB Chain and checked by pure, tested rules.
  • Abuse defencesCaptcha, sign-up caps per /24 subnet, device fingerprints, throwaway-email and alias checks, step-up email codes and a referral-farm ranking.
  • The web appA Next.js progressive web app with 18 routes, the admin and finance console included, in English, Chinese and Korean.
  • The mobile appReact Native (Expo), on the same API and message catalogue as the web app, with KYC camera capture and a notification centre.
  • The admin and finance consoleUsers and their referral trees, KYC review, the withdrawal queue, per-country figures and a finance view scoped to each payment collector.
  • A deploy pipelineFrom GitHub Actions to AWS, behind Nginx with Let's Encrypt.
  • Unit testsAround the reward maths, the payment rules, the abuse guards and the admin permissions.

Result

In productionBoth products are live, at bondkoinlabs.com and voltaragrid.com, checked 26 Sep 2026. We make no claim about app-store listings.

Bondkoin Labs

55,000+ monthly active users

Client figure from the Bondkoin Labs admin dashboard, Sep 2026

2live products on one engine
3languages: English, Chinese and Korean
14data models
18web routes, admin included

No token prices, yields, earnings or returns here, and no user figures except the one Bondkoin Labs reported, with its source.

Building a reward or loyalty product?

Points, tokens, payouts, and the abuse that comes with them? Tell us what you're planning, and we'll sketch how we'd build it on the call.

Book a 30-min call, opens in a new tabSend a project brief

Or message us:WhatsApp, opens in a new tab

WhatsApp:

Related services

Next: BlocksMaples: a P2P crypto marketplace with USDT escrow