> 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/balance-adapters/cap-savings.md).

# Cap Savings

Reports an account's staked stcUSD, Cap's yield-bearing savings token, valued in USDC through cUSD's burn quote.

Reports an account's **staked stcUSD**, Cap's yield-bearing savings token, valued in USDC. One leg, one label pair: `["Savings", "stcUSD"]` for every position this adapter can emit.

Sibling of [Cap Stablecoin](/funds/infrastructure/architecture/onchain-accounting/balance-adapters/cap-stablecoin.md), same protocol, same taxonomy, same underlying asset, different leg. Both are registered on the NAV Calculator.

* **Type:** Plain adapter
* **protocolSubId:** `keccak256("cap")`, unchanged from the pre-split adapter
* **Underlying asset:** USDC
* **Source:** `CapSavingsBalanceAdapter.sol` · shared base `CapBalanceAdapterBase.sol`

## Positions returned

| Leg    | PositionKind | isDebt  | Description                                                       |
| ------ | ------------ | ------- | ----------------------------------------------------------------- |
| stcUSD | `Staking`    | `false` | Staked cUSD (stcUSD shares), redeemed to cUSD then valued in USDC |

Staked cUSD is a staking principal, so it reports `Staking`, unchanged from the pre-split adapter.

## Balance calculation

Two hops, the ERC-4626 share conversion, then the burn quote:

```
cUsdAmount = stcUSD.convertToAssets(stcUSD.balanceOf(account))   // ERC4626 shares → cUSD
amount     = ICUsd.getBurnAmount(USDC, cUsdAmount).amountOut     // cUSD → USDC
```

This is the same two-hop quote the pre-split adapter used for this leg, so the reported amount does not move across the split.

## Why Cap is served by two adapters

See [Cap Stablecoin](/funds/infrastructure/architecture/onchain-accounting/balance-adapters/cap-stablecoin.md#why-cap-is-served-by-two-adapters); the split exists so each label segment is a per-adapter constant, which is what makes `AssetKindRegistry`'s adapter-keyed label overrides safe to use on either leg without corrupting the other.


---

# 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/balance-adapters/cap-savings.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.