Skip to main content
Depositing is two stages: queue into the current batch, then claim shares after that batch settles.

​
Timeline

1

Request

Call deposit(asset, amount, proof) on the DepositQueue. Approve the queue first for ERC-20s; for native ETH send msg.value equal to amount.The queue checks RiskManager (whitelist, caps, minimums) and escrows assets. The request joins the current batch.
2

Wait for settlement

After cutoff, a reporter submits NAV; after the review delay, an operator accepts. Acceptance settles the batch at one price.
3

Claim

Call claimDeposit(asset, batchId) for your pro-rata shares. No deadline.

​
Price is the next accepted report

Depositing does not lock the last known price. Settlement uses the next accepted NAV after the batch closes. Risk checks (caps, minimums) use the last known price at request time. Conversion uses the settlement price. That is how every depositor in the batch gets the same forward price.

​
One request per batch

At most one open deposit request per asset per batch. A second deposit of the same asset in the same batch reverts — cancel and re-deposit, or wait for the next batch.

​
Cancelling

Cancel a current-batch deposit before settlement with cancelDeposit(asset) for a full refund. After settlement, cancel is unavailable — claim shares instead. A fund admin can cancel a stuck request in any unsettled batch and refund you.

​
Claim math

​
What can block a deposit

Optional per fund via RiskManager: See Risk controls.