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

# What is Red Potion

> An on-chain asset-management protocol where tenants launch tokenized funds and investors hold ERC-20 shares priced against NAV.

Red Potion is an on-chain asset-management protocol. A protocol operator onboards **tenants** — fund houses or organizations — and each tenant can launch any number of **tokenized funds**. Investors deposit assets into a fund, receive ERC-20 shares priced against the fund's net asset value (NAV), and redeem those shares back into assets. Fund operators put the deposited capital to work through allowlisted strategy wallets under configurable risk limits and fee schedules.

Red Potion is built with [Foundry](https://book.getfoundry.sh/), Solidity `0.8.34`, and OpenZeppelin v5 upgradeable contracts. Every contract is deployed behind a `TransparentUpgradeableProxy`.

## What you get

**One deposit, professionally managed.** You deposit a supported asset into a fund. The fund operator allocates that capital across strategies on your behalf — you never juggle positions or chase yield across protocols.

**Yield-bearing shares you actually hold.** Deposits mint you an ERC-20 share token unique to the fund. Your share count stays constant; the value of each share moves with the fund's reported NAV. Shares are freely transferable.

**Fair, batched pricing.** Red Potion does not use continuous AMM-style pricing. Deposits and redemptions collect into time-boxed **batches**, and every request in a batch settles at the same fair price once an operator submits and an operator accepts a NAV report. No one in a batch gets a better price than anyone else.

**Guardrails around every request.** Each fund can enforce TVL caps, per-batch caps, minimum deposit and redemption sizes, a drawdown gate, a depositor whitelist, and an emergency pause — all configurable per fund.

## The core idea in one paragraph

A fund is a **hub-and-spoke** system. The [Fund](/developers/contract-reference/fund) contract is the hub: it holds assets, orchestrates settlement, and acts as the single access-control registry. Around it sit spokes — a [DepositQueue](/developers/contract-reference/deposit-queue), a [RedeemQueue](/developers/contract-reference/redeem-queue), an [Oracle](/developers/contract-reference/oracle) (the batch clock and NAV reporter), a [FeeManager](/developers/contract-reference/fee-manager), a [RiskManager](/developers/contract-reference/risk-manager), and a [FundShare](/developers/contract-reference/fund-share) token. Capital is deployed through [Strategy](/developers/contract-reference/strategy) wallets that can only make explicitly allowlisted calls. Time is divided into batches; an off-chain reporter submits a price after each batch closes; after a mandatory review delay the report is accepted, settling all deposits and redemptions at one fair price in a single transaction.

## How this documentation is organized

<Columns cols={2}>
  <Card title="Overview" icon="compass" href="/overview/introduction">
    What Red Potion is and how batched fund shares work, in plain terms.
  </Card>

  <Card title="Using Red Potion" icon="wallet" href="/using-redpotion/fund-shares">
    Depositing, redeeming, fees, and the risk controls that apply to you.
  </Card>

  <Card title="Developers" icon="code" href="/developers/architecture">
    Contract architecture, a per-contract reference, the role model, and deployments.
  </Card>

  <Card title="Security" icon="shield-halved" href="/security/risks-and-safety">
    Risks, a glossary, and how to get help.
  </Card>
</Columns>

<Warning>
  **Risk.** Fund performance is not guaranteed and may fluctuate. Strategy losses reduce share price. You may lose some or all of your deposited assets. Past performance is not indicative of future results. See [Risks and Safety](/security/risks-and-safety) for full disclosures.
</Warning>