# Overview

The rethink.finance dApp provides an intuitive interface for depositors, managers, and operators interacting with non-custodial vaults.

**Operators** can deploy and configure the set of smart contracts that together define a vault. Subject to governance and scoped permissions, they may settle flows (deposit and redemption requests), update NAV, and execute strategy logic within clearly defined operational boundaries.

**Depositors** can discover vaults, review their investment strategy, understand performance, inspect positions, verify parameters and delegated permissions on-chain, participate in governance, and request deposits or redemptions directly through the interface.

{% hint style="info" %}
You can find a detailed overview of all the mentioned contracts on the [Architecture](https://rokbehin.gitbook.io/rethink.finance/protocol/architecture) page.
{% endhint %}

***

## Main Success Scenario

1. **Operator** deploys a vault with predefined settings
   1. Basic info (Name, LP token symbol, denomination asset, image and description)
   2. Fees (Management fee, performance fee, deposit fee, redemption fee, etc.)
   3. Whitelist (If applicable)
   4. Management (Planned settlement period and min. liquid asset share)
   5. Governance (Type, gov. token, quorum, late quorum, voting period and proposal threshold)
   6. Initial supported positions (Scoped permissions for assets and protocols + NAV calculation methods)
2. **Depositor** finds a vault and requests a deposit
   1. Deposit gets processed with new NAV update, LP tokens get minted to depositor
3. **Operator/Automation** executes strategy on behalf of depositors
   1. Manual execution via existing protocol interfaces ([Pilot extension](http://pilot.gnosisguild.org/))
   2. Automated execution via script or AI agent (can be off-chain)
4. **Operator** and depositors (or their delegates) can create on-chain proposals to:
   1. Change initial supported positions
   2. Change initial vault settings
   3. Execute a raw transaction (interact with any contract/address)
5. **Operator** earns a fee
6. **Depositor** requests redemption
   1. Redemption gets processed with a new NAV update, LP tokens get burned, initial deposit + profit are claimed

***

## Discovery

<figure><img src="https://1901648714-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPooHz80vFLyZclBhWqez%2Fuploads%2Fjek7KHvUC0WHydL27Vu4%2FScreenshot%202026-01-23%20at%2012.26.46.png?alt=media&#x26;token=bf70d716-bac5-4023-8bf9-6ee7da0eefaf" alt=""><figcaption></figcaption></figure>

## Details

<figure><img src="https://1901648714-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPooHz80vFLyZclBhWqez%2Fuploads%2FnCoFer8aaGKURSHU3dlA%2FFrame%2014707.png?alt=media&#x26;token=826b0c73-de5b-4e3c-9a7b-32fd4d69df6b" alt=""><figcaption></figcaption></figure>