Burn UI
Approval, burn submission, queued-request blocking, and cancellation in the live app.
Burn UX Responsibilities
- check EVE allowance
- prepare
approve(...)when needed - simulate
AMM.exit(...) - block duplicate current-batch queued burns
- expose cancellation when protocol rules allow it
The amount label is You will burn. Minimum queued-exit feedback belongs only to Burn mode and must not appear after switching to Mint. The minimum is conditional on a queued exit; it is not a general mint minimum.
Portfolio shows current request actions and claimable ETH independently of historical activity. A processed queued exit requires a separate claim.
Current Write Shapes
EVE.approve(AMM, burnAmount)
AMM.exit(requestedEth, burnAmount, burnPriceTolerance)
AMM.cancelRedemption(batchId)requestedEth is the quoted ETH for burnAmount at the current base price, reduced by a 0.1%
buffer (BURN_REQUEST_BUFFER_BPS). exit() reverts with AMMTooMuchETHRequested if the requested
ETH would need more EVE than burnAmount at execution-time NAV, so an unbuffered quote fails on any
NAV drop between quote and inclusion. With the buffer, burnAmount acts as the maximum burn and
any EVE not needed stays in the wallet.
Important Detail
The pending-request block is based on direct contract reads into the current batch, not on subgraph-only state.
Last updated on