> ## Documentation Index
> Fetch the complete documentation index at: https://docs.thaler.finance/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating a vault

> Step by step instructions for opening your first Thaler vault. The full lifecycle starts here.

## Prerequisites

| Requirement | Detail                                                                                |
| ----------- | ------------------------------------------------------------------------------------- |
| Wallet      | A Solana wallet with at least 2 SOL, plus a small amount for network fees             |
| RPC         | The protocol uses a public RPC by default; a custom RPC can be configured in settings |
| Browser     | Any modern desktop or mobile browser that supports Solana wallet adapters             |

## The flow

<Steps>
  <Step title="Open the app">
    Navigate to `thaler.finance` and sign in with the Solana wallet. The protocol uses
    self-custodial sign-in; nothing leaves the wallet until the user approves a transaction.
  </Step>

  <Step title="Choose a tier">
    Open the **Create Vault** screen and select one of the six Thaler One tiers. The selector
    shows the APY range, the yield floor, and the minimum deposit for each tier. The minimum
    is fixed at 2 SOL for the beta.
  </Step>

  <Step title="Review the strategy">
    Read the strategy summary on the left side of the screen. It lists the three pillars the
    vault will use, the venues it will route through, and the immutable constraints baked into
    the policy.
  </Step>

  <Step title="Read the Terms and Policy Agreement">
    The acceptance modal opens when the user clicks **Create Vault**. Scroll to the bottom of
    the agreement and tick the acceptance box. The agreement covers the non-discretionary
    execution model, the dedicated worker that runs the strategy, the agent wallet that
    co-signs permitted instructions, and the immutable Squads policy extension.
  </Step>

  <Step title="Sign the creation transaction">
    Approve the transaction in the wallet. The transaction creates the smart account, signs
    the policy extension, takes the vault creation fee, and routes the deposit into the
    staking leg.
  </Step>

  <Step title="Wait for confirmation">
    Most vaults confirm in under thirty seconds. After confirmation the vault appears on the
    **My Vaults** screen and the worker begins building the three pillars within the policy
    bounds.
  </Step>
</Steps>

## What the creation transaction does

The transaction bundles four actions into a single signature.

| # | Action                                 | Effect                                                     |
| - | -------------------------------------- | ---------------------------------------------------------- |
| 1 | Create the Squads smart account        | A new on-chain account with the user as a co-signer        |
| 2 | Co-sign the policy extension           | The rule set is bound to the account and becomes immutable |
| 3 | Take the vault creation fee            | A small SOL amount goes to the protocol treasury           |
| 4 | Route the deposit into the staking leg | 2 SOL is staked through the chosen provider                |

No additional signature is required to start the lending and perpetual legs. The worker builds them inside the policy bounds the user just signed.

## Fixed deposit size

The beta accepts exactly **2 SOL** per vault. The amount input is locked so it cannot be set higher or lower. The lock applies whether the user chooses SOL or USDC as the deposit token; the USDC equivalent is routed to SOL using a same-chain LI.FI swap before the vault is funded.

The fixed deposit equalises capacity across early users and reduces operational variance during the first wave. Variable deposit sizing opens after the beta concludes.

## Depositing in USDC

If the user selects USDC as the deposit token, the protocol routes through LI.FI to swap USDC into the SOL equivalent of 2 SOL. The deposit form shows:

| Information shown        | Source                                        |
| ------------------------ | --------------------------------------------- |
| Estimated USDC required  | LI.FI route quote                             |
| Estimated SOL output     | LI.FI route quote                             |
| Selected aggregator      | LI.FI route quote (e.g. `jupiter`, `raydium`) |
| Estimated execution time | LI.FI route quote                             |

The swap happens in the same transaction as the deposit, so a partial fill never strands the funds.

## What the user does not configure

| Decision                 | Made by                                           |
| ------------------------ | ------------------------------------------------- |
| Staking provider         | Policy and current conditions                     |
| Lending market           | Policy (Kamino today)                             |
| Perpetual venue          | Policy (Hyperliquid or Pacifica)                  |
| Rebalancing rules        | Policy                                            |
| Stop-loss or take-profit | Not applicable; the strategy is non-discretionary |

The only choices the user makes at creation are the tier and the deposit token.

## Next read

<Columns cols={2}>
  <Card title="Claiming yield" icon="coins" href="/vault/claim">
    How accrued yield is settled, and the 24-hour cooldown that gates the claim button.
  </Card>

  <Card title="Closing a vault" icon="vault" href="/vault/close">
    The single-transaction unwind that returns the deposit plus accumulated yield in SOL.
  </Card>
</Columns>