shift
  • Introduction
  • Underlying factors for developing shift
  • Get started
    • How to choose the Vault
    • How to deposit
    • How to withdraw
    • How to shuffle between Vault versions
    • How to track the balance
    • How to review transactions history
    • Emergency situation
  • SHIFT Products
    • Vault
    • DeFi strategy
    • Vault for Financial Institutes
  • Risk Management
    • Overview
    • Risk Assessment and Management Policy
    • Risk Mitigation
  • Developer Resources
    • Ecosystem overview
    • Vault contract
      • Position status logic
    • DEFII
      • Logic contract
      • LocalDefii contract
      • RemoteDefiiPrincipal contract
      • RemoteDefiiAgent contract
      • Instructions
    • OperatorRegistry contract
    • Emergency situations
    • Deployment addresses
  • Vaults
    • USD - Risk Level 3
  • FAQ
    • General
    • Fee terms
    • Platform design
    • Emergency
    • Utility
    • Security
    • Communication
  • Resources
    • Discord
    • Medium
    • Twitter
    • Telegram
    • Github
Powered by GitBook
On this page
  1. Developer Resources

Emergency situations

During the operation of the protocol, various emergency situations may arise. For example, these could be:

  1. A bug in the smart contract.

  2. A MAJOR trigger was activated.

  3. An exploit.

In such situations, the owner of DEFII calls emergencyExit(), after which the liquidity is withdrawn from the third-party protocol to the DEFII contract.

To exit from DEFII, the user simply needs to call the withdrawFundsAfterEmergencySituation() function in the LocalDefii or RemoteDefiiAgent contract, and the funds from DEFII will be sent directly to the user's wallet.

Last updated 1 year ago