Minimum Shares

Minimum Shares Explained in Detail

Minimum shares is a user-provided lower bound for how many shares they must receive. If the vault or pool would mint fewer shares, the transaction should revert.

This is similar to minimum output in a swap.

Smart contract example

require(shares >= minShares, "too few shares");

The check protects against bad execution after the user signs or submits the transaction.

Minimum Shares in Auditing

Without a minimum-share check, a user can deposit assets and receive too few shares because of rounding, fees, donations, share-price manipulation, or front-running.

Auditors check vault and strategy entry points for output protection.

Red flags in code

• Deposit function accepts assets but no minShares or equivalent guard.

• shares > 0 is the only protection.

• First-deposit and low-supply states are not tested.

• previewDeposit is treated as a guaranteed result.

• Routers omit user-supplied minimum output.

How to test or review it

• Simulate attacker deposit plus direct donation before victim deposit.

• Test empty vault, dust supply, and low-liquidity states.

• Verify user-provided minimum shares are enforced.

• Compare preview results with actual minted shares.

• Test rounding direction around one-share boundaries.