ohtradeDocs
Open trading app ↗

Weekly extra rewards

The extra pool rewards active stakers who meet trading-fee targets based on their previous week. A week runs from Monday 00:00 in New York to the following Monday, including daylight saving changes.

Your targets

OH fee target = last week's time-weighted average account OH × 1%
USDC fee target = last week's allocated USDC rewards × 5%

Targets round up to the next micro-unit. The OH average uses actual balances and time held in seconds. It counts OH tracked inside the protocol across available, staked, unclaimed, order and collateral states without counting an internal move twice. External wallet OH outside that accounting is excluded.

Allocated USDC rewards include the still-locked portion of a completed allocation. Waiting to claim does not reduce the following week's target. A new account has no automatic first-week qualification; the launch week starts with everyone unqualified.

At least one target must be positive and both requirements must be met. Qualification takes effect at the next five-minute boundary. An account with two zero targets does not qualify by default.

Example: a previous-week average of 10,000 OH and 200 USDC of allocated rewards creates targets of 100 OH and 10 USDC in actual trading fees. These are fee targets, not trade volume targets.

How a batch is divided

The normal/extra switch is evaluated for the batch's eligible income. When the batch has no effective qualified weight, everyone receives 100% normal rewards. When it has effective qualified weight, everyone receives 80% normal rewards, while 20% forms the extra pool.

Old income keeps its original stake ownership. A trader who arrives just before the batch cannot claim someone else's old income. A qualified user's exit also does not erase that user's earlier earned share.

Fee-covered extra weight

Qualification opens access to the extra pool. The weight used inside that pool is also limited by the user's current-week paid fees and previous coverage consumption.

For a qualified user i:

R_i = the user's income weight in this batch
P_i = highest stake principal since that user's last cutoff
F_OH,i = OH trading fees paid this week
F_USDC,i = USDC trading fees paid this week
U_i = USDC income weight already covered this week

C_i = min(
  R_i × min(1, 100 × F_OH,i / P_i),
  max(0, 20 × F_USDC,i − U_i)
)

When P_i is zero, the OH coverage factor is treated as one. Only qualified users contribute C_i. With total income weight B = ΣR_i and covered weight C = ΣC_i:

When C = 0: normal_i = R_i; extra_i = 0
When C > 0: normal_i ≈ 0.8R_i; extra_i ≈ 0.2B × C_i/C

The program uses integer allocation and carries its rounding rules through the ledger. The coverage limit controls distribution weight, rather than imposing a fixed monetary cap on the extra reward. A sole user with nonzero covered weight can receive the entire 20% pool.

Even when a user's previous-week USDC target is zero, current-week USDC fees are needed for nonzero USDC coverage. Completing an OH-only target can therefore show qualification without producing extra weight until that coverage exists.

A 1,000 USDC batch

Alice owns 600 of the batch's income weight and Bob owns 400. Alice is the only user with effective qualified coverage:

UserNormalExtraAvailable immediatelyReleased over 24h
Alice480 USDC200 USDC536 USDC144 USDC
Bob320 USDC0 USDC224 USDC96 USDC

If neither had effective covered weight, Alice would receive 600 and Bob 400 as normal rewards, each with the ordinary 70%/30% release schedule.

The qualification panel shows qualified stake versus total stake, qualified accounts, fee progress and the recent-history extra estimate. An account count and an income-weight denominator measure different things; the distribution uses the latter.

← Previous
Stake OH and receive USDC
Next →
Sell OH into the buyback