> For the complete documentation index, see [llms.txt](https://docs.kpk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kpk.io/funds/infrastructure/architecture/onchain-accounting/meta-balance-adapters/balancer-v3-gauges.md).

# Balancer V3 Gauges

Reports an account's gauge-staked Balancer V3 LP plus claimable rewards across any gauge.

Reports an account's **gauge-staked** Balancer V3 LP plus claimable rewards across any gauge. Staked LP is decomposed pro-rata into the underlying tokens of the gauge's `lp_token` pool; BAL and extra reward tokens are reported as rewards. Wallet-held LP is the separate [Balancer V3 Pools](https://docs.kpk.io/funds/infrastructure/architecture/onchain-accounting/meta-balance-adapters/balancer-v3-pools.md) adapter.

* **Type:** Meta-adapter
* **protocolSubId:** `keccak256("balancer-v3-gauges")`
* **Instance key:** the gauge address, widened to bytes32.
* **Source:** `BalancerV3GaugesMetaBalanceAdapter.sol`

## Positions returned

| Leg             | PositionKind | isDebt  | Description                                                                     |
| --------------- | ------------ | ------- | ------------------------------------------------------------------------------- |
| Staking         | `Staking`    | `false` | Pro-rata share of one underlying pool token, from the account's gauge-staked LP |
| Rewards (BAL)   | `Rewards`    | `false` | Claimable BAL, minted via the Balancer Minter                                   |
| Rewards (extra) | `Rewards`    | `false` | Claimable amount of each extra gauge reward token                               |

Tokens not registered in NAVCalculator are skipped, as are zero amounts and asset-filtered tokens.

## Balance calculation

<figure><picture><source srcset="https://1699303810-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUsQM4bzcmOPSgkWddkeN%2Fuploads%2FznlAJRF1UuJsrfsYHExP%2Fmeta-balancer-v3-gauges_D.png?alt=media&amp;token=a3571c30-ad34-4421-a82b-e1374b97b0bf" media="(prefers-color-scheme: dark)"><img src="https://1699303810-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUsQM4bzcmOPSgkWddkeN%2Fuploads%2FTXLDfltgiTZpOphyYG0q%2Fmeta-balancer-v3-gauges.png?alt=media&amp;token=8e56e2dc-6f9c-4967-bc17-656ccbb040ee" alt="Flowchart of the Balancer V3 Gauges balance adapter: read calls derive position legs into PositionBalance entries."></picture><figcaption><p>Balancer V3 Gauges adapter: how the underlying balances reported to the NAV Calculator are derived.</p></figcaption></figure>

**Staking legs** use `staked = gauge.balanceOf(account)` and the same `BalancerV3PoolLib.poolBalanceOfIndexed` decomposition as the [Pools adapter](https://docs.kpk.io/funds/infrastructure/architecture/onchain-accounting/meta-balance-adapters/balancer-v3-pools.md#balance-calculation), applied to the gauge `lp_token` pool: tokens in index order, legs keyed on the pool-token index, a transiently-zero scaling factor or token rate yields a `0` leg.

**BAL rewards** (`claimableBal`) emulate the gauge inflation checkpoint:

```
claimable = max(integrateFraction(account) - minter.minted(account, gauge), 0)
```

`integrateFraction` is recomputed by walking weekly boundaries (`WEEK = 7 * 86400`) to `block.timestamp`, accumulating `integrate_inv_supply` from the inflation rate, capped relative weight and `working_supply`. It tries the mainnet model (`calculateIntegrateFraction`, up to 500 weeks, future-epoch rate switch via the token admin) and falls back to the L2 model (`calculateIntegrateFractionL2`, up to 256 weeks, per-week `inflation_rate(week)`). A killed gauge zeroes the rate. Any revert yields 0.

**Extra rewards** come from `gauge.claimable_reward(account, token)` for each `reward_tokens(i)` (BAL excluded; it is handled via the minter).

## Identity

* **positionId:** `abi.encode(address gauge)`
* **positionKind:** `Staking` · `Rewards`

`positionLabels(positionId)` returns `["Staking Gauge", "<sym0>/<sym1>/…"]` from the staked pool's token symbols; verbose reads only (`getAccountPositionsVerbose` / `getAccountNavVerbose`).

## Constructor

```solidity
constructor(address balancerMinter_, address navCalculator_)
```

| Parameter         | Description                                                                                            |
| ----------------- | ------------------------------------------------------------------------------------------------------ |
| `balancerMinter_` | Balancer Minter contract (must be a contract); resolves the BAL token, token admin, and minted amounts |
| `navCalculator_`  | NAVCalculator address (must be a contract); source of the asset registry and the instance set          |

## Registration

Register with `addMetaBalanceAdapter(adapter)`, then add gauges with `addMetaInstances`. Each coordinate is the gauge address widened to bytes32.


---

# 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.kpk.io/funds/infrastructure/architecture/onchain-accounting/meta-balance-adapters/balancer-v3-gauges.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.
