How Withdrawals Work
Concrete vaults use a Withdrawal Queue to make redemptions predictable, secure, and fair. This protects both users and the protocol.
What Is the Withdrawal Queue?
If a vault uses a queue, this will be clearly shown in the Concrete App before you deposit.
When you submit a withdrawal request:
- Your request is added to a queue
- Funds are prepared and released in batches
- You’ll see your estimated withdrawal time in the app
- Track your withdrawal status in your Portfolio tab — you’ll see labels like “Queued”, “Processing”, or “Available”
Withdrawal Flow
Submit Withdrawal → In Queue → Funds Ready → Claim (if needed) → Tokens in Wallet (Wait up to 7 days)
Weekly Vault Batches
Async vaults process withdrawal requests in epochs configured per vault. The cadence — daily, weekly, or otherwise — depends on the vault's configuration, not a protocol-level rule. Each vault page lists its specific cutoff and processing schedule.
If Alice submits her request before Monday, June 3 at 12:00 PM UTC, she’ll receive her funds by Thursday, June 6. If she submits after the cutoff (e.g., Monday at 12:01 PM), her request will be included in the next week’s batch, and her funds will arrive by Thursday, June 13.
Withdrawal Caps Per Epoch
Some vaults may have a withdrawal cap that limits the total volume of redemptions processed in a single epoch, expressed as a percentage of vault TVL. Whether a cap is enabled, and at what threshold, is determined by the vault curator based on the strategy's liquidity profile and unwind capacity. Not all vaults use caps. Caps work alongside cadence to keep batch sizes predictable and aligned with the strategy's unwind capacity. By keeping redemption batches predictable, caps allow curators to maintain more consistent strategy execution, which can contribute to better vault APY over time.
To check the exact redemption process, including whether a cap is active and at what threshold, visit the withdrawal management page for the vault you are interested in.
How caps behave
When requests within an epoch stay under the cap, the batch processes normally at the scheduled time. When requests exceed the cap, only requests up to the cap threshold are processed in that epoch — the remainder roll forward to subsequent epochs and are processed in the order they were originally requested (First In First Out). Depositors waiting across multiple epochs continue earning yield until their portion is processed.
Say a vault processes withdrawals every Tuesday, with a cap of 20% of TVL per epoch.
If Alice submits a withdrawal request on Friday, May 29, her request joins the queue for the next batch on Tuesday, June 3. If total requests that week are under the 20% cap, Alice receives her funds by Friday, June 6.
If requests in a given epoch exceed the cap, the vault's withdrawal queuing service processes them in the order they were submitted (FIFO) across subsequent epochs. Alice continues earning yield on her position while she waits, and her funds are returned as her place in the queue is reached.
Cross-Chain Withdrawals (Bridging)
If your vault operates across two different chains (e.g., Ethereum → Berachain or Ethereum → Corn), you’ll need to bridge your vault tokens before you can receive your funds.
The app handles this automatically — no need to use an external bridge or tool. You’ll see exactly what to do in your Portfolio view when your funds are available.
Once your vault tokens arrive on the destination chain:
- Some vaults send funds automatically
- Others require you to click “Claim” when ready
Always confirm you control the destination wallet, if you're bridging to another chain in order to withdraw. Need to change your address after bridging? Follow our Request Address Change Guide
Why Withdrawal Queues Exist
Vaults deploy deposited assets into yield strategies. When the vault's idle balance is insufficient to fulfill withdrawal requests immediately, withdrawal queues let the vault deallocate from strategies in an orderly batch — protecting both the vault's integrity and the predictability of redemption.
Concrete uses queues to:
- Smooth out large withdrawals
- Maintain protocol liquidity
- Protect long-term earners
- Ensure no user is unfairly prioritized