Upgradeability
Whether a contract's code can change after deployment, and who can change it, decides how much of this documentation is a description and how much is a promise. Status as of 2026-09-27.
| Contract | Chain | Upgradeable | Who can upgrade | Time delay | Storage |
|---|---|---|---|---|---|
KingsVaultV2 (Lending, GHO Saving) |
Ethereum | No | — | — | — |
KingsVaultV2Async (HLP) |
Ethereum | No | — | — | — |
Controller |
Ethereum | Yes — UUPS proxy | DEFAULT_ADMIN_ROLE (_authorizeUpgrade) |
None | ERC-7201 namespaced |
AaveV3Strategy, SteakhouseStrategy, GhoSavingFluidStrategy, GhoSavingStrategy, HyperStrategy |
Ethereum | No | — | — | — |
HyperCoreAllocator |
HyperEVM | Yes — UUPS proxy | DEFAULT_ADMIN_ROLE |
None | ERC-7201 namespaced |
HyperCoreRouter (×5) |
HyperEVM | No | — | — | — |
What an upgrade can and cannot reach
- An upgrade to the Controller can change how NAV is settled, how fees are computed and minted, how funds are routed between vaults and strategies, and what each role may call. It cannot change the vault contracts themselves, nor take a depositor's shares.
- An upgrade to the HyperCoreAllocator can change how bridged USDC is allocated on Hyperliquid and how state messages are produced.
- Strategies are replaced, not upgraded: a Developer registers a new strategy and revokes the old one (
strategyAdd/strategyRevoke), and a Keeper moves funds across. Depositors see this as a change in the vault's registered strategy list, on-chain. - Vaults are never replaced under a depositor: a new vault is a new product with its own address and shares.
Verification status
The upgradeable contracts' implementation addresses can be read from each proxy's ERC-1967 implementation slot. Source verification of the deployed implementations on Etherscan is not complete; see Deployment Verification Status.
For who holds DEFAULT_ADMIN_ROLE on the two upgradeable contracts, see Key holders.