Unable to withdraw from LazyVault_LowerRisk_USDC (Base) — gas fee shows N/A

[diegows]

Trying to withdraw from LazyVault_LowerRisk_USDC on Base (FleetCommander: 0x98C49e13bf99D7CAd8069faa2A370933EC9EcF17), post SIP2.59.4 execution.

Issue: Transaction fee preview shows “N/A” in the Summer.fi app, and the same happens calling redeem/withdraw directly via Basescan’s Write Contract tab — no gas estimate returned, transaction won’t simulate.

Already ruled out:

• Confirmed on Base mainnet (not testnet/other chain)
• Tested with both MetaMask and Brave Wallet — same result
• Tried a custom RPC (mainnet.base.org) — same result
• Confirmed sufficient ETH for gas (~$4)
• Checked balanceOf: 17,490.225692 shares
• Checked maxWithdraw: 18,771.690783 USDC available — so liquidity/cap isn’t the blocker
• Small test amounts also fail the same way

Given maxWithdraw returns a healthy number, this doesn’t look like a liquidity or balance issue — seems like something in the redeem/withdraw call itself is reverting silently before gas can even be estimated.

Any guidance on what else could cause a silent revert here, or whether others are seeing this post-unpause?

[jensei]

Hi @diegows and welcome to he Lazy Summer DAO forum. I can confirm that the vault is still paused. I was just answering similar question here:

[SIP2.59] Offboard legacy Arks across BA-managed Fleets

when sending the calldata with the proposal, there seemed to be some cached data - therefore the SIP2.59.4: Offboard legacy LazyVault_LowerRisk_USDC Arks (Base) will have to be resubmitted, voted on and executed for the vault to be unpaused. seems like this is the issue "just" with the Base LR USDC Fleet, and I will bring this proposal onchain later today (@Recognized_Delegates)

so, the DAO will have to vote on the proposal again, and the vault should become withdraw-able immediately after execution of said proposal (if-passed)