ExitQueue

ExitQueue tracks redemption requests; AMM holds their EVE escrow and claimable ETH.

LifecycleCopy Anchor Link

1. AMM escrows EVE and records a request in the current unpriced batch.
2. Controller prices the batch and opens a new batch.
3. Controller funds processing through AMM, which applies the request tolerance, burns escrow, and credits claimable ETH.
4. The user claims ETH from AMM separately.

The registered Controller may price batches. The registered AMM may create, process, or close requests. These are registered-address checks; there are no separate AMM or Controller roles.

AccountingCopy Anchor Link

liveRedemptionOffsets() returns the ETH liability and matching EVE escrow of priced, unprocessed requests that are still within their processing window. StrategyManager subtracts the liability from gross assets; AMM and performance-fee math exclude matching escrow from live supply.

Unpriced requests remain equity. Processed requests instead reserve ETH in AMM lockedForClaims. Expired, unprocessed requests stop contributing live offsets.

Limits and cancellationCopy Anchor Link

• Maximum 25 live priced batches.
• MAX_BATCH_PROCESSING_TIME = 3 days, measured from pricing.
• An unpriced request can be cancelled.
• A priced, unprocessed request can be cancelled strictly after three days. At exactly three days, it is still in the processing window.
• Strictly after three days, an unprocessed request cannot be processed (ExitQueueBatchExpired). Cancellation returns EVE; it does not pay ETH. Already credited ETH remains claimable.
• A processed request cannot be cancelled; its ETH remains claimable.

Cancellation through AMM can close eligible requests while the queue is paused. Pausing normal processing does not erase the user's claim or eligible cancellation.

The keeper's configurable minimum batch age is a separate delay before pricing. See Keepers and automation.