Withdraw supported funds from your Smart Vault to your connected owner wallet or another reviewed recipient. If you choose another network, the withdrawal and bridge are separate stages. Check the destination, asset, network, and amount before approving either.
Withdraw on the current network
Section titled “Withdraw on the current network”- Sign in with the Smart Vault’s owner wallet and open My Smart Vault.
- Select Withdraw and choose the connected wallet or another wallet as the destination. For another wallet, enter the full recipient address and check it carefully.
- Check the network, asset, available balance, and amount. Max uses the available vault balance. Switch your connected wallet to the requested network if needed.
- Review the withdrawal and confirm it in your owner wallet. Wait for the result, then check the recipient and the transaction status.
A loading balance, unavailable token details, wrong network, or unresolved earlier withdrawal can keep the form unavailable. Use the displayed status or read-retry action; do not create another withdrawal to work around an unknown result.
Withdraw to another network
Section titled “Withdraw to another network”The guided bridge requires a connected owner wallet on Base, verified Base USDC, and an available route. Available destination networks and assets depend on the routes offered at the time.
- In Withdraw, choose Another wallet, then Another network.
- Review and approve the withdrawal of Base USDC to your own connected Base wallet. This is the intermediate step, not delivery to the final destination.
- After the withdrawal is confirmed, choose the destination network, asset, and recipient in the bridge flow. Review its quote and any separate approvals or signatures.
- Track that route until its result is clear. Check the destination transaction or receiving wallet before treating the transfer as delivered.
When a bridge needs attention
Section titled “When a bridge needs attention”If the withdrawal is confirmed, do not withdraw the same funds again for this transfer. Use Check bridge status for the saved route. If the app asks for a Base transaction hash, use the matching hash from your wallet for that route. The withdrawal hash and bridge hash can identify different stages.
A missing hash, unavailable route status, or interrupted screen does not prove the bridge failed or returned funds. Keep the existing attempt and do not start another route while it is unresolved. See pending actions for status checks and the details to give support.
Liquidity pools use a separate request-and-claim process. See provide liquidity; a personal Smart Vault withdrawal is not an LP redemption.
Frequently asked questions
Section titled “Frequently asked questions”Why can I not withdraw yet?
Section titled “Why can I not withdraw yet?”Check the connected owner wallet, requested network, token details, balance, recipient, and amount. Wait for loading data or use the displayed read-retry action. If an earlier withdrawal is unresolved, check that attempt first; do not start another to bypass it. A bridge also needs verified Base USDC and an available route. If the form stays unavailable, contact support with the public wallet address and message shown.
What if I reject the wallet request?
Section titled “What if I reject the wallet request?”If you declined the wallet request before submission, that request was not approved. Check the transaction view before starting again, especially if the message is unclear or the wallet shows a hash. An uncertain submitted withdrawal must be checked as the same attempt; see pending actions.
The form says the withdrawal failed or keeps waiting. Can I try again?
Section titled “The form says the withdrawal failed or keeps waiting. Can I try again?”Check the same withdrawal in Chain and your wallet before trying again. Use Check transaction status when offered, and enter a replacement hash only when it belongs to that attempt. A timeout or missing hash does not prove failure. If the withdrawal to your owner wallet is confirmed but a bridge is unresolved, do not withdraw again or start another route. Follow withdrawal and bridge recovery and keep the transaction details for support.