Guides

Depositing

Depositing is standard ERC-4626 and works as you would expect. Approve the vault, then deposit.

Steps

1

Approve the vault

cast send <asset> "approve(address,uint256)" <vault> <amount> \
  --rpc-url <rpc> --private-key $PK

2

Deposit

cast send <vault> "deposit(uint256,address)" <amount> <you> \
  --rpc-url <rpc> --private-key $PK

Returns the number of shares minted. Alternatively, mint(shares, receiver) if you want an exact share count and are willing to let the asset amount vary.

3

Confirm

cast call <vault> "balanceOf(address)(uint256)" <you> --rpc-url <rpc>

What to know

There is no deposit fee. Entry is free. The only fee you pay as a depositor is the exit fee on redemption. There is also no ongoing management fee.

Your assets leave the vault immediately. The deposit is forwarded to the Manager contract in the same transaction. This is by design, and it is why withdrawal requires a cooldown — see Withdrawing.

There is a minimum deposit size. It is expressed in shares, not assets. Deposits below it revert with InvalidMinShares.

cast call <manager> "minSharesInVaultToken(address)(uint256)" <vault> --rpc-url <rpc>

You start earning from the next report. Yield is credited through periodic reports, and profit vests over several days. A deposit made shortly before a report will not capture the full epoch's yield — this is deliberate, and it protects existing depositors from being diluted. See The share price.

Sizing a large position. If maxRedeemCap is non-zero, you can only redeem up to that amount per request, and you can only have one request pending at a time. A position larger than the cap must be exited sequentially — cooldown, collect, request again. Factor that into how long a full exit would take.

Errors you might hit

Error	Cause
InvalidMinShares	Deposit is below the minimum share threshold
InvalidDeposit	Zero amount, zero shares, or zero receiver address
EnforcedPause	The vault is paused
ERC-20 revert	Insufficient approval or balance