Architecture
The application separates market data, fee resolution, wallet reads and protocol actions. That separation allows each layer to evolve without rebuilding presentation components.
How it works
The wallet adapter represents public address, chain and balance reads.
The interface applies this rule consistently across market details, position management, and rewards. Market state, fee inputs, and position ranges remain separate so each layer can update without changing the underlying product model.
The protocol adapter isolates position actions from presentation components.
The interface applies this rule consistently across market details, position management, and rewards. Market state, fee inputs, and position ranges remain separate so each layer can update without changing the underlying product model.
Network reads and protocol actions follow separate permission boundaries.
The interface applies this rule consistently across market details, position management, and rewards. Market state, fee inputs, and position ranges remain separate so each layer can update without changing the underlying product model.
Important considerations
Liquidity provision involves price, range, smart-contract, issuer, keeper, and network risks. Wallet access is limited to public account discovery and balance reads. Review current market conditions and every wallet request before taking action.