> For the complete documentation index, see [llms.txt](https://cheomayield.gitbook.io/cheomayield-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cheomayield.gitbook.io/cheomayield-docs/deposit-flow.md).

# Deposit Flow

## Deposit

1. User approves the stablecoin (USDC / USDT / bnUSD / USDG) to the vault contract.
2. User calls `deposit(amount)`.
3. The contract calls `_accrue()` first — interest is computed deterministically from `block.timestamp`, so there is no discrete rate jump to front-run.
4. Stablecoin is transferred in; receipt shares are minted (round-down, no dilution of earlier holders).
5. A **FIFO lot** is recorded for the deposit, with `maturity = timestamp + 90 days` (legacy `CheomaPreDeposit`; the current `BasePreDeposit` / `SonicPreDeposit` vaults have no per-deposit lock and no on-chain user redeem — withdrawals open with the phase-2 gate on GIWA mainnet).

## Interest

* Simple (non-compounding) interest: `interest = totalAssets × apyBps × elapsed / (10000 × 365 days)`.
* Accrues continuously and settles on-chain at the next deposit/redeem.

## Redeem

1. User calls `redeem(shares)`.
2. Requires the deposit's 90-day lot to be mature **and** `withdrawalsOpen == true` (admin-controlled).
3. Receipt shares are burned; the user receives pro-rata principal + accrued yield in the deposit asset.

## Custody / withdrawals

* Only `treasury` can call `withdraw` or `emergencyWithdrawAll`. The `admin` key can configure the cap and open/close deposits & withdrawals but **cannot** move funds.

## Receipt token

Receipt tokens (`ch1USDC`, `chGIWA`, `chSonic`) are the legacy pre-deposit receipts: `ch1USDC` and `chGIWA` are **soulbound** (non-transferable by design), `chSonic` is transferable. The current pre-deposit receipts are **`prechUSDCb`** (Base) and **`prechUSDCs`** (Sonic) — both **transferable** ERC-20s (DeFi composability). They represent the user's claim, not a tradeable position.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cheomayield.gitbook.io/cheomayield-docs/deposit-flow.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
