TurboFlow Trading Competitions: How They Work

TurboFlow is not a perp DEX, and that is the whole point of it. It runs binary up/down predict markets — events contracts — where you pay a USDT-denominated premium, pick a direction and a duration, and the contract settles at expiry. A win pays your premium multiplied by a locked return rate, plus the stake back; a loss burns the premium. There is no position to manage, no leverage to select and no funding to pay.

Scoring a competition on a venue like that requires deciding what "volume" even means, and the answer Voltrade landed on is the reason this page exists.

What the venue is good at

The venues directory lists TurboFlow as a predict-market venue with a live universe currently covering three symbols: BTC, ETH and XAU. That is a deliberately small surface, and it suits the format — a binary contract on gold or bitcoin over a short duration is a clean directional bet, and the return rate is locked at placement rather than moving against you.

Voltrade's integration here runs through a partner API rather than a public chain read, and TurboFlow's user base largely sits on Solana addresses rather than EVM ones.

How Voltrade tracks your TurboFlow volume

Volume is the premium, counted at placement. Each predict order's usdt_value — the USDT premium you committed — credits your wallet on the day the order was created. Settlement never moves volume between days, which matters on a venue where a contract placed at 23:58 can expire minutes into the next day.

Three rules follow from that choice, and they are the fair ones:

• Cancelled orders are excluded, because the premium is refunded and nothing was ever at risk.
• Pending orders count, because the premium is committed the moment the order exists. If you cancel while the day is still open, the next sync tick self-corrects.
• Payout is not volume. The venue's payout field is a gross figure — stake returned plus profit on a win, zero on a loss — so it is not a PnL number and it is not what the leaderboard counts.

The API is Ed25519-signed per request. Voltrade reads GET /platform/user/predict-orders for each participant wallet using a partner API key. The scheme builds a canonical string from method, path, timestamp and access key, hashes it with HMAC-SHA256, then signs the digest with an Ed25519 private key. Because the HMAC key material can be interpreted more than one way, the client implements each candidate interpretation and ships a probe script that confirms which one the API accepts, so the variant is pinned per environment rather than assumed. The confirmed variant keys the HMAC with the raw 32 bytes hex-decoded from the API key, lowercased in both the header and the signing message.

One day bucket, one API window. The endpoint filters on created_at with a maximum window of 24 hours — which maps exactly onto Voltrade's start-anchored 24-hour competition days. Every venue on the platform uses start-anchored days as a cross-venue invariant; on TurboFlow that convention happens to line up 1:1 with the venue's own hard limit, so each competition day is precisely one API window.

Deduplication is mandatory, not defensive. Two independent mechanisms in the API re-serve the same order. The window filter is inclusive on both ends, so adjacent day buckets share a boundary second. And the offset pagination walks newest-first, so an order placed mid-walk shifts every later page down and re-serves rows already seen. Neither can skip an order — inserts only ever happen at the top — but both duplicate, and an undeduplicated sum would over-credit an active trader. Every multi-call fetch funnels through one dedupe. The documented item schema carries no order id, so the dedupe key falls back to a composite of placement time, pair, premium and duration, which is unique unless the same wallet places two identical orders in the same millisecond on the same pair.

Addresses are passed through verbatim. The venue matches EVM addresses case-insensitively but everything else exactly, so only 0x-form addresses are normalised. A base58 Solana address is never lowercased — doing so would silently match nothing.

Eligibility: wallet only, either network

There is nothing to link. You register with the wallet you trade on TurboFlow with, and that wallet is the tracking key — the same model as Lighter and Convallax. Because the venue spans both networks, TurboFlow registration accepts either a Solana or an EVM wallet: the connected wallet as-is, or any verified wallet on either network already linked to your account.

What kinds of competitions run here

Volume competitions on committed premium. Since the premium is real USDT rather than leveraged notional, TurboFlow competitions score at the spot rate of 1 VXP per $1, not the 0.1 rate applied to perpetual notional. That makes a dollar of TurboFlow premium worth ten times a dollar of perp notional in points terms — which is correct, because a dollar of premium is a dollar genuinely put at risk.

Competitions can scope specific symbols, in which case only orders on those symbols count, resolved the same way the challenge engine resolves markets. A day locks three hours after it ends, and recently-ended competitions keep settling for a further 30 hours. Once a day's row is frozen, its API window is never re-read.

How to enter

Connect a wallet on Voltrade — Solana or EVM — register for the competition, and place predict orders on TurboFlow with that same wallet. Volume counts from your registration, and the competition's daily windows roll on its start hour rather than at midnight.

Honest notes and limitations

• TurboFlow competitions are admin-only by construction. Self-serve creators on Voltrade can only create on-chain token competitions, so selecting TurboFlow as the venue is a platform-side action. This is structural in campaign creation, not a policy setting.
• The market universe is small. Three symbols at present. Check the live list on the competition page rather than assuming a pair is in scope.
• Committed premium is the metric, not accuracy. A volume competition here rewards the size and count of the bets you place, not whether they win. If you want profit scored instead, that is what PnL challenges are for — see volume vs PnL competitions for the difference.
• Signing is environment-specific. The accepted signature variant is verified against each environment before it is trusted, which is a deployment concern rather than a trader one, but it explains why this integration is treated more cautiously than a public-chain read.