> For the complete documentation index, see [llms.txt](https://lavarage.gitbook.io/lavarage/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lavarage.gitbook.io/lavarage/platform/liquidity.md).

# Liquidity

**1. Providing Liquidity on Lavarage**

Lavarage is designed to be a decentralized peer-to-peer platform for margin trading. We have traders on one side who borrow liquidity from lenders on the other side to trade, with leverage, on decentralized exchanges.

There are three distinct roles on the liquidity provision side:

1. Lender - Actively manage lending vaults by creating loan offers for various tokens
2. Staker - Passively stakes token(s) into protocol vault(s) to earn yield
3. Liquidator - Plays a critical role during liquidations by providing backstop liquidity. Liquidators supply token(s) to lending vaults to cover outstanding loans in exchange for the collateral assets of the liquidated positions.

This design ensures that lenders and stakers earn interest based on vault utilization and are shielded from liquidation-related PnL (e.g., bad debt) under normal circumstances.

**2. Two-Sided Platform**

Liquidity provision on Lavarage is fully decentralized and permissionless for both lending and staking. Lending is open to anyone holding a [Lava Rock NFT](/lavarage/community/lava-rock-alpha.md), while backstop liquidity provision remains available only for whitelisted partners.

Every lending vault has a quote currency, e.g. SOL. This is the token that is staked into and could be borrowed from this vault. The manager of the vault, i.e. the lender, actively manage loan offers that dictate which collateral tokens traders can borrow the quote currency against and the respective loan terms, which includes maximum open LTV, interest rate, etc.


---

# 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://lavarage.gitbook.io/lavarage/platform/liquidity.md?ask=<question>&goal=<endgoal>
```

`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.