# BOOSTS
In Asymetrix version 2, we have introduced two distinct boost types:
* [**ODDS BOOST**](/asymetrix-v2/boosts/odds-boost.md)
* [**esASX BOOST**](/asymetrix-v2/boosts/esasx-boost.md)
### Eligibility for BOOSTS
To be eligible for these BOOSTS, users must provide liquidity in one of the supported pools and then lock their positions within the Asymetrix interface. Currently, Asymetrix supports two ASX/ETH pools:
* Balancer (ASX/ETH ratio is 80/20)
* Uniswap v3 (ASX/ETH ratio is 50/50)
Users can select the pool that best suits their preferences.
{% hint style="info" %}
BOOSTS will only be activated if you provide liquidity and lock it in Asymetrix. **Adding liquidity directly via Balancer or Uniswap websites won't enable these BOOSTS, you need to lock it**.
If you didn't use the Asymetrix interface to add liquidity but instead directly contributed to one of the two official pools, your position will still be recognized in the Asymetrix interface. All you'll need to do is lock it in the relevant section of DASHBOARD.
{% endhint %}
### Boost Values and Determining Factors
The BOOST types can have the following values:
* **ODDS BOOST**: Ranges from x1.05 to x4.0
* **esASX BOOST**: Ranges from x1.05 to x4.0
Two factors affect the size of the BOOST:
1. **Lock Period**: This is straightforward. The minimum time a user can lock their liquidity position is one week, and the maximum 30 weeks.
2. **Liquidity-to-Deposit Ratio (LTD)**: This is the ratio of **locked liquidity** to the user's **deposit size** in Asymetrix.\
**The minimum required Liquidity-to-Deposit ratio is 3%** \
If this ratio drops below 3%, BOOSTS will be automatically deactivated. Additionally, users who have received esASX with BOOST face the risk of losing previously farmed but unclaimed esASX. When the LTD ratio is less than 3%, these unclaimed esASX tokens become claimable (buy with a discount option) by other users. This applies only to esASX that were farmed with an active BOOST. esASX tokens earned without a BOOST cannot be liquidated.
**The maximum required Liquidity-to-Deposit ratio is 9%.** \
You can provide and lock up liquidity equivalent to twice your deposit (it would be 200% in this case), but this would be redundant.
Both the Lock Period and LTD have an equal impact on the BOOST size (50% each).
### BOOST Calculation Formula
Variables:
***User's LTD** = Ratio of provided liquidity to the user's deposit;*\
\&#xNAN;***Max. required LTD** = 9%* according to *current settings;*\
\&#xNAN;***Lock period** = number of weeks that the user chooses to lock their position;*\
\&#xNAN;***Max. lock period** (in weeks)= 30* according to *current settings;*\
\&#xNAN;***C** = Constant value, set at 3.0 in current settings;*\
\&#xNAN;***B** = Bonus value based on Time Lock* \
*\* 0.5 for a lock period from 1 to 10 weeks.*\
*\* 0.75 for a lock period from 11 to 20 weeks.*\
*\* 1.0 for a lock period from 21 to 30 weeks).*
*Formula:*
### **Examples**
> **Example #1**: User locks in liquidity equal to 6% of his deposit for 15 weeks.\
> BOOST will be calculated as (6%/9% x 0.5 + 15/30 x 0.5) x 3.0 +0.75) = **2.50**
>
> **Example #2**: User locks in liquidity equal to 9% of his deposit for 3 weeks. \
> BOOST will be calculated as (9%/9% x 0.5 + 3/30 x 0.5) x 3.0 + 0.5) = **2.15**
>
> **Example #3**: User locks in liquidity equal to 3% of his deposit for 30 weeks.\
> BOOST will be calculated as (3%/9% x 0.5 + 30/30 x 0.5) x 3.0 + 1.0) = **3.00**
### BOOSTS table
For clarity, below is a table of BOOSTS received at different LTD ratios and lock periods.
For a practical guide on how to obtain these boosts, please see the next section titled "[DASHBOARD (Practice guide)](/asymetrix-v2/dashboard-boosts-practice-guide.md)".
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.asymetrix.io/asymetrix-v2/boosts.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.