Skip to main content

Withdrawal Queue

Helm uses a FIFO withdrawal queue with a configurable claim delay to safely unwind positions when liquidity providers exit. The default delay is 3 days unless governance changes it. This protects remaining LPs and ensures the protocol can properly deleverage its Core positions.

Why a Queue?​

When you withdraw liquidity, the protocol needs to:

  1. Unwind the corresponding hedge position on HyperCore
  2. Bridge assets back from Core to EVM
  3. Rebalance the remaining pool composition

These operations take time and must be done carefully to avoid slippage and market impact. The queue ensures orderly processing.

How It Works​

Requesting a Withdrawal​

  1. Choose the amount of LP tokens to withdraw
  2. Submit the withdrawal request
  3. Your request enters the FIFO queue with the current claim delay cached on the request

Processing​

  • Withdrawals are processed in FIFO order (first in, first out)
  • The protocol's keeper system handles the unwinding and bridging
  • Once the cached delay passes and your position is at the front of the funded queue, you can claim

Claiming​

  • After the unlock period, return to the app and claim your tokens
  • Tokens are delivered to your wallet on HyperEVM

Instant Withdrawals​

If the pool has sufficient EVM-side liquidity, you may be able to withdraw instantly:

  • A small fee is charged for instant withdrawals
  • Available liquidity depends on current pool composition and pending operations
  • Not always available — depends on pool state

Important Notes​

  • Withdrawals are processed strictly in FIFO order — no queue jumping
  • The withdrawal amount is locked at request time, not at claim time
  • Users cannot directly cancel a withdrawer request after it is created
caution

Before confirming, check the amount and recipient carefully. The protocol owner has an escape-hatch cancellation path only for requests that cannot be claimed; cancelled requests refund LP shares instead of withdrawing tokens.

Next Steps​