where LSepoch is the MM's Liquidity Score in the market in the epoch, UptimeEpochis the MM's Uptime score in the market in the epoch, and Volumeepoch is the MM's total volume (maker and taker) in the market in the epoch.
a, b, and c are exponent parameters that weight the different components of the formula.
Liquidity Score
LSEpoch=N=1∑40,320min(LSNBid,LSNAsk)
The ’s Liquidity Score for a market in an epoch, LSEpoch, 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. This promotes dual-sided liquidity since single-sided liquidity will earn a Liquidity Score of 0 under the min() 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 (60⋅24⋅28=40,320). 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.
LSNBid=Spread1BidDepth1+Spread2BidDepth2+…∀BidDepthi≥MinDepth and Spreadi≤MaxSpread
LSNAsk=Spread1AskDepth1+Spread2AskDepth2+…∀AskDepthi≥MinDepth and Spreadi≤MaxSpread
LSNBid is the sum of all bid order depths divided by the spread of the order for all limit orders placed by the in snapshot N that exceed MinDepth in size and are within the MaxSpread.
LSNAsk follows the same logic as LSNBid, but on the ask side of the order book.
Spread is calculated from the (distance from mid-price divided by mid-price).
UptimeEpoch is the number of order book snapshots throughout the epoch in which the had a positive Bid Liquidity Score and a positive Ask Liquidity Score in the market of interest. This means the quoted on both sides of the order book with order sizes greater than or equal to MinDepth with spreads less than or equal to MaxSpread in the snapshot.
For who qualify for OLP rewards (for the first time ever) partway through an epoch, UptimeEpoch 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 an qualifies for the first time with exactly 20,000 snapshots remaining. Also suppose the had an UptimeEpoch of 18,0000 as defined by the scoring formula above during the remainder of the epoch. In this case, UptimeEpoch would be scaled to 2000018000∗40320=36288.
For addresses that qualify partway through an epoch but have qualified in the past (the address failed to maintain eligibility at some point), UptimeEpoch will not be scaled. This is to disincentivize addresses from losing their eligibility from epoch to epoch.
Volume
Volume is a 's cumulative eligible maker and taker volume in the market during the epoch.