Key risks
Capital, valuation, governance, liquidity, and automation risks for EVE holders.
Experimental mainnet deployment
Entry is invite-gated. Deposits are real ETH at real risk. No principal protection or guaranteed return exists, and there is no insurance protecting deposits; do not deposit more than you can afford to lose entirely.
NAV and capital losses
EVE's redemption price follows net NAV per live share. Strategy losses, token price changes, execution costs, accounting errors, and vulnerabilities can reduce that value. Deposits growing aggregate NAV do not establish investment returns.
Concentrated-liquidity exposure
The registered strategies at the dated deployment snapshot use four Uniswap v3 pools. Concentrated LP positions can underperform holding their underlying assets, lose value, or require swaps to satisfy ETH withdrawals.
They share the UniCL strategy family and infrastructure. Not every deployed instance has identical bytecode, but shared logic, Uniswap dependence, feeds, and market exposures mean four pools do not provide four independent risk systems. Paired-token amounts depend on the position's range; there is no fixed 50/50 allocation.
Exit delays
If AMM has insufficient free ETH, an exit is queued. The Mimic queue and strategy tasks must price requests and make liquidity available for processing. Gas caps, outages, failed reads, pauses, strategy capacity, and liquidity conditions can delay this work.
At the snapshot, the queue keeper waited until a batch was 24 hours old before automatic pricing. After pricing, a separate three-day processing window applies. Neither is a promise that ETH will arrive at the end of that period.
A priced request that is still unprocessed strictly more than three days after pricing can no longer be paid. Its only recovery is cancellation, which returns EVE and pays no ETH. Credited ETH from processed requests stays claimable. The exact rules are in The redemption queue.
Automatic AMM immediate-liquidity top-up was disabled at the snapshot. Do not assume an always-funded immediate-exit buffer.
Settlement price and slippage
A queued exit is priced later than submission. A final batch price outside the user's
priceTolerance causes EVE to be returned when the request is processed, rather than
settling ETH. Wider tolerance accepts more downside; narrower tolerance can prevent an exit.
Mint-output and exit-input bounds protect execution against the user's limits, including queued escrow. The deployed AMM does not provide a 5% checkpoint guard or a principal-loss limit.
Oracle and pool dependence
Normal ETH entry and exit read StrategyManager NAV. That NAV can depend on token price feeds and pool TWAPs even when no direct ETH/USD conversion is performed by AMM. Stale, invalid, or unavailable valuation inputs can therefore block normal trading and batch pricing.
USD displays and the historical bootstrap minimum also have direct oracle dependencies. ETH-denominated accounting should not be described as oracle-free.
Valuation failure and removal
A failed registered strategy NAV read can block aggregate NAV. Claims and eligible cancellations remain available without fresh NAV, so this is not a universal shutdown.
Recovery may require governance. Force-removing a strategy or removing a supported ERC-20 from accounting does not recover its capital; it removes that value from reported NAV. That makes it an accounting and governance risk as well as an availability fix.
Governance and upgrade risk
ADMIN controls registered peers, strategies, feeds, fees, and upgradeable management code. SECURITY has immediate designated emergency authority. A 48-hour timelock creates advance visibility but cannot guarantee that a queued or paused position can be redeemed before execution.
Proposed v2 strategies are a different build. Registration and migration must be confirmed on-chain, and review coverage must identify the build it actually covers.
Data and review limitations
Historical app data depends on indexer and snapshot availability. Missing history or prices must not be interpreted as zero assets or zero return. App charts are accounting estimates, not guaranteed payouts or proof of profit.
No completed independent audit report was verified in this repository review. See Security & audits.
Operational assumptions
Pricing relies on accurate strategy NAV and available keeper execution. App and indexing operators must maintain the intended mainnet deployment, environment configuration, and data endpoint. These dependencies are explained in Operational trust. Recovery procedures live in Operations.
Last updated on