rethink.finance
  • Getting Started
    • Welcome
    • Rethinking Vaults
  • dApp
    • Overview
  • Protocol
    • Architecture
      • Admin Contract
        • Flows
          • V1.0 Flows
          • V2.0 Flows
        • Fees
          • Performance Fee
          • Management Fee
          • Deposit Fee
          • Redemption Fee
      • NAV Calculator Contract
        • NAV Liquid Spot
        • NAV Illiquid
        • NAV DeFi Composable
        • NAV Methods Library
    • Security
    • Integrations
  • Execution
    • Manual
    • Algo/AI
  • Community
    • Closed Beta
  • Policies
    • Terms of Service
    • Privacy Policy
  • Links
    • GitHub
    • Discord
    • X
Powered by GitBook
On this page
  1. Protocol
  2. Architecture
  3. Admin Contract
  4. Flows

V1.0 Flows

1. Depositor requests a deposit.

2. Depositor approves the amount.

3. Manager triggers the NAV update.

4. Depositor comes back and processes request (sends asset to fund contract at previous NAV price and receives LP tokens in return).

Pros:

  • This was a faster implementation for MVP.

  • There is an incentive to generate speculative volume in/out of the vault (because some investors/managers might benefit from Con 1).

  • Investors do not need to deposit before the NAV update happens.

Cons:

  • Investors might be entering vault at a price that is no longer relevant (and benefit from it).

  • Investors are required to come back to the app at different times to process requests (broken flow, and unpredictable for managers).

  • There might be capital locked in the fund contract because investors requested redemption, but haven't processed the request.

PreviousFlowsNextV2.0 Flows

Last updated 1 month ago