Skip to main content
These diagrams follow each depositor and manager flow through the Loopscale app, the Loopscale APIs, and the underlying Exponent Strategy Vault. Instruction names are from the Exponent vault program.

​
Deposit

What happens:
  • Shares minted = deposit value × share supply ÷ total AUM, computed against the AUM refreshed earlier in the same slot.
  • The deposit reverts if it would mint fewer than min_lp_out shares or push the vault past its deposit cap.
  • Deposited capital starts in the vault’s reserves. The allocator then deploys it according to the strategy.

​
Queued Withdrawal

  • A request can be filled in several partial fills, and each fill can pay out in a different token entry.
  • Claiming needs both a fill and an unlocked withdrawal period (a lock interval, or the vault’s scheduled withdrawal days).
  • The manager has to clear queued requests before each window closes. If they don’t, the vault blocks new manager actions until they do.

​
Cancelling a request

Cancelling is only possible on vaults that allow it, after the vault’s cancel cooldown, and (in the Loopscale app) only before any part of the request has been filled.

​
Instant Withdrawal

Instant withdrawals skip the queue but are limited by available reserves and the vault’s per-window instant cap (see Withdrawals). The instant fee stays in the vault, compensating remaining depositors for the drain on liquidity.

​
Strategy Rebalance (Manager)

Depositors never sign rebalances. Their protection comes from the policy whitelist and the post-hook checks running atomically with every action.

​
Parameter Change (Governance)

Changes to fees, reserves, withdrawal schedule, deposit cap, roles, token entries, and policies all take this path once a vault holds depositor capital.