Start: deallocate from strategy
Check Which deallocation routes are configured?
Check the documentation for which direct / swap / unwrapAndSwap paths are enabled for this strategy. Using the wrong route will revert.
Route A — Direct
deallocate(adapter, amount)
Strategy unwinds directly into vault asset with no DEX swap.
Called by Allocator Admin or Operator on Allocator Contract
OR
Route B — Swap
deallocateWithSwap(adapter, amount, txData)
Strategy sells held token directly into vault asset in one swap.

txData = 0x quote for held token → vault asset, taker = strategy address.
Called by Allocator Admin or Operator on Allocator Contract
OR
Route C — Unwrap + Swap
deallocateWithUnwrapAndSwap(adapter, amount, txData, minIntermediateOut)
Held token unwrapped first, then intermediate swapped to vault asset.

txData = 0x quote for intermediate token → vault asset.
minIntermediateOut = quote's sellAmount.
Called by Allocator Admin or Operator on Allocator Contract. Detailed walkthrough →
Done
Constructing 0x txData: Call the 0x Swap API off-chain with sellToken, buyToken, sellAmount, and taker = strategy contract address. The API returns encoded calldata to pass directly as txData. Quotes are time-sensitive — fetch and submit in the same session. The strategy approves the 0x AllowanceHolder internally. The Alchemix Admin UI should be used to construct txData when available.
User route — Force deallocate (TBD)
forceDeallocate() — permissionless in-kind redemption. Status and penalty configuration under review.