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 | 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 | 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 | Current compatibility reference | Includes active fields and deprecated slots that must remain in place for proxy-upgrade safety. |
| Shortfall | 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. For the dated auction design and safety boundaries, see Shortfall and auctions. The BNB converter migration is documented under TokenBuyback.