> 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/pool/lp-score.md).

# LP score and weekly rewards

How GAGE/sGAGE LP emissions stream, how checkpoints set a position's weight, and what collecting or transferring changes.

The GAGE/sGAGE pool is **Uniswap v4**, not Uniswap v2. **Gage V2** refers to the lending engines and is a separate version number.

Eligible LP positions earn sGAGE emissions over time. There is no separate deposit step: the reward contract tracks each position NFT in your wallet and its reward weight.

## How emissions are divided

The liquidity budget for an epoch sets its emission rate:

```
pool emissions per second = epoch LP budget / seconds in the epoch
position emissions for an interval =
  pool emissions per second × interval seconds
  × position weight / total eligible weight
```

The contract uses integer arithmetic, so rounding can leave dust. At an epoch boundary, the rate changes to that epoch's budget. When weights change, subsequent emissions use the new shares.

A position's weight is its **value in GAGE at its last checkpoint**. A position outside its price range at that checkpoint has zero weight. This is value-based accounting, not simply the number of tokens or NFTs held.

For example, if a position has 10% of the eligible weight for one hour, it earns approximately 10% of the emissions streamed during that hour. If its share falls to 5%, it earns 5% of subsequent emissions until the next change. Adding liquidity later does not earn earlier emissions.

The calculation is continuous across intervals. It is **not a single end-of-week division of accumulated position scores**. The score on Pool describes participation; the stored reward weights and accumulator determine the actual allocation.

## Where the score shows

On Portfolio's **Pool** tab, each position's card shows **This week**, its share of the pool and about how much sGAGE that earns, and folds `SCORE · WK n` under **Details** (liquidity in range, weighted over the week; it sets your share of this week's pool rewards).

## Checkpoints and price changes

A checkpoint settles rewards earned using the previous weight, then refreshes that position's weight from its liquidity, range and the current pool price. Checkpointing is public; the app's liquidity flows and the keeper refresh positions.

Weights stay fixed between checkpoints. Crossing a price boundary does not by itself instantly update every stored reward weight. A removed or burned position must also have its stored weight cleared; the keeper refreshes stale positions, including ones changed outside the app.

## Which positions count?

* Eligible user positions in the GAGE/sGAGE pool can carry weight.
* The protocol's seed position has zero reward weight.
* The floor bands have zero reward weight.
* Out-of-range positions have zero weight when checkpointed.

If total eligible weight is zero, emissions for that interval remain undistributed and can be burned. They are not retroactively awarded to the next depositor.

## Earned, collected and claimable are different

1. **Pending LP emissions** accrue to the position NFT. Portfolio shows them as `n sGAGE pending` on the position's card and counts them in **Now** and on the **Rewards** tab.
2. **Collect**, on Portfolio through **Collect all** or the Rewards tab's **Claim**, settles that pending amount and creates a **seven-day drip for the collecting wallet**.
3. **Claim**, a later step of the same button, transfers the portion of that wallet's drips that has unlocked. The rest keeps unlocking.

Transferring an NFT transfers its still-pending position rewards to the new owner. It does **not** transfer drips already created for a previous collecting wallet.

Unused deal budget can also reach LPs as a separate rollover distribution after an epoch ends. That lump is assigned to the eligible weights present when it arrives, rather than retroactively to earlier participants. The contract pays a collected lump directly, separately from the seven-day drip for streamed emissions.

Swap fees are separate from sGAGE emissions and are collected on Uniswap's position page.

See [Weekly budgets](https://docs.gage.cash/rewards/weekly-budgets.md) for the difference between an LP allocation, future streaming and the deal reward budget.


---

# 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/pool/lp-score.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.
