Permissions
Connecting a wallet exposes only the public account details required by the interface. A treasury contribution is a separate action that requires explicit transaction confirmation.
How it works
No token approval is requested.
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.
No message or typed-data signature is requested.
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.
Only the TreasuryTransferAdapter can submit native or ERC-20 transfers to the configured treasury.
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.