Total Score
For any given market, a liquidity provider’s (Total Score) in an epoch is calculated as: where is the liquidity provider’s Liquidity Score in the market in the epoch, is the liquidity provider’s Uptime score in the market in the epoch, and is the liquidity provider’s total volume (maker and taker) in the market in the epoch., , and are exponent parameters that weight the different components of the formula.
Liquidity Score
The liquidity provider’s Liquidity Score for a market in an epoch, , is the sum of the minimum between the Bid and Ask Liquidity Scores (see below) across all order book snapshots in the epoch for the relevant market, multiplied by a bespoke volatility parameter for each market (represented by Θ). This promotes dual-sided liquidity since single-sided liquidity will earn a Liquidity Score of 0 under the function. A snapshot of the order book is taken randomly every 10-100 blocks. This is approximately every minute on average, which means there are approximately 40,320 snapshots in an epoch In practice, the upper bound of the summation will vary depending on the actual number of snapshots in the epoch. For the purposes of this guide, we will assume that there were exactly 40,320 snapshots in the epoch. is the sum of all bid order depths divided by the spread of the order, multiplied by the volatility parameter for that snapshot, for all limit orders placed by the liquidity provider in snapshot that exceed in size and are within the follows the same logic as , but on the ask side of the order book. The volatility parameter is calculated as follows: where is the oracle price moving average over blocks (1000 blocks, or roughly 10 minutes), represents the oracle price of the current block, and represents the realized volatility over blocks. This function has a clamp and scales well if the current oracle price deviates from the moving average, or if there is a spike in volatility over the last blocks. The range of - so we bound it within a finite field. We introduce two new parameters which monitor the sensitivity to volatility and a clamp. Because should trend towards the cap of 10 as described above for a 3% price move within a 10-minute span, is currently set at 2,500. A higher value means trends towards faster, but as is currently set to 10 per market (and can be modified on a per-market basis), a higher would not bypass that maximum. is calculated from the mid-price (distance from mid-price divided by mid-price).For the current values of and , see the Formula Parameters page.
Uptime Score
is the number of order book snapshots throughout the epoch in which the liquidity provider had a positive Bid Liquidity Score and a positive Ask Liquidity Score in the market of interest. This means the liquidity provider quoted on both sides of the order book with order sizes greater than or equal to with spreads less than or equal to in the snapshot. For liquidity providers who qualify for OLP rewards (for the first time ever) partway through an epoch, is scaled based on the total number of snapshots from the moment of qualification to the end of the epoch. For example, suppose there are exactly 40,320 snapshots in an epoch and a liquidity provider qualifies for the first time with exactly 20,000 snapshots remaining. Also suppose the liquidity provider had an of 18,0000 as defined by the scoring formula above during the remainder of the epoch. In this case, would be scaled to .For addresses that qualify partway through an epoch but have qualified in the past (the address failed to maintain eligibility at some point), will not be scaled. This is to disincentivize addresses from losing their eligibility from epoch to epoch.
Volume
is a liquidity provider’s cumulative eligible maker and taker volume in the market during the epoch.Fully Expanded Formula
The fully expanded formula is:For information on individual reward calculations each epoch, see the Reward Allocations page.
