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

# Lending

Fira's lending infrastructure includes separate markets for fixed-rate (BT-denominated) and variable-rate (USDC-denominated) lending.

## Overview

Fira uses two lending market deployments:

### FiraLendingMarket (Fixed-Rate)

* **Loan token:** BT (Bond Token)
* **Collateral:** Pendle PT tokens (PT-USDe, PT-sUSDe, PT-USDG)
* **Interest rate model:** None (`IRM = address(0)`) — the rate is implicit in the BT discount
* **Supply:** Whitelist-gated to the LiquidityInjector only
* **Oracle:** FiraSolvencyOracle (3-layer oracle pipeline)

### VariableLendingMarket (Variable-Rate)

* **Loan token:** USDC
* **Collateral:** wstETH, cbBTC
* **Interest rate model:** AdaptiveCurveIrm (adjusts based on utilization)
* **Supply:** Permissionless via SisuVault (ERC-4626)
* **Oracle:** Morpho wstETH/USDC, ChainlinkOracleV2 for cbBTC/USDC

## SisuVault

The SisuVault is an ERC-4626 vault that aggregates USDC deposits and supplies them to variable-rate lending markets. It is managed by a curator and allocator (Markov Labs) who control market allocation.

Vault shares (`mkUSDC`) represent proportional claims on the underlying USDC plus accrued interest.

## Key functions

| Function                                             | Description                            |
| ---------------------------------------------------- | -------------------------------------- |
| `supplyCollateral(params, amount, user, data)`       | Deposit collateral                     |
| `borrow(params, assets, shares, user, receiver)`     | Borrow loan token                      |
| `repay(params, assets, shares, onBehalf, data)`      | Repay debt                             |
| `withdrawCollateral(params, amount, user, receiver)` | Withdraw collateral                    |
| `liquidate(params, borrower, seizedAssets)`          | Liquidate undercollateralized position |
| `getUserPosition(params, user)`                      | View full position details             |
| `accrueInterest(params)`                             | Update interest state                  |

## Related pages

* [Fixed-Rate Lending (Feature)](https://github.com/Pi-2lavega/fira-gitbook-sync-final/blob/main/developers/smart-contracts/overview/features/fixed-rate-lending.md)
* [Variable-Rate Lending (Feature)](https://github.com/Pi-2lavega/fira-gitbook-sync-final/blob/main/developers/smart-contracts/overview/features/variable-rate-lending.md)
* [Contract Deployments](https://github.com/Pi-2lavega/fira-gitbook-sync-final/blob/main/developers/smart-contracts/protocol-contracts/contract-deployments.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 by asking a question.

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

```
GET https://docs.fira.money/developers/protocol-contracts/lending.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.
