Overview
The shortest path from first visit to understanding how the live app behaves on Arbitrum Sepolia.
Before You Open The App
The current web3 client is a single-chain app for Arbitrum Sepolia. It is not a generic
multi-chain shell and it assumes the current contract snapshot from
frontend-app/web3-app/src/config/index.ts.
Use a wallet supported by the RainbowKit and wagmi integration in the app.
Switch to Arbitrum Sepolia before attempting a mint or burn.
Treat the flow as a protocol redemption flow, not a DEX swap. Burns can settle immediately or enter the queued exit lifecycle.
What Users Can Do Today
Mental Model
Users deposit native ETH through AMM.enter(...) and receive EVE. The frontend simulates
the write first and applies slippage to the minimum acceptable token output.
Users burn through AMM.exit(...). If AMM liquidity is sufficient, redemption is immediate.
If not, the request is queued in ExitQueue and later depends on keeper pricing and processing.
Queued burn expectation
A burn is not always final in one transaction. If your request enters the queue, the final
outcome depends on the batch price and your priceTolerance.
Last updated on