Whitelists
By default a vault is permissionless: anyone can deposit. If your mandate requires restricting participation (a private vault, an allowlist-only fund, a compliance requirement) you can enable whitelists from the Whitelists tab.
Two independent gates
| Gate | Controls |
|---|---|
| Deposit whitelist | Which addresses can deposit, mint, or claim new shares. |
| Withdraw whitelist | Which addresses can withdraw or redeem. |
Each gate turns on or off independently. You maintain a separate address list for each.
Enabling a whitelist
- Open the Whitelists tab in the vault console.
- Enable the gate you want: deposit and/or withdraw.
- Add the addresses to allow.
When the deposit whitelist is on, an address not on the list sees "Address not on the deposit whitelist" and cannot deposit.
The deposit whitelist is a mint gate
The deposit whitelist controls who can create new shares: deposit requests and the deposit-claim path. It does not restrict who can hold shares.
It does not block share movement by itself:
- Standard ERC-20 transfers, when enabled, can move shares to any address.
- Reducing a pending redeem request returns shares to the owner.
To restrict who can hold shares, keep transfers disabled. With transfers off, shares cannot move freely between addresses. T3tris has no "transfers allowed only between whitelisted holders" mode: transfers are either open or off.
To control who can deposit, enable the deposit whitelist. To control who can ever hold shares, enable the deposit whitelist and keep transfers disabled.
Withdraw whitelist
The withdraw whitelist restricts who can redeem. Use it when your mandate requires controlling exits as well as entries. An address not on the list is blocked from redeeming.
Operational notes
Enabling, disabling, and editing whitelists are onchain actions and require the relevant roles. Whitelisting interacts with your vault's visibility: a restricted vault is often also marked private.