Blofin Trading Competitions: How They Work

Blofin is a centralised derivatives exchange, and its Voltrade integration runs through an affiliate reporting API rather than a per-user key. That produces the most idiosyncratic day-boundary behaviour of any venue on the platform — Blofin days do not start at midnight UTC — and it is worth understanding before you plan a competition around a daily cap.

What the venue is good at

The venues directory lists Blofin as a centralised exchange supporting both perpetual and spot markets, described as a derivatives venue with deep liquidity across BTC, ETH and altcoin perpetuals. Its Voltrade history is team-format: the platform has hosted a Blofin "War of Whales" team competition, which is a structure that suits a venue where volume is reported per invited account rather than per public address.

How Voltrade tracks your Blofin volume

Volume comes from Blofin's affiliate API endpoint /api/v1/affiliate/invitees/daily/info, which returns daily rows per linked UID with a single field: tradingVolume, denominated in USDT.

One aggregate, not a breakdown. That field is the entire figure. Spot and perpetual volume are not separated, and the endpoint offers no per-market filtering at all — so on Blofin competitions the campaign's trading-pair list is ignored rather than silently misapplied. If you see a Blofin competition on Voltrade, it is an all-activity competition by necessity.

The endpoint is queried UID-only. Rather than relying on the server-side window parameters, the sync requests the most recent 500 daily rows for a UID and filters the competition window client-side. Filtering locally against a known-good row set is the more defensive choice for anything that decides a payout, and it costs nothing here because the response is already bounded.

Blofin days start at 16:00 UTC. Every daily row's timestamp observed across every surveyed UID lands at exactly T16:00:00.000Z — midnight in UTC+8, Blofin's home timezone. A row stamped 2026-05-29 16:00 UTC aggregates trades made during [2026-05-29 16:00, 2026-05-30 16:00) and is not final until the following 16:00 UTC. This was confirmed the hard way: a bucket's reported volume was seen growing from 13,844.76 to 28,267.13 long after its own timestamp. An earlier version of the sync had the boundary backwards, closed those days a day early, and froze partial values.

The consequence for settlement is that a Blofin day only locks once max(competition-day end, the bucket's own 16:00 + 24h) + 3h has passed — bucket-aware, not clock-aware. And it produces one genuine edge case worth naming: trading between a competition's start and the first 16:00 UTC lands in a bucket labelled with the previous date, outside the day list, and is dropped. The operational fix is to start Blofin competitions at 16:00 UTC.

Per-day attribution can therefore shift by up to ~16 hours against calendar UTC, but competition totals are exact — nothing is double-counted and nothing is lost, as long as every bucket maps to a day inside the window. Do not compare a Blofin per-day column against another venue's expecting them to mean the same wall-clock hours.

Sub-invitees take a second path. The affiliate daily endpoint rejects sub-invitees with error code 800079, so those traders are scored from snapshot deltas instead: an hourly job records their lifetime totalTradingVolume, and each competition day's volume is the difference between the last snapshot at or before the day's start and the last one at or before its end, clamped at zero so an upstream correction cannot produce a negative day. Linking writes a snapshot immediately, so a trader always has a baseline from the moment they link even if the hourly job has a gap. Which path a trader takes is decided at link time and stored on their record.

This is the same architecture Lighter uses for its public volume counters — see Lighter trading competitions for the version of it that needs no linking at all.

Eligibility: link your Blofin UID

Registration for a Blofin competition is blocked until your Blofin UID is linked. You sign up on Blofin under Voltrade's affiliate code, then link the UID from your profile, and the UID becomes the tracking key for every Blofin competition you enter afterwards.

There are no API keys and no read credentials involved — the affiliate API reports on invited accounts, which is why the link is a UID rather than a key. It also means the invite relationship is what makes tracking possible: an account that was not invited through the platform cannot be read by this endpoint.

What kinds of competitions run here

Volume competitions on total reported activity, including team formats. Because market filtering is unavailable, competition design leans on the levers that do work: prize-pool structure, qualifying minimums, daily counted-volume caps and participation floors. How DEX trading competitions work walks through those structures — leaderboard tiers, pro rata, thresholds and lotteries — and how to read which one a competition is actually using.

Scoring uses the platform's standard rates: 1 VXP per $1 of spot volume and 0.1 VXP per $1 of perpetual notional, with perps discounted an order of magnitude because leverage makes notional cheap to manufacture. Since the Blofin figure is a single aggregate assumed to be futures volume per the venue's own documentation, treat the per-market breakdown on your Blofin dashboard as informational rather than as what is being scored.

How to enter

Connect and verify a wallet on Voltrade, link your Blofin UID from your profile, then register and trade. Volume is bucketed across the competition window, and the daily buckets follow Blofin's 16:00 UTC boundary as described above.

Honest notes and limitations

• You must have signed up under the affiliate relationship for the reporting endpoint to return your rows at all.
• Per-market scoping is impossible here. If a competition needs to reward one specific pair, Blofin is the wrong venue for it.
• Days are 16:00-anchored. If a daily cap matters to your strategy, plan around that boundary rather than around midnight.
• Competition creation on integrated venues is admin-side. Self-serve creators on Voltrade are restricted to on-chain token competitions.
• Fees are not scored. Voltrade counts reported volume, not fees paid. For the fee side of exchange selection see exchange fee rebates explained and the exchanges directory.