Allowlist
King's Vault V2 is permissioned: only addresses granted the Investor role on a vault can deposit into it or withdraw from it. This page states exactly what that gate covers and what it does not.
What the allowlist gates
| Action | Gated | Enforced by |
|---|---|---|
deposit, mint |
Yes — the receiver must hold Investor |
_deposit … onlyRole(Roles.INVESTOR); maxDeposit / maxMint return 0 otherwise |
withdraw, redeem |
Yes — the owner of the shares must hold Investor |
_withdraw … onlyRole(Roles.INVESTOR); maxWithdraw / maxRedeem return 0 otherwise |
claim (async vault) |
Yes | same |
emergencyRedeem |
Yes | same |
What it does not gate
| Action | Gated | Consequence |
|---|---|---|
Transferring vault shares (transfer, transferFrom) |
No — shares are standard ERC-20 tokens | An address outside the allowlist can hold shares. It cannot withdraw them; it can transfer them onward or back to an allowlisted address. |
| Reading vault state | No | Anyone can read balances, NAV, and events. |
What the allowlist is not
- It is not identity verification. King's Vault does not collect or verify personal information; the list contains wallet addresses only. See the Privacy Policy.
- It is not a promise of continued access. The
Adminrole can grant and revokeInvestorat any time. A revoked address keeps its shares but can neither withdraw nor emergency-redeem until re-admitted; see Exit paths. - It is per vault. Being admitted to one product does not admit an address to another.
How an address is admitted
The Admin of the vault calls grantRole(Roles.INVESTOR, address). The grant is an on-chain event (RoleGranted) and takes effect immediately.
Third-party integrations
Investor is an address role, so it can be granted to a contract as well as to a wallet. A partner's own vault, custody contract, or gateway contract can therefore be admitted as a single depositor, hold King's Vault shares on behalf of its own users, and apply its own access rules, fee structure, and reporting in front of King's Vault. Because King's Vault vaults follow ERC-4626, such a contract interacts with them through the standard deposit / redeem / convertToAssets interface with no King's Vault-specific integration.
In that arrangement the partner contract is the allowlisted party; King's Vault's own list does not see or govern the partner's end users.