Permission Matrix
The role names in the contracts (Admin, Developer, Keeper, Guardian, Investor, manager) describe who. This page reorganises the same permissions by what kind of power each one is, which is the question a risk reviewer asks first:
- Add risk — move depositor funds into an external protocol, or widen where they may go.
- Remove risk — pull funds back, or stop activity.
- Take value — set or receive fees.
- Change settings — roles, registries, parameters.
- Change code — upgrade a contract's logic.
Status as of 2026-09-27. Function names refer to kingsvault-v2 main (6add944). For who actually holds each role, see Key holders.
Matrix
| Role | Add risk | Remove risk | Take value | Change settings | Change code |
|---|---|---|---|---|---|
Admin (DEFAULT_ADMIN_ROLE) |
— | — | Sets the fee receiver (setManager) |
Grants and revokes every role; confirms NAV epochs (confirmValues) |
Yes — upgrades Controller and HyperCoreAllocator |
| Developer | Widens where funds may go: registers vaults, adds strategies (registerVault, strategyAdd), adds HyperCore routers |
Narrows it: removes strategies (strategyRevoke) |
— | — | — |
| Keeper | Moves funds into strategies (fundInvest); allocates on HyperEVM (allocate, router steps) |
Moves funds out (fundDivest, fundReplenish); executes async redemption rounds; relays cross-chain returns |
Sets the performance fee rate (setFeeRate, ceiling below 100%) |
Proposes NAV epochs (proposeValues) |
— |
| Guardian | — | Pauses and unpauses vaults; permanently shuts a vault down and triggers strategy exits (shutdown, vaultExit) |
— | — | — |
| Investor | — | Withdraws or redeems own shares; claims async redemptions; emergencyRedeem after shutdown |
— | — | — |
| manager (fee receiver) | — | — | Receives fee shares and harvested tokens | — | — |
Function-level view
The same permissions, listed by function. A filled cell means the role can call it; a blank cell means it cannot. Every function has exactly one role, and the two steps that move the share price — propose and confirm — sit with different roles.
| Function | Investor (user) | Keeper | Developer | Admin | Guardian |
|---|---|---|---|---|---|
Deposit · withdraw · redeem · claim; emergencyRedeem after shutdown |
● | ||||
Move funds between vault and strategies (fundInvest, fundDivest); execute async rounds; relay cross-chain messages |
● | ||||
Propose valuation (proposeValues); set fee rate (setFeeRate, snapshotted at proposal) |
● | ||||
Confirm valuation (confirmValues, ≤ 1 h after proposal) |
● | ||||
| Register vault; add or revoke strategy; add cross-chain router | ● | ||||
Grant and revoke roles; set fee receiver (setManager) |
● | ||||
Upgrade Controller and HyperCoreAllocator |
● | ||||
Pause · unpause · exit all strategies (vaultExit) · shut a vault down |
● |
What the matrix shows
The Keeper is the only role that can both add and remove risk, and it also sets the fee rate. This is the operational role — it runs every day, so it is the key most exposed to compromise. The fee power is bounded (the rate can never reach 100%, and a change only applies from the next NAV snapshot), but it sits with the automation role rather than with governance.
The Guardian can stop but cannot steer. Pause halts deposits and withdrawals; shutdown is irreversible and exits every strategy. There is no intermediate "pull this one strategy back to idle" action available to the Guardian — that is a Keeper fundDivest.
The Admin can change code. Controller and HyperCoreAllocator are UUPS proxies whose _authorizeUpgrade is gated on DEFAULT_ADMIN_ROLE. The vaults and strategies are not upgradeable. See Upgradeability.
No single role can move the share price alone. A NAV epoch needs a Keeper proposal and an Admin confirmation within one hour. Dual pricing means that between confirmations the vault always uses the valuation less favourable to the party transacting.
Two roles must agree for funds to reach a new protocol. A Developer must register the strategy; only then can a Keeper fund it.
Where each role's checks live
| Contract | Roles checked |
|---|---|
KingsVaultV2 / KingsVaultV2Async |
Investor (deposit, withdraw, redeem, claim, emergencyRedeem); Guardian (pause, unpause, shutdown); Controller address (fund, harvest, fee-share mint); Keeper on the async vault (executeRedeem) |
Controller |
Admin (confirmValues, setManager, role grants, upgrade); Developer (registerVault, strategyAdd, strategyRevoke); Keeper (fundInvest, fundDivest, proposeValues, setFeeRate, vaultHarvest); Guardian (vaultExit) |
| Strategies | Keeper (invest, divest, replenish, exit, harvest); the Controller proxy must itself hold Keeper on each strategy |
HyperCoreAllocator / HyperCoreRouter |
Admin (upgrade, role grants); Developer (addRouter); Keeper (message handling, allocate, executeRedeem, router steps) |
The split is a design decision, not a limit
Every function in the contracts is gated individually, so the division of duties above is the one chosen for the current portals, not a ceiling. A new portal can be deployed with roles cut as finely as its mandate requires — separate proposers and confirmers, a Keeper per strategy, a fee-only role — without changing the vault or strategy code.
Every role is also simply an address. Any role can therefore be held by a contract that enforces narrower rules than the Controller does: a multisig, a timelock, or an automation contract that can call only one function on a schedule. One Keeper account is already such an automation contract; see Key holders. Administrative roles are designed to be held by multisig with time-delayed execution.