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

# Lending (LVF)

Peapods Finance offers a robust and modular lending system built upon a modified fork of Fraxlend. This architecture allows the protocol to create isolated lending pairs, where lenders can supply assets such as USDC and receive pfTKNs (eg. pfUSDC) in return. These pfTKNs act as yield-bearing receipts and represent the supplier's claim to future repayment.

The uniqueness of Peapods' lending system lies in its isolated design where each lending pair operates independently, ensuring that risks are contained within individual pools. This means if a default or severe event occurs in one market, it will not impact the solvency of any other. As a result, the platform mitigates systemic risk, allowing for more predictable and safer participation.

Additionally, the protocol's design ensures that any bad debt is socialized within the pair rather than across the protocol.

<figure><img src="/files/E17fTUBnjdh8PCTe7Bbw" alt=""><figcaption></figcaption></figure>

While inspired by Fraxlend, Peapods’ version is further optimized to support the Leveraged Volatility Farming (LVF) mechanics and to enhance receipt token composability across DeFi.

<br>


---

# 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:

```
GET https://docs.peapods.finance/lending-lvf.md?ask=<question>
```

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.