Security
Security boundaries define what the current interface can and cannot request. This page is not an audit report.
How it works
Wallet access is limited to public EVM account 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.
Business code is scanned for transaction, contract-write and signature methods.
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.
Review wallet permissions and destination addresses before every action.
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.