Open App
EN

Where the money goes, and what comes back.

The mechanism is simple enough to state in full. Doing so also makes clear which parts are confirmed by the chain and which rest on the operator’s word.

The short version

  • You deposit USDT, the contract takes custody, and the principal is locked for the plan term.
  • Yield accrues daily at 00:00 UTC inside the position; it reaches your claimable balance only at maturity, together with the principal.
  • The operator names three revenue sources: a USDC/USDT liquidity pool, Turbo Swap fees and Turbo Buy fees.
  • Five layers are paid out of those sources: plan yield, referral commission, leadership differential, onboarding bonus and the $TURBO reward.
  • A stablecoin pool on its own earns well under the ~0.9% a day the longest plan pays, and no published figure closes that gap.

The path a deposit takes

Five steps, and the third is the one that surprises people.

  1. 01

    You deposit USDT

    From 1 USDT on BNB Smart Chain, into a plan of 7, 14, 30 or 60 days. The first deposit takes two transactions: an approval, then the deposit itself. Both cost a few cents of BNB in gas.

  2. 02

    The contract takes custody

    The deposit goes to the protocol contract, whose address is public and whose source is verified. Ownership is renounced, so the terms of your plan cannot be altered after the fact, by anyone, including the team.

  3. 03

    The principal is locked for the term

    There is no early exit and no partial withdrawal of the deposit. A 60-day plan means 60 days during which that money is out of reach. This is the single most important thing to understand before choosing a duration.

  4. 04

    Yield accrues daily

    The contract accrues yield once a day at 00:00 UTC, at the fixed rate written into your plan, and keeps it inside the position: calculatedROI grows, your claimable balance does not. Both the principal and the full ROI are credited to that balance when the term ends, so a running plan pays nothing to the wallet.

  5. 05

    The principal returns at maturity

    At the end of the term the deposit is returned automatically. Nothing renews by itself: starting another cycle means making a new deposit by hand, which is also the only way compounding happens here.

Where the yield is said to come from

The operator names three revenue streams and states that none of them depends on new deposits. These are their claims; the chain shows the pool exists but not the arithmetic behind the rate.

The USDC/USDT liquidity pool

Deposits are stated to enter a stablecoin pair, which is why the operator reports no impermanent loss: both sides of the pair track the dollar, so there is no price divergence between them to lose value to.

Turbo Swap fees

The protocol runs its own swap surface. Trading fees collected there are stated to feed the same distribution that pays plan yield.

Turbo Buy fees

A fiat-to-crypto gateway, with its fees described as the third stream. Like the others, its volume is not published.

A stablecoin pool alone typically earns well under the roughly 0.9% a day that the longest plan pays. The operator does not publish how the three streams together compare with the payouts, and that gap is the central open question about the model.

What else pays, and to whom

Plan yield is one of several layers. They are funded differently and behave differently.

  • Plan yield

    Every depositor

    The fixed rate for the term: 3%, 10%, 24% or 54%. Credited daily, paid in USDT.

  • Referral commission

    Anyone with 25 USDT deposited and an active network

    Up to 51% of daily ROI is distributed across 20 levels. It comes out of the protocol’s distribution, not out of the referred person’s deposit.

  • Leadership rewards

    Ranks from 250 team members up

    A differential on team volume, from 1% at Partner to 10% at Legend.

  • $TURBO allocation

    Power and Ultimate deposits from 100 USDT

    An additional reward in token, from 0.56% to 1.12% of deposit value to the investor. It vests monthly and carries a 2% sell tax.

  • Buyback and burn

    Token holders, indirectly

    10% of admin fees are used daily to buy $TURBO and send it to the burn address, permanently reducing supply.

Timing, in one place

Yield credited
Daily, 00:00 UTC
Plan ROI claimable
At the end of the term, with the principal
Referral and leadership rewards
Claimable any time during the cycle
Principal returned
At the end of the term
Early exit
Not available
Renewal
Manual, a new deposit
$TURBO first tranche
Immediately, then monthly

The accrual is a public crank

Daily rewards are not pushed by a server the operator has to keep running. The processing is a function on the contract, and the queue it works through is readable.

  1. 01

    Each day is a numbered batch

    TIME_STEP is 86,400 seconds and launchDate is 10 March 2026, 13:00 UTC, so the day counter is fixed arithmetic rather than an operator decision. getDailyRewardStatus returns the current day and how many users it has processed.

  2. 02

    Anyone can push it forward

    needsDailyRewardCalculation returns whether a day is still pending, and calculateDailyRewards processes a batch. Neither is owner-only: any address can pay the gas and move the queue.

  3. 03

    Or you can push only your own

    processMyDailyRewards settles your positions without waiting for the queue to reach you. claimRewards runs the same settlement before paying out, so a claim never depends on someone else having pushed the crank.

  4. 04

    And the result is checkable

    dailyRewardDayCompleted takes a day number and returns true or false. On 6 October 2026 the contract reported day 209 with 33,587 of 33,587 users processed.

This removes the operator from the accrual: nobody has to run a bot for your rewards to be calculated. It says nothing about whether the pool holds enough to pay them.

What the chain confirms, and what it does not

Confirmed: the contract exists and is verified, ownership is renounced, the pool holds what it holds, and every deposit and payout is a public transaction. None of that requires trusting the operator.

Not confirmed: that the stated revenue covers the promised rate. A fixed return is a liability the protocol takes on, and whether it can keep meeting that liability is not something a block explorer can answer.

This is why the rest of this site separates the two rather than treating the whole model as verified because part of it is.

Check it at the source