How rewards work

Rewards in the fixed-rate product are computed, not received. The platform runs the APR maths against each position, writes an unclaimed earning row, keeps the admin fee, and books the whole gross amount as money it has committed to pay. There is no external yield feed and nothing reconciles against one.

This page is the arithmetic and the schedule. If you have not read the funding warning on the overview, read it first — it changes how you should read every number below.

The formula

Two methods, chosen platform-wide by stakingDefaultAprCalculationMethod. It is not a per-pool setting.

Simple (the default, and what you get if the setting is unreadable):

reward = amount x (apr / 100) x (daysStaked / 365)

Compound:

reward = amount x ((1 + rate/n)^(n x daysStaked/365) - 1)

n — the compounding periods per year — comes from the position's resolved earning frequency, which is its own snapshot and falls back to the pool's only for a legacy row that predates the column:

A zero or negative amount, APR or day count returns zero. daysStaked is measured from the position's startDate, always — never from the last payout.

Worked example. 1,000 USDT at 12% APR for a 30-day lock:

The staker's realised rate on the simple pool is 9.6%, not 12%. That is by design — the admin fee comes out of the reward, not out of the advertised APR. The admin overview measures every pool against its net promised APR for exactly this reason, so a healthy pool does not report as underpaying by exactly your fee.

When a reward row is written

The position's earningFrequency sets the accrual interval:

The engine works from the position's startDate in whole intervals: it computes the latest interval boundary that has fully elapsed, caps it at endDate, and settles up to there. A position five hours into a DAILY pool is owed nothing yet; a position 25 hours in is owed one day.

Each position carries a watermark, lastDistributionDate, recording the point the engine has already settled to. END_OF_TERM pools and auto-compound pools never advance it during the term.

Why the engine cannot double-pay

This matters because the cron runs hourly, you can trigger distribution by hand, and settlement runs its own final accrual. Three mechanisms keep those from overlapping:

Accrual is a running total, not an increment. For each period the engine computes the reward owed for the entire elapsed term at the position's snapshotted APR, subtracts everything it has already credited, and writes the difference. Missing a run costs the staker nothing — the next run pays the whole outstanding amount at once.

Every row is keyed to its period. Accrual rows carry a periodBucket of accrual_YYYY-MM-DD, under a unique database index on (positionId, type, periodBucket). A concurrent duplicate collides at the database rather than being credited twice.

One-off payouts live in a different namespace. The "already paid" total only counts rows this engine wrote. An admin bonus is always booked as type BONUS with its own bucket, so it is additive money rather than an advance against the APR curve — otherwise a goodwill payment would silently suppress the staker's real accrual until the curve caught up.

The fee split

Each accrual is split at the moment it is written:

• The net amount goes to the staker as an unclaimed stakingEarningRecord.
• The fee — the position's snapshotted adminFeePercentage of the gross — is credited to the Super Admin wallet through the platform fee collector, and only then recorded as a PLATFORM_FEE row on the earnings screen.
• The gross is recorded as a platform loss: the liability the platform has just taken on.

Recording all three is what makes the profit figure honest. Booking only the fee reported a 20% fee as pure profit while the platform had actually committed to paying the whole accrual — plus 20 against a real net of minus 80.

Two edge cases you can configure yourself into:

Auto-compound

autoCompound changes the payout shape completely:

• No claimable rewards during the term. The claim endpoint returns a 400: "Auto-compound rewards are returned with your principal at maturity and cannot be claimed separately."
• At maturity the engine computes the whole term's compounded reward in one pass, takes the admin fee, and credits principal plus net reward as a single wallet credit.
• The position's stored amount is then rewritten to the compounded total for history, but pool capacity is restored by the original principal, never the compounded figure.
• earningFrequency stops controlling payout timing and instead sets the compounding periods per year.

Auto-compound pools are also rejected by both manual distribution endpoints — there is nothing intra-term to distribute.

The automatic schedule

The hourly cron processStakingPositions — Process Staking Logs on the cron screen — does two jobs, and they obey different rules. It touches fixed-rate positions only; the on-chain product has six tasks of its own.

Maturity settlement always runs. Once a position passes its endDate, the final outstanding reward is accrued, the principal is returned and the position completes — regardless of your distribution settings. Holding someone's principal because an admin toggle is off is a breach of the lock they agreed to, not a configuration choice.

Intra-term accrual is gated by two settings:

Skipping an hour never costs a user anything — accrual is delta-based, so the next qualifying run credits the full outstanding amount.

Operationally the cron processes up to five positions at a time, retries a failed position three times with a five-second gap, and if any position still fails it raises a high-priority in-app notification to a Super Admin listing the position IDs.

Distributing by hand

There are two distribute endpoints and they do genuinely different things. Both require create.staking.earning.

Use this when automatic distribution has been off, or the cron was down, and you want to bring a pool's positions up to date. It routes every write through the same authority the cron uses, so it can be run repeatedly and cannot collide with the cron. Optional positionIds narrows it to a subset — maximum 100 per call. dryRun: true computes and reports the amounts without writing anything.

Use this to pay a bonus, pass through an unusually good month, or make good on an incident. You give it poolId, a total amount and a distributionType label of regular or bonus. The pool's current admin fee percentage is taken off the top and credited to the platform; the remainder is split across active positions in proportion to their staked amount.

Both labels write BONUS earning rows — the label only stops a "regular" and a "bonus" run in the same cycle from colliding. The whole distribution is atomic: if any share computes to a non-finite number, nothing is written and no fee is booked.

Claiming a fixed-rate reward

Rewards sit as unclaimed rows until the user claims them. A claim takes every unclaimed row on that position at once and credits the total to the user's wallet as a STAKING_REWARD transaction, rate-limited to ten claims per hour per user and gated on the withdraw_staking KYC feature.

Three refusals:

• Auto-compound pools — rewards are not separately claimable.
• Cancelled positions — their unclaimed rewards were forfeited at cancellation and are never payable.
• On-chain positions — there is nothing to claim. The door says so in product words before it refuses by mode: "On-chain rewards compound in the pool and are paid when you unstake. To take rewards out, unstake the shares you want to withdraw; there is no separate claim."

A COMPLETED position stays claimable. Rewards earned during the term do not expire when the term ends, and the admin overview counts them as an outstanding liability until they are claimed.

In on-chain mode

Every mechanism above is absent, and the substitutes are not analogues of it.

One consequence is worth stating on its own, because it has no fixed-rate equivalent: an exit settles at the lower of the price when it was requested and the price when it settled. A fall between the two is taken by the holder, and a rise between the two is not kept by them — and the same rule applies to the platform's own commission exit, so the treasury is not advantaged by it.

How a stake moves follows the observation and exit path end to end; Operating on-chain staking covers the commission ledger and the slashing reimbursement.

Next: the position lifecycle.