What happens in an incident
If a critical issue is detected, guardian controls pause execution components to contain risk quickly.
Pause is an incident-response control. It is intended to stop unsafe normal flows while preserving user recovery paths.
Pause impact at a glance
| Area | What users should expect |
|---|---|
| Normal lifecycle actions | Open, manage, and exit actions are unavailable while pause is active. |
| Pricing and safety controls | Protective checks remain in place; unsafe execution paths stay blocked. |
| Recovery path | returnNft remains the key user recovery mechanism during pause scenarios. |
Who can do what during pause
| Role | Operational scope |
|---|---|
| Users | Can call returnNft to recover direct NFT custody for manual or external handling. |
| Guardian | Triggers and lifts pause for incident containment. |
| Governance/timelock owner | Handles policy/config changes and can execute coordinated returnNft recovery actions during pause. |
returnNft recovery path
Position owners can call returnNft at any time to recover direct custody of their LP NFT outside managed protocol flows.
During pause, governance can also execute returnNft recovery for positions, and custody is sent directly to each owner wallet, never to protocol owner wallets.
After returnNft, the protocol no longer controls that NFT or manages that position. The lifecycle is recorded as exited at current value in accounting and history.
Recommended user response during pause
- Confirm incident status from official protocol channels and on-chain pause state.
- Use returnNft if you need direct custody for external/manual risk management.
- Track follow-up governance and recovery updates before re-enabling normal automation assumptions.