> For the complete documentation index, see [llms.txt](https://docs-v4.venus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-v4.venus.io/technical-reference/reference-isolated-pools/risk-fund-and-shortfall.md).

# Protocol reserves and legacy Shortfall

The contracts in this section do not share one lifecycle. The standalone Isolated Pools product and its new-auction flow are deprecated, but the protocol-reserve contracts remain part of the current income architecture.

| Component                                                                                                               | Lifecycle                       | Scope                                                                                                                                                                                  |
| ----------------------------------------------------------------------------------------------------------------------- | ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [ProtocolShareReserve](/technical-reference/reference-isolated-pools/risk-fund-and-shortfall/protocol-share-reserve.md) | Current                         | Records and distributes protocol income for Core and isolated-pool deployments according to on-chain configuration. It is not deprecated with the standalone Isolated Pools interface. |
| [RiskFundV2](/technical-reference/reference-isolated-pools/risk-fund-and-shortfall/risk-fund-v2.md)                     | Current on BNB Chain mainnet    | Holds protocol-controlled raw token balances and receives the output of `RiskFundBuyback`. Per-pool accounting was removed in the VIP-620/VIP-621 migration.                           |
| [RiskFundV2 storage](/technical-reference/reference-isolated-pools/risk-fund-and-shortfall/risk-fund-storage.md)        | Current compatibility reference | Includes active fields and deprecated slots that must remain in place for proxy-upgrade safety.                                                                                        |
| [Shortfall](/technical-reference/reference-isolated-pools/risk-fund-and-shortfall/shortfall.md)                         | Deployed legacy/recovery        | The BNB Chain mainnet auction path is paused and all registered pools were `NOT_STARTED` at the recorded audit block. Historical token-transfer debt can still require recovery.       |

For the current conceptual flow, see [Protocol income, RiskFundV2, and bad-debt handling](/risk/risk-fund-and-shortfall-handling.md). For the dated auction design and safety boundaries, see [Shortfall and auctions](/technical-reference/reference-technical-articles/shortfall-and-auctions.md). The BNB converter migration is documented under [TokenBuyback](/whats-new/token-converter.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs-v4.venus.io/technical-reference/reference-isolated-pools/risk-fund-and-shortfall.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.