Withdrawing from deprecated isolated pools
Venus isolated pools have been fully deprecated. Their navigation and market screens have been removed from the Venus app, so positions can no longer be managed through the interface.
For markets that still allow repayments and redemptions, legacy positions may be closable by interacting directly with the market contracts. This is not possible for every market: some deprecated markets are unlisted or have REPAY or REDEEM paused. Check the market status as described below before submitting a transaction. Do not repeatedly submit transactions if the required action is unavailable.
Production isolated pools were deployed on BNB Chain, Ethereum, and Arbitrum. Core Pool positions and other Venus products are separate from the deprecated standalone pools. Legacy testnet deployments also exist on BNB Testnet, Sepolia, and Arbitrum Sepolia; make sure you select the explorer for the network where your position exists.
Before you begin
You will interact with Venus contracts through a block explorer, connecting the same wallet that holds the position:
BNB Chain — BscScan or BscScan Testnet
Ethereum — Etherscan or Etherscan Sepolia
Arbitrum — Arbiscan or Arbiscan Sepolia
vTokens are beacon proxies, and RewardsDistributor contracts are transparent proxies. On an explorer, open Contract and use Read as Proxy or Write as Proxy when those tabs are available. If the explorer has not recognized the proxy, do not guess an implementation address or construct a transaction manually; stop and ask for verification through the official community forum.
Confirm the explorer domain, network, and full contract address before connecting your wallet. Token names and symbols can be imitated. Venus contributors and support representatives will never ask for your seed phrase or private key.
Keep enough of the network's native token for gas. The direct vToken flow operates on ERC-20 underlying tokens. For WBNB or WETH markets, repayment requires the wrapped token and redemption returns the wrapped token; BNB or ETH held for gas is not the same asset.
Contract inputs use integer base units, not human-readable decimal amounts.
The current Deployed Contracts → Markets page lists documented pool and vToken addresses. Older unlisted markets may appear only in your Venus transaction history or the canonical isolated-pools deployment records. Deployment records identify contracts but do not prove their current implementation, pause state, liquidity, or oracle status.
Each isolated-pool market is a vToken contract. Supplying an asset mints vTokens; borrowing records debt in the vToken. Repayments and redemptions below are made through the vToken proxy, while approvals are made through the underlying token contract.
Step 1 — Identify your positions and check market status
For every isolated-pool vToken you previously used, open its proxy on the correct explorer and check these functions under Read as Proxy:
balanceOf(<your address>)— your vToken balance. A non-zero value represents a supplied position, but does not guarantee that redemption is currently available.borrowBalanceStored(<your address>)— debt denominated in the underlying token, calculated with the market's latest stored borrow index. It does not first accrue new interest.underlying()— the ERC-20 token used to repay the market and received on a direct redemption.comptroller()— the Comptroller proxy that controls this market.
borrowBalanceCurrent(<your address>) accrues interest and is not a view function. Explorers generally place it under Write as Proxy, where broadcasting a transaction does not display its return value like a normal read. Do not send a transaction merely to read this value. A wallet/client simulation or RPC eth_call can obtain the simulated result; otherwise use borrowBalanceStored to identify debt and re-check it after repayment.
Token holdings can help find supplied positions, but a borrow-only account can have a zero vToken balance. The absence of a vToken from a wallet's token list—or the absence of an app notice—does not prove that the wallet has no debt or unclaimed rewards. Review the wallet's Venus transaction history and the official market records on every relevant network.
Before using the write functions below, open the market's Comptroller proxy and check:
isMarketListed(<vToken address>)must returntrue.actionPaused(<vToken address>, 3)checks REPAY and must returnfalsebefore repayment.actionPaused(<vToken address>, 1)checks REDEEM and must returnfalsebefore redemption.
If the market is unlisted or the action you need is paused, the direct call below will revert. Stop and ask for help through the Venus community forum; include the chain, wallet address, vToken address, and any transaction hash or revert data, but never share private credentials.
Step 2 — Repay your borrows
Do this only for markets where borrowBalanceStored is non-zero and REPAY is available. If you have no borrows, skip to Step 3.
Open the underlying token returned by
underlying()and use Write as Proxy if it is itself a proxy. Callapprove(spender, amount):spenderis the vToken proxy address, not its implementation.amountmust cover the debt after newly accrued interest and must be entered in the underlying token's base units. If an existing allowance is non-zero, some tokens require setting it to zero before changing it.
Open the vToken under Write as Proxy and call
repayBorrow(repayAmount). For a full repayment, passrepayAmount = 115792089237316195423570985008687907853269984665640564039457584007913129639935, which istype(uint256).max.
Passing type(uint256).max asks the vToken to repay up to the debt after interest accrual. The vToken caps the attempted transfer at that debt rather than attempting to transfer uint256.max. The transaction can still revert because of market state, oracle updates, insufficient token balance or allowance, or token behavior; fee-on-transfer behavior can also leave debt behind.
After confirmation, re-check borrowBalanceStored(<your address>). Do not treat the position as closed unless it is zero. Once it is zero—or if you decide to stop attempting repayment—check allowance(<your address>, <vToken address>) on the underlying token and revoke any unused allowance by calling approve(<vToken address>, 0).
Repeat for every borrowed market in each pool and on every affected network.
Step 3 — Withdraw your supplied assets
For each listed market where balanceOf is non-zero and REDEEM is available, open the vToken under Write as Proxy:
redeem(redeemTokens)— burns the specified vTokens and returns the corresponding underlying. To request a full exit, pass the complete value returned bybalanceOf(<your address>). This is the preferred full-exit method.redeemUnderlying(redeemAmount)— requests a partial withdrawal denominated in the underlying token's base units. Conversion to vTokens and rounding can affect the resulting amount, so do not use it as a guarantee of an exact full exit.
After confirmation, re-check balanceOf(<your address>) and confirm that the underlying tokens reached your wallet. Direct redemption from a WBNB or WETH market returns the wrapped token, which must be unwrapped separately if you need BNB or ETH. Token-level transfer fees or other token behavior can affect the amount received.
Repaying all borrows first is the simplest pool-local order because it removes account shortfall as one possible blocker. It does not guarantee redemption. A paused or unlisted market, insufficient market cash, unavailable oracle prices, or token and reward-hook failures can still cause a transaction to revert.
For a market your account has entered, redeeming or calling exitMarket causes the Comptroller to check the account across all currently listed entered markets in that pool. The Resilient Oracle first applies its configured validation and fallback logic. If it still cannot produce a valid price for any required market, the operation can revert. exitMarket performs the same full-balance redeem check and generally cannot bypass that condition.
If a repayment or redemption fails unexpectedly, stop rather than repeatedly spending gas. Ask for help through the Venus community forum and provide the chain, wallet address, vToken address, and transaction hash or revert data.
Reward claims
A legacy RewardsDistributor may still record accrued rewards. Claiming updates the accrual and attempts payment; payment succeeds only if that distributor holds enough of its reward token. A pool can have multiple distributors, each covering one reward token. Calling one distributor does not claim from the others.
The following mainnet proxy addresses come from the deployment records at commit 943e7db. Use these proxy addresses—not a contract named RewardsDistributorImpl—and verify the network, proxy, and rewardToken() value on the explorer before submitting a claim.
BNB Chain
DeFi
BNB Chain
DeFi
BNB Chain
DeFi
BNB Chain
GameFi
BNB Chain
GameFi
BNB Chain
Liquid Staked BNB
BNB Chain
Liquid Staked BNB
BNB Chain
Liquid Staked BNB
BNB Chain
Liquid Staked BNB
BNB Chain
Liquid Staked BNB
BNB Chain
Stablecoins
BNB Chain
Stablecoins
BNB Chain
Stablecoins
BNB Chain
Tron
BNB Chain
Tron
BNB Chain
Tron
BNB Chain
Tron
Ethereum
Curve
Ethereum
Curve
Ethereum
Curve
Ethereum
Liquid Staked ETH
Ethereum
Liquid Staked ETH
Ethereum
Liquid Staked ETH
Ethereum
Liquid Staked ETH
Arbitrum
Liquid Staked ETH
Not every deprecated pool had a RewardsDistributor deployment record. If your pool appears in the table, check each listed proxy for that pool; duplicate reward-token symbols represent distinct distributors and must not be deduplicated.
Before claiming, read the distributor's comptroller() and maxLoopsLimit(), then call getAllMarkets() on that Comptroller. Check isMarketListed(<vToken address>) for every returned market:
If every returned market is still listed and the number of markets does not exceed
maxLoopsLimit(), use Write as Proxy and call the one-argumentclaimRewardToken(address)with your address.If any returned market is unlisted, the one-argument overload will revert because it passes the complete historical market array to the claim logic. If the array is longer than
maxLoopsLimit(), it will also revert. Instead, useclaimRewardToken(address,address[]): pass your address first, then all verified listed vToken addresses returned by that Comptroller. Do not include an unlisted vToken, and split the list into separate calls no larger thanmaxLoopsLimit()if necessary.
Both overloads update rewards for the markets they process and then attempt to pay the distributor's recorded aggregate accrued amount. The two-argument fallback does not calculate additional pending rewards from omitted or unlisted markets. If rewards from an unlisted market have not already been recorded, the current claim path cannot update them; ask for help through the Venus community forum because a protocol or governance action may be required.
Each call covers only that proxy's reward token and Comptroller. It does not claim other reward tokens, other distributors, other pools, or other networks. No token approval is required.
After confirmation, verify the reward-token transfer. If the distributor does not hold enough reward tokens, the contract retains the accrued amount instead of making a partial payment. Claiming rewards is optional and independent of repaying and redeeming positions.
Last updated