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

Deposit and repayment

PreviousArchitectureNextWithdrawal and borrowing

Last updated 2 months ago

Flow

Both deposit and repayment transactions will work in the similar technical flows as described below:

  1. Strobe lending core contracts will update their state after deposit or repayment to reflect the changes.

At first, user will send a to Axelar multisig account on XRPL. The sent amount, gas fee amount, payload, destination address, destination chain, will be included in of the transaction. In particular, the memo data representing the payload will contain information about the user action. In this case, it will either be deposit or repayment.

The XRPL <-> Axelar will pick up the payment transaction to Axelar multisig account, and forward the payload to . The GMP call is confirmed, approved, and executed on Axelar. At this point, user's funds are locked at Axelar multisig account.

The EVM Sidechain <-> Axelar relayer will approve and execute the message. When the message is executed, that inherits .

payment transaction
memos field
relayer
Axelar blockchain
Axelar ITS contract will add to the balance of Strobe's core contract, and call executeWithInterchainToken method of Strobe's core contract
IInterchainTokenExecutable