Security
Security boundaries define what the current interface can and cannot request. This page is not an audit report.
How it works
Connecting a wallet reads public EVM account data.
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.
Chain writes are isolated to treasury contributions and never request a token approval.
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 the network, full destination address, amounts and every wallet request before confirming.
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.