Skip to main content
Depositing into a Red Potion fund is a two-stage process: you queue a deposit into the current batch, and later claim the shares once that batch settles. This page walks the full path.

​
The timeline

1

Request

You call deposit(asset, amount, proof) on the DepositQueue. For an ERC-20 you approve the queue first; for native ETH you send msg.value equal to amount.The queue checks the deposit against the fund’s RiskManager (whitelist, caps, minimums) and escrows your assets. Your request joins the current batch.
2

Wait for settlement

The batch closes at its cutoff. A reporter submits the NAV price; after the mandatory review delay, an operator accepts the report. Acceptance settles the whole batch at one price.
3

Claim

You call claimDeposit(asset, batchId) and receive your pro-rata share of the batch’s minted shares. There’s no deadline — claim whenever you like.

​
Your price is the next accepted report

An important subtlety: when you deposit, you do not lock in the current price. Your batch settles at the next NAV report accepted after the batch closes. Risk checks (like caps and minimums) are evaluated at request time against the last known price, but the actual conversion uses the fresh settlement price. This is what guarantees every depositor in the batch the same, forward-looking fair price.

​
One request per batch

You can have at most one open deposit request per asset per batch. Depositing the same asset again in the same batch reverts — cancel and re-deposit if you want to change the amount, or wait for the next batch.

​
Cancelling

You can cancel your current-batch deposit any time before it settles by calling cancelDeposit(asset), and you’ll be fully refunded. Once the batch settles, cancellation is no longer possible — you instead claim your shares. A fund admin can also cancel a stuck request in any unsettled batch, refunding you.

​
Claiming — the math

When your batch settles, the Fund mints a total number of shares for the whole batch. Your claim is pro-rata to your share of the batch’s deposits:

​
What can block a deposit

The RiskManager can reject a deposit for any of these reasons. Each control is optional per fund: See Risk Controls for details on each.