> For the complete documentation index, see [llms.txt](https://docs.jpegd.io/jpegd-dao/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jpegd.io/jpegd-dao/about-the-jpegd-protocol/jpegd-boosts/ltv-boost.md).
# LTV Boost
LTV boosts allows users to increase the [LTV](/jpegd-dao/about-the-jpegd-protocol/lending-mechanics/loan-to-value-ratios-and-liquidation-thresholds.md) of individual positions by up to **10%** above the Base LTV of the selected collection.
To enable the LTV boost, $JPGD tokens need to be locked on a per-position basis as illustrated in the [example](#id-84d7) below. The amount of boost can be chosen by the user, ranging from 0.01% to 10% extra LTV. Once activated, the boost effects will remain active until the user requests the [withdrawal](#withdrawal) of the associated $JPGD.
Unlock up to 10% extra LTV by locking $JPGD
### Cost
To estimate out how much JPGD you need to lock, follow these steps:
1. Calculate the difference between the boosted credit limit and the base credit limit.
2. Multiply this difference by the lock rate.
3. Then, divide by the price of JPGD in Ethereum (ETH).
This formula helps determine the amount of JPGD tokens needed to unlock a 10% boost in loan-to-value (LTV). The cost is 20% of the extra value provided by the increased credit limit, payable in JPGD tokens.
So, to summarize, the formula for the amount of JPGD to lock is:
`AmountOfJPGDToLock = (boostedCreditLimit - baseCreditLimit) * lockRate / jpgdPriceInEth`
#### Example:
100 ETH floor collection\
35 ETH = max borrow with no[ JPEG Card](/jpegd-dao/about-the-jpegd-protocol/tokens/jpeg-cards.md)\
45 ETH = max borrow with staked JPEG Card\
60 ETH = max borrow with staked JPEG Card and locked JPGD tokens\
Assumed JPGD token price = $0.0006\
Assumed ETH price = $1,000
Increase in credit limit due to locked JPGD tokens = 15 ETH x 20% cost (in JPEG tokens) = 3ETH / $0.0006 = 5,000,000 JPGD tokens.
With a 3 ETH cost you essentially unlock an additional 15 ETH of credit.
### Withdrawal
Boost owners can request a withdrawal at any time. The processing period is of **7** days, after which the boost associated to the position will be disabled and the $JPGD will be available for withdrawal.
When a user locks JPGD tokens to get a boost, those tokens remain theirs. If they transfer the NFT, the boost stays active for whoever owns the NFT next. Only the boost owner can disable a boost.
### Liquidation
In the case of liquidation, the locked JPGD gets burned.
### Legacy boosts
All boosts created prior to the application of [PIP-58](https://snapshot.org/#/jpeg%E2%80%99d.eth/proposal/0x7c06ac3e2ed666c445378c58f71ee4e9b209ef84faa1a22375689dd9c29dd8d2) have been marked as having a withdrawal requested and unlock time will be the current unlock time set when creating the boost. Users can cancel the withdrawal request anytime.
## Learn how to enable LTV Boost
[View tutorial ->](/jpegd-dao/cdp-lending-guides/borrowing/create-an-ltv-boost.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://docs.jpegd.io/jpegd-dao/about-the-jpegd-protocol/jpegd-boosts/ltv-boost.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.