Venusprotocol isolated pools support conditional legacy exits after retirement

Legacy balances define the remaining uses

An existing position is the main reason to interact with a retired isolated pool. Its remaining obligations stay with that pool.

Supply claims and outstanding loans

A supplied balance represents a claim on the market's underlying asset. A borrow records a separate debt, with interest determined by the market's configured model. Managing either balance can remain necessary after new lending stops. The relevant action must still be available; retirement alone does not establish an executable exit.

New lending and asset-group exposure

Opening a new position requires an available Core market with suitable asset permissions and capacity. Historical isolated-pool use cases included lending within separately configured asset collections. Core E-Mode offers a related grouping mechanism on BNB Chain, subject to its own eligibility rules. An old pool label does not establish a currently available borrowing route.

Can an isolated pool meet a fixed withdrawal date?

A legacy isolated pool cannot provide a fixed withdrawal date merely because an account holds vTokens. Redemption requires sufficient available market cash, an enabled action, and permission under account-liquidity rules. Price or contract failures can also block execution. Waiting for liquidity exposes the position to continuing market conditions, without establishing when cash will become available. A withdrawal-dependent commitment therefore cannot treat the displayed supply balance as immediately accessible funds.

View full-size image

The sunset changed the standalone product

Venus Labs proposed the isolated-pool sunset on December 16, 2025. The plan made the initial pause conditional on a successful governance vote. Its later migration measures included tentative changes, so those dates and proposals did not establish execution in every market. AllezLabs' April 24, 2026 deprecation proposal subsequently described isolated pools as already sunset.

The standalone product ultimately retired across BNB Chain, Ethereum, and Arbitrum. Its market screens left the app. The lending engine continued serving other deployments, including modern Core Pools. The repository name isolated-pools identifies an architecture, while each deployed market has its own operating state.

Zero settings in the proposed wind-down configuration

AllezLabs' April 24, 2026 proposal targeted these settings for BNB Chain isolated pools. These are proposal-specific values, not permanent parameters or evidence of every market's current configuration.

A zero supply cap makes adding collateral through new supply unsuitable as a response to declining account health. A zero borrow cap blocks expansion of debt. Repayment and redemption have separate permissions, so the ability to attempt either action depends on its own pause state and the market's listing.

Pool identity determines contract compatibility

A migration destination must accept the actual underlying asset and the intended lending action. Matching token symbols cannot establish either condition.

Balances belong to a particular pool

Each standalone pool had its own Comptroller and market contracts. A Core market for the same underlying asset records a different position. Shared asset exposure does not combine their collateral or debt. The account, network, and market address identify the relevant balance; an asset name alone cannot distinguish an old isolated supply from a Core supply.

An engine name does not identify an implementation

BNB Chain Core token markets use legacy delegator contracts, while isolated-pool vTokens use beacon proxies. Modern Core Pools outside BNB Chain also use the isolated-pools engine. Even within that family, deployed implementations can differ. An integration designed for another network or release may therefore call an unavailable method. The proxy and its applicable implementation determine the interface.

Does repaying an isolated loan withdraw its collateral?

Repayment reduces the recorded debt, while redemption exchanges supplied vTokens for the underlying asset. Reducing debt can remove an account-liquidity obstacle to withdrawal, but it does not transfer supplied assets out of the market. Redeeming collateral while debt remains also requires the Comptroller to permit the resulting position.

Redemption requires enough available market cash to cover the requested underlying amount. A completed repayment does not establish that cash will be available for a later withdrawal. Market listing, action pauses, and applicable price checks remain separate constraints.

Core E-Mode fits compatible asset groups

E-Mode, or Efficiency Mode, provides specialized risk settings inside the BNB Chain Core Pool. It addresses the asset-group use case without creating another standalone lending pool.

Eligible collateral follows the selected group's collateral factors, liquidation thresholds, and liquidation incentives. Borrowed assets must be allowed in that group. An account with an incompatible borrow cannot enter it. Entry requires no outstanding VAI debt and sufficient account liquidity under the selected group's settings.

Assets outside the group require particular attention. With Core Pool fallback enabled, they use Core risk parameters. Without fallback, they contribute no borrowing power under that group's settings. A collection of supported tokens therefore does not automatically make the complete account compatible.

Default Core use remains an alternative when the desired borrowing mix does not fit an E-Mode group. The relevant Core markets still need capacity and enabled actions. Group membership does not remove those market constraints.

Returning from E-Mode to default Core also requires sufficient account liquidity under the destination's parameters. Higher borrowing power within a group can make that return unavailable while debt remains too large.

Reserve factors change the case for keeping supply

A higher reserve factor directs a larger share of accrued borrow interest toward protocol reserves. It does not describe a percentage deducted from the entire supplied principal. Suppliers receive a smaller share of that interest, which can reduce the reason to leave capital in a legacy market.

The wind-down proposals used reserve-factor increases to encourage migration. Borrowing costs can rise if withdrawals increase utilization and the market's interest model responds. That chain of effects depends on actual balances and rate parameters. A proposal's intended incentive cannot establish a fixed future rate or the date a particular supplier will recover funds.

Accrued rewards remain a separate claim

Legacy reward claims concern amounts the relevant distributor records, separate from loan repayment and supply redemption. The configured reward token, distribution speeds, and any ending block or timestamp determine further accrual. A displayed incentive does not establish continuing emissions. Claiming attempts payment from that distributor's token balance; insufficient funding can leave the recorded amount unpaid. Claiming an already accrued reward does not require keeping the associated loan open.

Isolation did not remove price or recovery dependencies

Separate pool accounting limited which asset collection a position used. It did not make every price feed, repayment, or recovery mechanism independent of configuration.

Price availability still affects actions

The ResilientOracle supports main, pivot, and fallback roles for individual assets. Multiple enabled roles are optional, so the name alone does not establish cross-validation. An entered market can also make withdrawal permission depend on prices for other relevant positions in its pool. Monitoring a single supplied asset can therefore miss a price failure affecting the account.

A risk fund does not promise automatic reimbursement

Applying BNB Chain mainnet RiskFundV2 balances to bad debt requires a scope-specific governance or operational action. Its global token balances replaced the former per-pool reserve ledger. New legacy Shortfall auctions and restarts are paused on BNB Chain mainnet. Leaving funds in a retired pool to await an automatic compensation process assumes a protection those mechanisms do not provide.

Legacy exit availability limits a Core migration

Direct legacy repayment or redemption requires a listed market and an enabled action. An unavailable action calls for stopping submissions. A cash shortage blocks a redemption larger than available liquidity. A smaller redemption still requires account permission, and waiting cannot override a pause or an unlisted market.

New lending requires a usable Core destination with an accepted underlying asset, available capacity, and suitable collateral rules. A Core listing does not close the old isolated position. For a full legacy exit, confirm zero borrow and vToken balances in each affected market and receipt of any redeemed underlying.