> 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/utility-contracts/oracles/lp-oracle.md).

# LP Oracle

LpOracleLib computes TWAP-based LP token prices by simulating a hypothetical rebalancing trade at the oracle-implied rate.

{% hint style="info" %}
**Source:** `src/fira_bonding/oracles/LpOracleLib.sol`
{% endhint %}

## Overview

LP token pricing is more complex than BT/CT because LP represents a share of a pool with two assets (BT + FW) in varying proportions.

## Pricing method

The library simulates a hypothetical rebalancing trade:

1. Compute the market's current `rateScalar` and `rateAnchor`
2. Compute `cParam = exp(rateScalar × (rateOracle - rateAnchor))` — where the pool "should" be according to the oracle
3. Calculate the hypothetical trade size to move the pool to the oracle-implied proportion
4. Sum total asset value after the trade: FW reserves (in asset terms) plus BT reserves, adjusted by post-trade rates
5. Divide by total LP supply

The hypothetical trade rate is the average of the oracle TWAP rate and the last trade rate, dampening the impact of stale oracle data.

### Post-expiry

LP pricing simplifies: 1 BT = 1 asset, so `LP value = (totalBt + fwToAsset(totalFw)) / totalLp`.


---

# 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/utility-contracts/oracles/lp-oracle.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.
