Strobe Protocol
  • Introduction
  • Terminology
  • Products
  • Money market
    • Rationale
    • User guide
    • Architecture
      • Deposit and repayment
      • Withdrawal and borrowing
      • Liquidation
      • EVM Sidechain lending internals
    • Interest rate strategies
      • Interest rate strategy 1
    • Asset parameters
      • Definitions
      • Values
    • Overcollateralization and collateralization ratio
    • Health factor and liquidation
    • Oracle
    • Axelar
      • General message passing
      • Failure conditions and solutions
    • Risks
    • FAQ
  • Useful links
Powered by GitBook
On this page
  1. Money market
  2. Architecture

Liquidation

PreviousWithdrawal and borrowingNextEVM Sidechain lending internals

Last updated 2 months ago

Flow

Liquidation may occur when the user's supplied collaterals are not sufficient to maintain the coverage ratio over his debts (e.g. LTV%). Refer to Health factor and liquidation for more insight.

  1. A liquidator program will be monitoring and detecting accounts not meeting the debt coverage ratio (accounts subject to risk of being liquidated, or "to-be-liquidated") by querying data from the indexer.

  2. Upon detecting the "to-be-liquidated" accounts, the liquidator account will send a liquidation transaction to the Strobe core contract.

  3. Sometimes, the liquidator account may not have sufficient balance of specific token to run the liquidation. In such scenario, the liquidator account will execute a swap through XRPL DEX, Squid Router, or any other DEXs to obtain the desired borrowed assets to liquidate the debts.

For more on liquidation mechanics, please refer to Health factor and liquidation.

The indexer will collect the events from the core contract and prices from 's on-chain price feeds contract.

Band Protocol