DevelopersProtocol
High-level architecture
The current contract and application architecture behind deposits, strategy management, redemptions, and indexing.
Main Components
| Layer | Components | Role |
|---|---|---|
| Immutable core | EVE, AMM | Token mint/burn and user entry/exit surface |
| Upgradeable management | Controller, ExitQueue, StrategyManager, Oracle, Converter | Strategy operations, queue state, NAV, valuation, conversion routes |
| Authorization | Registry, Whitelist, Timelock | Peers, roles, invite entry, delayed ADMIN actions |
| Automation | Mimic W1/W2 and keeper executors | Authenticated queue and strategy operations |
| User interface | everstrat-xyz/app | Mint/burn, Portfolio, Metrics, transaction UX, account details |
| Data layer | GoldSky subgraph | Activity feed, request history, user aggregates |
See the contract architecture diagram.
Key Relationship
Users interact through AMM entry (including invite authorization), exit, cancellation, and claim.
Core Rule
The hot path is ETH-first:
- AMM price calculations are based on ETH NAV.
- Normal enter/exit read NAV, which can depend on Oracle feeds and pool TWAPs.
- Oracle is also used directly for bootstrap USD validation and USD-denominated views.
Read next:
Last updated on