Everstrat.xyz | Docs
Get Started

Burn and redeem

The live burn flow, including approval, immediate redemption, queued redemption, and cancellation.

Burn Is A Redemption Flow

The app does not model burn as a spot swap. It prepares protocol writes around AMM.exit(...) and AMM.cancelRedemption(...).

If AMM liquidity is sufficient, the burn settles immediately and the indexed outcome is BURN_IMMEDIATE.

If liquidity is insufficient, the request is added to ExitQueue, later priced by a keeper, and then processed or closed depending on tolerance and timing.

Current Frontend Behavior

Check EVE balance, AMM allowance, base price, and current pending request state.
If allowance is insufficient, submit EVE.approve(AMM, amount) first.
Simulate AMM.exit(requestedEth, maxTokensToBurn, priceTolerance).
If a pending queued request already exists in the current batch, block creating another one.

Canceling A Pending Burn

The app exposes Cancel Pending Burn only when the request can be closed under the protocol rules. That includes unpriced requests and escape-hatch closures after MAX_BATCH_PROCESSING_TIME.

Read more in:

Last updated on

On this page