> For the complete documentation index, see [llms.txt](https://docs.gage.cash/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gage.cash/borrow/positions.md).

# Existing LP-backed loans

Manage an existing LP-backed loan.

The earlier engines no longer offer new loans backed by Uniswap LP positions. To borrow against a liquidity position now, see [Borrow against LP positions](https://docs.gage.cash/borrow/lp-lane.md), a lane of its own.

Existing LP loans remain visible in Portfolio and at their original position links. Borrowers can cancel eligible unfunded listings or repay existing loans. Lenders retain their repayment, reward and collateral-claim rights. Position valuation and recovery tools remain available for these loans.

## While escrowed

* Nobody modifies the liquidity or collects fees. Accrued fees stay in the position.
* Fees follow the NFT. Reclaimed: you collect them later. Claimed: the lenders do, as the two underlying tokens after the default is finalized.
* If the price leaves the range, the position holds one asset until it comes back. That changes its value, not the deal.

Liquidity provision, LP rewards and fee-funded GAGE/sGAGE liquidity are separate features and remain supported.

See [Contract addresses](https://docs.gage.cash/protocol/addresses.md) for the separate contracts and canonical NFT managers.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.gage.cash/borrow/positions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
